The Monzo app fails to maintain its activity state when moved to the background during the 2FA process. This creates a critical “Activity Switching Glitch” where the user is unable to complete the login because the app refreshes or closes the input dialogue as soon as the user switches to another app to fetch the required security code. This is particularly problematic as the app requires a TOTP code but makes it impossible to retrieve one from the same device.
Thanks for your response. Your explanation makes sense, and I believe it is generally correct. Under normal circumstances, I use biometric authentication to access the Monzo app.
There are, however, a small number of scenarios where I have observed different behaviour. One example is when adding a payment card to Google Wallet. After entering and submitting the card details, the Monzo app is launched to verify the request. During this process, I am prompted to enter a six-digit code from my authenticator app.
This is where the issue arises. Because of the previously reported bug, I am unable to access the authenticator app when the Monzo authentication flow is active on the same device, preventing me from completing the verification process.
This appears to be a genuine usability issue, as the authentication process requires a code from an authenticator app that cannot be accessed at the point it is needed when both applications are on the same device. As a result, I am unable to complete the verification process.
Thank you for taking the time to review this and for helping to clarify how the authentication process is intended to work. I appreciate your input.
I’m flattered with the possibility of being confused with an AI bot, unfortunately, I am quite the opposite. Thanks for everyone’s time and information. It would seem I’ve actually confused myself as well. After reading the latest response, I searched for Monzo in Google Authenticator, and there isn’t an entry. If the 6-digit code is being requested by Google Wallet, I genuinely wasn’t aware.