I upgraded to /e/os 4.0 about a week after its release and now, once again, my banking app (AIB Ireland) is not accepting my fairphone 5 as an authenticated device.
It worked until the app was updated about a week ago. The bank doesn’t care and only advises I use Chrome and standard Android.
Any advice?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
Have you read this topic?:
Perhaps you could clarify as the post linked above does not explain the issue.
Do you mean that AIB say that if our app does not work for you then you should use an html method – Online banking – but only Chrome will work? How come “standard Android”? In addition?
I understand, the bank’s advisers just say use Chrome and standard (not open source) android as their easiest response to fob off their Customer. In the link I wanted to bring into the picture your post where you explained AIB offered other options of verification to activate the access.
Sometimes it is a pot luck what sort of an adviser on the phone you get when contacting your bank…
Yes thank you. It is very similar in that the app calls to an external browser at a specific point logging in. I’ve tried chrome and brave and neither work.
Am going to try and go to a physical bank to help solve this.
When I tested I saw this at first login but when you earlier said stopped working is it the case that subsequent logins also interupt progress to call for Chrome?
Are you hoping perhaps that this is a one off to simply authenticate a new device?
@aibd “Are you hoping perhaps that this is a one off to simply authenticate a new device?”
That would be a winner for Own_oh I guess.
No, it repeatedly fails the authentication when it returns to the full app.
This topic was automatically closed after 30 days. New replies are no longer allowed.
