there is always a constant crash when you force quit the app then open it again. It always crashes the first time it is opened.
Subsequent times its opened (where it hasnāt been force quit) doesnāt result in the crash.
1 Like
Itās interesting that you say that.
I have experienced the same exact thing in the past, but not lately. Generally, I open the Monzo app to use it briefly, then close it from multitasking pretty much straight away when Iām finished because I use it ad-hoc and berg know if I will need it again for a bit. I leave the app for a second to āgo into backgrounding modeā before I quit it, but I donāt seem to get a crash next time I open it?
hmmā¦ it was doing it minutes agoā¦
I force quit all my apps (I never normally do this) to record a video of it doing it and now its not ā¦ wonder if it was me all along 
edit: got it doing it againā¦ Its if I open the app ātoo quicklyā after force quitting it.
2 Likes
At a guess, itās probably that you force-quit it too quickly: not giving Monzo enough time to go into the backgrounding state before quitting, leading to it failing to save-state properly and being unable to resume on next launch, resulting in a crash.
Itās also possible that you are launching it again ātoo quicklyā as there may be background cleanup going on still and then an immediate re-launch causes a crash?
PS: @N26throwaway The other point to this (that I forgot to mention!) is that continually upgrading-over iOS with the same backup probably more closely recreates how ānormal peopleā use their phone, and is therefore valuable feedback. I appreciate that they wonāt be doing so as often, given the number of builds involved in beta releases, but they are likely to do so a lot. Their first thought when experiencing a bug is also unlikely to be to give their phone a fresh install, so even if that would fix the bug anyway, if there is a way to fix it more gracefully (for the user) then that would be preferred. Running my phone this way therefore may reveal bugs which are likely to affect normal users, but which we otherwise wouldnāt uncover if testing on a ācleanā device, so I see my feedback as valuable and hope it is.
That isnāt to say that bugs are not sometimes caused entirely by using beta iOS, as by definition there will be iOS bugs in the software which may interact with apps in unpredictable ways, but I am confident analytics data will probably point to the cause of individual bugs. Iām also always happy to run isolation testing where I restore to a public release to see if a bug is still present, if required.
Additionally, I do read Appleās own release notes for new builds (when available), so if a bug is caused by a known issue in iOS I will already be aware of the cause and will mention this if/when reporting to Monzo. Sometimes this is helpful as changes in APIs can require refactoring of code before public release, otherwise the public would see the issue too, so a report to make Monzo aware (in case they arenāt) acts as a way to give early warning to allow time for that refactoring to happen before the public ever upgrade.
1 Like
Hi @iOS_Health team. I have a bug for you.
The new app evolution transaction feed doesnāt mark transactions as viewed and so when I get a new transaction the notification badge is higher than it should be.
If I go to the normal feed by tapping on my Monzo card, it clears fine.
This is really really annoying. Pls help 
3 Likes
Great to see, be good for a fix on the feed issue, and having to kill and restart the app to get it to update
2 Likes
Hey @michaelw90, thanks for reporting that. Could I ask that you share that feedback via the āGive us feedbackā button on the new home screen? That will route the message directly to the App Evolution team working on that feed 
1 Like
Oh this is new. Iām trying to submit a twitter link for a logo. After pressing submit, this error appears. No idea what it means.
3 Likes
Possibly relies on the borked Twitter APIā¦
5 Likes
Yes of course. Bloody Elon 
1 Like
Itās great to hear this is happening. Iāve had performance issues since 2019 when I first started using Monzo. The main problem is swiping left and right between pots - very laggy for me.
Hopefully you guys can get it sorted!
Thanks.
2 Likes
Hi, Iām Dale and Iāve just joined Monzo as a Senior iOS Engineer in the iOS Health Team, joining @MikeMurray & @leewatkins.
Iāve been developing iOS apps since 2010, spanning various industries such as banking, investments, sports and retail. During that time Iāve also had the pleasure to work on developing backend services and infrastructure as well as scaling projects and teams and occasionally dabbled in the management side of things. But I always get drawn back into engineering as tech is where my heart lies.
Iām a father to two amazing daughters, so my spare time is mostly dedicated to them. But when I do get a spare few minutes I love a bit of gaming and try to watch the F1 whenever I get chance.
Iām looking forwards to getting stuck in and engaging with the community!
14 Likes
Welcome to the best community on the internet, Dale!
9 Likes
Nearly 2 months on, itād be interesting to get a rundown from @iOS_Health if we can of what improvements have been done thus far based on the new team being formed?
8 Likes
Any reason why Monzo takes up 2GB on my iPhone 13 Pro Max, iOS 16.3.1?
Iāve deleted the app many times and reinstalled it, and then it stays at 200mb for a day until it shoots up to 2-3gb?
Probably historic transactions/attachments?
Thatās a lot.
A few things that will contribute: uploading images of receipts for transactions, custom contact photos, your own photo, custom pot images, minzoās own pot images, your recent transaction history.
Again, thatās abnormally large. Significantly more than mine. Perhaps you use those features a lot and I donāt. But documents and data is often a result of things being cached locally, or documents you add to the app like what Iāve mentioned above.
2 Likes
no attachments whatsoever to the transactions like any files. just opened the account two weeks ago