We've seen apps doing this a few times before and have an idea of why it's happening. It's incredibly rare and caused by a misguided and broken attempt at anti-tampering. It will also likely break in future Android releases and with certain OEM variants of Android. They're likely using some debugging functionality to check the initial call stack and are hard-wiring specific permitted call stacks. Secure spawning has a slightly different initial call stack from how it starts differently. It's possible we can make it align or at least fake it so these apps stop banning GrapheneOS when secure spawning is enabled.
Santander bank app fails to work unless 'Secure app spawning' is disabled
Please help add it to the list of banking apps by filling out the issue form here: https://github.com/PrivSec-dev/banking-apps-compat-report/issues
11 days later
Hi all, any update on this? I tried turning off Secure app spawning but its still not working
Thanks
Dom
CoachDom Only thing I've done to date is open a Starling account and move my money over until I see what happens and in the mean time I can log on via the website and have most functions.
If roamer4223 does not hear back I will try and contact them also. If no luck I will just move on and close the account with Santander.