Santander UK

[jonathancross]

Is there an existing issue for this?

• [x] I have searched the existing issues

App name

Santander UK

Link to app

https://play.google.com/store/apps/details?id=uk.co.santander.santanderUK

App version

5.18.0

Country of the app

United Kingdom

Build Number

2025041100

Device list

Pixel 8a

Profile app tested in

Secondary profile(s)

Google Play installed?

Installed

Where did you install this app from?

Google Play Store

Google Play services Network permission revoked?

• [ ] Revoked
• [x] Not revoked
• [ ] I did not have Google Play services installed

Native code debugging

• [x] Allowed
• [ ] Blocked

Exploit protection compatibility mode

• [ ] Enabled
• [x] Disabled

Memory tagging

• [ ] Enabled
• [x] Disabled
• [ ] N/A

Dynamic code loading via memory

• [ ] Restricted
• [x] Allowed

Dynamic code loading via storage

• [ ] Restricted
• [x] Allowed

Stock OS compatibility

• [x] Works
• [ ] Does not work
• [x] Not tested

NFC payments

• [ ] Works
• [ ] Works but requires another service
• [ ] Does not work
• [ ] N/A (Not supported by app)
• [x] Not tested

Description of the app's functionality

Needed to enable all permissions for it to load. Now that it is setup, I'll try to start revoking permissions 1 by 1.

Are there any extra notes you think users should know about?

No response

ADB logcat of the app if necessary

[jonathancross]

Hmmm... stopped working after initial login.

[spring-onion]

If you disable secure app spawning it should work.

[ar2g20]

Never mind, it's working sporadically at best. Will try to figure it out.

[ar2g20]

Nope. Ignore previous comments. It's stopped working

[SuperPauly]

Not working on the 8 Pro either. Hasn't for a month or 2.

[Callumari08]

Is this working? might wanna reopen this issue...

[Permanently]

From https://github.com/PrivSec-dev/banking-apps-compat-report/issues/143#issuecomment-2624493915:

I reopened all of the issues that pertain to previously deemed incompatible apps, the recent changes have improved compatibility on a significant number of them. When I receive feedback from users, possibly update their status and conclude my own digging I close them and move on to the next. That doesn't mean I won't still keep an eye out, I have notifications active across the entire repository so I won't miss any good news!

@Callumari08

[eylenburg]

App works for me on Android 16 (GOS).

• Main profile
• No Play Services
• Disabled secure app spawning

[jonathancross]

Great news @eylenburg! Can you please ensure that it continues to work after logging out and then back in again / restarting phone, different IP address (switching networks for example).

Thanks!

[eylenburg]

@jonathancross I didn't want to log out (in case it turns out to be broken then), so I installed the app into a Private Space. The private space has Play Services (unlike the main profile) and a different IP address (both are using different VPN servers). I had no problem logging in at all. Got an SMS saying "new device registered for mobile banking" afterwards. Secure app spawning is disabled in the main profile which I think also extends to the private space. The app is up to date according to Aurora Store (version 5.22.0)

One thing to mention is that when using it without Play Services, when it asks you to whether you want to enable notifications, you need to say "No" because otherwise it will crash. But notifications won't work without Play Services anyway.

[spring-onion]

Would be good to hear from a few more people, in the meantime I'm marking it compatible again.

[jonathancross]

Would be good to hear from a few more people, in the meantime I'm marking it compatible again.

Okay, I'm trying to get it tested by a friend.

[Permanently]

I'd argue that having to disable secure app spawning makes it not compatible, given you have to decrease security to make it work in the first place. I thought that was established from an earlier comment? https://github.com/PrivSec-dev/banking-apps-compat-report/issues/635#issuecomment-2815642836

Edit: just to contribute to the testing as well, it works on my device with secure app spawning disabled. I was aware that it worked without SAS for quite a while, as it was assumed we all knew.

[dimcraab]

Would be good to hear from a few more people, in the meantime I'm marking it compatible again.

Not even opening for me on my Pixel 8. have tried giving it all permissions but still closes on me immediately after launching. haven't even been able to login

[jonathancross]

@dimcraab Did you disable secure app spawning?

[dimcraab]

@dimcraab Did you disable secure app spawning?

yep. tried everything I could think of

[spring-onion]

I'd argue that having to disable secure app spawning makes it not compatible, given you have to decrease security to make it work in the first place.

I don't necessarily disagree. It comes down to us needing to update the list in a way that gives you a more nuanced verdict.

[Permanently]

Would it be worth doing an indicator for "works out the box" and "works in specific circumstances"?

[spring-onion]

@Permanently Something along these lines yes, there's multiple approaches you could take. For now if there's particularly noteworthy information to share about an app we'll include it within a simple sub-item below their entry.

[hodj1967]

This seems to be not working again. v5.23.0 30 Jul 2025. Fresh install of GOS+Play Services and install of app from a verified Google account from Play Store in secondary profile. Correction to previous submission: ~~Fails to launch~~ launches but immediately closes with exploit compatibility on and secure app spawning off. Phone rebooted and same behavior.

[JackMadeley]

The app appears to not be working again after an interim period where there were no errors.

I am running the latest version of GrapheneOS (Android 16) and have tried disabling the Secure Spawning and enabling "Exploit protection compatibility mode" but to no effect. I am running Santander UK v5.24.0 and have tried an existing install and a fresh install from the Google Play Store and Aurora Store - with no success. I have Google Play Services installed with network restrictions activated and even granting the GPS's access to the network still had no luck in getting the app past the initial 3 seconds.

[eylenburg]

Still works for me, v5.24.0 of the app

[JackMadeley]

Still works for me, v5.24.0 of the app

Could you let me know the details of the device and settings you are working with so I can try to replicate?

[eylenburg]

Could you let me know the details of the device and settings you are working with so I can try to replicate?

Pixel 8, GrapheneOS 16 (up to date), secure app spawning disabled, installed in private space with Play Services (and network permissions), installed from Aurora Store

[JackMadeley]

Ah @eylenburg you are right.

A fresh install from the Aurora Store and disabling Secure App Spawning (and then waiting about 45 seconds) does allow the app to run correctly.

[LivingFlyer]

Seems like it's broken again but I'm fully not sure what caused this.

[eylenburg]

Still works for me on v5.27.0

[LivingFlyer]

How did you install it?

[eylenburg]

Actually I just updated GOS to version BPA2A.250805.005 (newest version) and Santander keeps crashing now. I only updated GOS, not Santander. Santander was updated the day before, so this is seems to be issue caused by the GOS update.

[LivingFlyer]

So my initial assumption was correct that the recent GOS update caused this since it worked fine before. We should export the logs and hand them to the devs.