I tapped on the notification a few mins after it came up but it seems to have gone from TestFlight.
So it has. I updated before it got pulled. Hope it wasnât because of something disastrous.
(I know I can roll back to an older build if so)
Also got it and was coming on here to say it is noticeably snappier for me
perhaps one of the coral crew could ask in the slack channel if there was a reason it was pulled? please and thanks
Iâve asked through TestFlight beta feedback
I got logged out of Monzo just after I updated and had to log back in. Not sure if thatâs related to why it was pulled.
Just raised the question. Iâll let you know
Thanks Jack, much appreciated.
Thanks Colin for also raising it through feedback, wouldnt have thought to do that myself
Response: â We need to upload a new build which has a bug fix for incorrect categorisation for older transactionsâ
Oooh I wonder if this fix is for this:
Ahh thats grand, so nothing wrong with running this .14 build. no need to roll back?
âIt should be ok but theyâll need to logout/login again when the build with the fix has been uploaded if they want older transactions to be categorised correctlyâ
Sadly not
Whereâs this weekâs screenshot? Youâre slacking.
Have to work sometimes (semi retired so only occasionally)
Itâs because the updates are so dull
We want POT SORTING!!!
We want POT HIDING!!!
We want DARK MODE!!!
None of this Business and US account rubbish⌠Gosh Monzo sort it out please!
We donât want any of this bug-fixing nonsense anymore please Monzo.
Bugs are merely features that you hadnât discovered yet, I donât know about other people but I like a very feature full app