24-09-2025 22:26 - edited 24-09-2025 22:47
24-09-2025 22:26 - edited 24-09-2025 22:47
Don't know if anyone can help - went through the convoluted process of linking O2/VM accounts today (despite having zero products with Virgin). I don't login to my account very often, hence being late to this party.
After setting it up (which wasn't straight froward), I can no longer login to the O2 app using biometrics/passkey. I am using Android and my phone is a few years old now but all my other apps that use passkeys still work fine (as did the previous O2 app).
At first, it wouldn't let me setup a passkey at all - when I chose the option to do so, it just sent me back to the previous page with the message 'you've cancelled adding a passkey', despite the fact I did not cancel anything.
The only way I could get it to work was by selecting the 3 dots at the top right of the phone screen which then gave me an option to "Open in an external browser".
Once I chose to this, it let me setup the passkey no problem at all. So I can login to my O2 account on my phone using biometrics/passkey if I use the web browser. But when logging in through the app, the app's in-app browser will not recognise the passkey. It's as though there is no link between the two.
I've checked all the settings on my phone regarding autofill/password manager etc, and nothing has changed from how they were before. All the other apps that use passkeys still work. The only variable that has altered is this new VMO2 app.
Anyone experienced similar? Anybody know if the app's in-app browser is not compatible with older phones (Galaxy A50, 6 years old).
Not the biggest problem ever because I can login via the browser. But it makes having the app a waste of time because to log in on it via another method means I have to keep getting verification codes emailed to me which is ridiculous.
How have we gone from the previous version where if I switched to data instead of Wi-Fi I didn't need any kind of login, to this utter mess??!!
on 24-09-2025 22:36
Try deleting the app and reboot your phone before reinstalling it.
on 24-09-2025 22:38
on 24-09-2025 22:38
on 24-09-2025 22:40
on 24-09-2025 22:40
I tried that, but unfortunately no luck:(
24-09-2025 22:44 - edited 24-09-2025 22:45
24-09-2025 22:44 - edited 24-09-2025 22:45
It could be that. But the previous version of the app worked fine, and all the other apps I have on the phone that are using passkeys still work without any issues.
If it is a compatibility issue, you'd think that they could have let us known in advance.
Not the end of the world if it can't be solved, as I can just login via the browser. I'm more curious than irritated now as to what the issue is.
on 24-09-2025 23:00
on 24-09-2025 23:00
According to...
https://www.o2.co.uk/help/products-and-services/o2-services-and-apps/my-o2-app
How to get the My O2 app
To get started, you’ll need a smartphone or tablet with either Android 7.1 or later, or iOS 14.0 or later.
Android 11 should be good too 🤷
Not the first time O2 have got it wrong though...
on 24-09-2025 23:10
on 24-09-2025 23:10
Yeah.... No idea what the issue is, but I've wasted more than enough time trying to figure it out without success. Must be something to do with the in-app browser not syncing with where the passkeys are stored on my phone - yet all other apps with passkeys work no problem. I'd be surprised if I'm the only one with the issue though.
Hopefully some genius will post here soon with an easy fix/workaround. For now, I'll remove the app and just use the website.
24-09-2025 23:25 - edited 24-09-2025 23:27
24-09-2025 23:25 - edited 24-09-2025 23:27
on 25-09-2025 00:37
Maybe something that @Dave-O2 can look into for you @Jossy278 ?
on 25-09-2025 08:27
on 25-09-2025 08:27
Ping doesnt support Android 11 for any authentication methods, hence it wont accept your device, it supports Android 13 and up.
Ping is the platform used by o2 for authentication