Aside from getting a new phone, I’ve tried everything. and I’m tired of trying, so I’ll admit I’ve not gone through the typical trouble shooting steps each new update (I just update and see if it’ll launch), and honestly, I shouldn’t have to.
The delete, restart phone, reinstall trick used to fix it, until it would crash again a few days later and the previous steps had to be repeated. That alone was a dreadful experience.
I appreciate the steps I’ve outlined haven’t worked to replicate the issue. They have worked for me to replicate on dev devices which consist of a brand fresh install of monzo that aside from being launched, has never been logged into or set up, to rule out any settings within Monzo causing it. But I’m not the only person it’s impacting as evidenced by folks above and in the other threads I’ve linked to. You’ll find a bunch of folks complaining about it on twitter and reddit too.
@JJWILK088 seems to be stuck in the same situation I’m in, so I’d be curious if they’ve found a way to fix it.
I don’t know if there’s anything different about my device vs other folks, I don’t have any particular sort of special setup, I tend to stick to defaults for most things. The only setting I change for Monzo is to enable Face ID for authorising transfers and confirming purchases vs my card pin. But that’s not the cause because it’s happened whilst I’ve had it disabled too. Nor would it explain why a fresh installation of the Monzo app crashes on launch too.
But who knows, it wouldn’t be the first time a bug has been triggered by something odd that seemingly has no discernible connection. Equally it could just be something in Monzo’s app which only discriminates against a particular thing so as to only manifest for some folks and never for others. I’ve had an app crash before because it plugged into my contacts. One of my friends has accents in her name, and one of those accents would cause the app to hang. Or like a bug equivalent of what Uber did to Apple to trick their app reviewers. Perhaps it doesn’t like my v6 IP (most folks are still v4) address and that causes the app to get stuck that it can no longer be launched. Your guess is as good as mine. Apps are complicated; moreso when they’re a front end for a service as complex as Monzo. Only Monzo has the looking glass required to identify the cause and fix it. All I can do is look for patterns that can hopefully point them in the right direction.
I steer clear from beta software, only resorting to installing the Monzo TestFlight build to try to overcome this bug and another. I’m currently sticking with the release builds. I’ve moved everything over to RBS for now, so it’s no stress at this point, and I care little for trying to fix it myself. I’ll keep checking every update, nag the thread, and hope Monzo will eventually issue a proper fix on their side.
Edit to add: If it helps, although it first happened to me on July 8th, it appears to have began around the time the neon cards launched, correlating when the consistent and frequent reports from users began appearing online. Several the day those cards launched, and a steady stream of them since then up until now. Prior to that date, complaints of crashing were scarce and not happening upon launch of the app.