Barclays app no longer working, detecting GOS as "rooted device"

ntop

abdullah
Same issue here and i have logged a ticket with Barclays IT department to see where i get to.
There said it will take 3 working days
will update as i hear

DeletedUser495

abdullah there are multiple ways you can log in, I log in via account number and sort code. Some transactions require pin sentry, like making new payments or adding new payees. But pin sentry is not hard to get.

abdullah

DeletedUser495 even logging in requires pin sentry for me… oh well, it was good while it lasted. I think it's easier to access Barclaycard so that should be fine.

DeletedUser495

abdullah I don't believe this is the end of the road for you. I, when logging in through account number certainly don't have to use one. Have you explored all login options? Don't give up too soon. At what point in the login process is it asking to use pin sentry?

abdullah

DeletedUser495 It's immediately after I enter account number and sort code. Maybe it's just required for the first login? I'll give it a try and see what happens. I don't use my current account a whole lot so I don't really need constant/on-demand access to it to be honest.

DeletedUser495

abdullah in the second ID verifying step use passcode you have been given that you used with your app and memorable word, don't use option for app or pin sentry. Then later when you login for the first time on a new device you may have to re-enter full card number and security number, any subsequent login should be easier.

n3t_admin

have you tried disabling "Secure App spawning"? That sometimes works when an app mistakenly detects root.

DeletedUser495

n3t_admin that unfortunately disables secure app spawning across all apps. I wouldn't want to go that way, although exploring this may be interesting to those who only use small set of apps (like me). Thanks for bringing that up.

n3t_admin

DeletedUser495 hmm, I was under the impression this could be toggled on a per-app basis. Have you tried it just for testing purposes? At least this would bring clarity about the root cause.

DeletedUser495

n3t_admin I did. App starts normally, then throws memory tagging error. Disabled that.

When going to register, app complains with 00006 error (unable to process at this time). Tried turning off secure spawning, then hardened memory allocator, then enabled exploit protection compatibily. None made any difference for me, resulting in the same error, never got a message about device being rooted although when app was previously installed, after latest update app did start complaining about device being rooted.

n3t_admin

DeletedUser495 that sucks. Might be that they enforce some different checks related to Play Integrity now.

In that case I just recommend contacting their support, and if they are unwilling to change - switch banks when possible. I did the same back in the day with one of the German dinosaur banks (Sparkasse) which is just behind in tech (implementation and knowledge) by about 10 years. Never looked back.

DeletedUser495

n3t_admin the problem with banks, happens with one, happens with another. This is part of a bigger orwellian issue we are facing nowadays.

abdullah

DeletedUser495 it's why I have signed up with almost every bank and even some building societies 😅

SnowboundShip53

@DeletedUser495 did you hear back from barclays, the person I spoke to had zero technical knowledge

cleanbowtie

Has anyone gotten anywhere with this? Really frustrating!