Damus
GrapheneOS · 2w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqwhgfwfvcvyzqflek0ktawafynukauvjgvg44hrmn0q2ckjswc2gqwfs7qu Did you try the per-app exploit protection compatibility mode?
bluebird profile picture
@nprofile1q... Yes, I did try that without success. The app crashes in an obfuscated code path (no memory corruption bug ig) and opens a website stating that the device might be rooted or there would be settings that reduced system security.
For some reason, the issue can π—»π—Όπ˜ be reproduced on my P6a on the same app version 5.3.1 (latest). They might have setup hardware attestation but did not add the keys of the GOS build on newer Pixel devices?

https://discuss.grapheneos.org/d/23692-sparkasse-pushtan-app-not-working-anymore/92
https://github.com/PrivSec-dev/banking-apps-compat-report/issues/604
1
GrapheneOS · 2w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqwhgfwfvcvyzqflek0ktawafynukauvjgvg44hrmn0q2ckjswc2gqwfs7qu That's likely the issue. We made it easier for companies to automatically add the new ones by adding a signed JSON file providing them. https://grapheneos.org/articles/attestation-compa...