Anyone else having a problem with the Halifax app saying their phones rooted/Jailbroken

Jon_01

I had this error pop up after the app updated back in Nov.

The phone's an Android, never been rooted and has been running the app for over two years without a problem.

I was told that the next update would fix it. The update rolled out last Friday and nothing's changed!

Called the helpline a number of times, and they have no idea when a fix will be rolled out and have no way to communicate with the app developers!

I've tried 3 other banks apps and they all work without a problem.

Anyone else had this and found a fix?  Or do I just move banks?

Thanks

born_again

What android version are you running?

Jon_01

13, with security update from 01/11/23

Don't think it's that.

born_again

Wonder if it's related to phone manufacture?
Just tried my on Honor 90 (Android 13 same update) & works fine.

Mark_d

I'm running Android 13 and never had a problem with the Halifax app.

Does you have any software on your phone that the Halifax app could consider a security risk?  Have you unlocked the bootloader?

Jon_01

Mark_d said:

I'm running Android 13 and never had a problem with the Halifax app.

Does you have any software on your phone that the Halifax app could consider a security risk?  Have you unlocked the bootloader?

Nothing iffy installed. Just apps from Google store. Not got 'install from random sources' enabled (or whatever it's called).

The app was working fine, then they updated it, and it wouldn't work after!  Like, right after!

Also, if it were a problem with the phone, wouldn't other banking apps also not work?  Because Starling, Nat West and First Direct all work fine???

The helpline says that's lots of phones have stopped working like this, even vanilla iPhones are getting the message and not working!!

Mark_d

Different apps might have different checks they perform to decide if the phone is safe.

Since the a problem only happened when you updated the app, and the helpline advises it's a common issue, I think we know what the problem is.

I can't imagine it will be too long before Halifax provide a solution to the problem.  In the meanwhile there are still options to do telephone and internet banking?

Jon_01

Mark_d said:

Different apps might have different checks they perform to decide if the phone is safe.

Since the a problem only happened when you updated the app, and the helpline advises it's a common issue, I think we know what the problem is.

I can't imagine it will be too long before Halifax provide a solution to the problem.  In the meanwhile there are still options to do telephone and internet banking?

You'd think, wouldn't you. But they've been saying since Nov that, 'The next update will fix it'. The next update rolled out last Friday (so two and half months after the problem appeared) and it didn't fix it!

Most, if not all, developers would have just rolled back the version that created the issue, but Halifax don't seem to want to do that. They'd rather leave their frontline agents to field questions they haven't been supplied answers too...

Nasqueron

Mark_d said:

Different apps might have different checks they perform to decide if the phone is safe.

Since the a problem only happened when you updated the app, and the helpline advises it's a common issue, I think we know what the problem is.

I can't imagine it will be too long before Halifax provide a solution to the problem.  In the meanwhile there are still options to do telephone and internet banking?

Halifax and Lloyds (and I guess RBOS) are basically the same platform since Lloyds took over the group, while they could have different ones, it's unlikely. OP could setup a Lloyds one with a simple saver and use the app then and see if that has the same issue.

 I use Pixel 6 Pro with Android 14 and have no issues in either app, not unlocked the device either, just stock android.

flaneurs_lobster

What model of phone is giving the error? Let's see if anyone else with the same phone is getting the same issue.

HillStreetBlues

Jon_01 said:

13, with security update from 01/11/23

Don't think it's that.

Isn't that about the time you first started having the issue? so could be something to do with the update to 13