Hi everyone,
good to see we’re once again working together to get around this “security” check.
FYI: This comment does not contain a permanent solution, but a potential temporary one.
tl;dr: Uninstall MobilePay, reboot phone, install MobilePay, log-in with MitID etc… works again - for a couple of minutes.
I’m sporting a Fairphone 5 on which I previously was also not able to log-in to MobilePay with MitID. This was resolved with help from @oliveradams who provided the uninstall-default-browser trick in this thread - thanks again!
So, after applying that fix I now have another default browser (Brave) and the default browser removed. MobilePay worked great for several months. That changed after a recent MobilePay update, after which I got the same “Security check failed (…)” message as @Thaulow above (while still on /e/os 2.9).
Today I updated to /e/os 3.0.1 and rebooted my FP5, after which a lot of apps also updated - including MobilePay. Full of new hope, I tried logging in to MobilePay again… Same error… A little disheartened I gave it one last shot after all other app updates had completed:
- I uninstalled MobilePay
- I rebooted once more (because, “have-you-tried-turning-it-off-and-on-again” actually works sometimes)
- I re-installed MobilePay (from the /e/os App Lounge)
- I logged in (needed to go through SMS activation + MitID authentication again)
- I was in - and able to make a transfer
Unfortunately my happiness was cut short as the red text of doom once again appeared after a few minutes. I was able to snap a quick screenshot before closing the app and getting “locked out” again:
This error hints at the initial “authentication” login potentially being different from subsequent “refresh” ones.
I’m sorry I can’t provide a permanent solution, but I hope that this additional info may help nonetheless in finding one.
I’ll be watching this thread, and hope that one of you figures it out, or will update it if I’ll be lucky enough to.