Replying to Avatar GrapheneOS

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq9dxzvzpewcce5zkqtupqqypju4y2p5je6k7zq6wzme7gnkv0ja4smmrhum You can see Revolut shows an error about custom firmware not been supported where they claim they are "serious about keeping your data secure". This is them using an SDK to specifically detect GrapheneOS and then banning it. It is not related to the Play Integrity API at the moment. It's a client side check within the app. Play Integrity API is something their service can enforce based on the app triggering it and their service obtaining the result from Google's service.

This is a pain. Lloyds Bank (UK) app used to work well until a year or so ago when they did similar. :(

Are you aware of any info, anywhere, on which banking apps are happy to run on custom firmware?

Reply to this note

Please Login to reply.

Discussion

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqfn95p9khdsazyanadz7ksrwuel0yjslhccfk7h50dh4472acw8dqpkmmk6 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq9dxzvzpewcce5zkqtupqqypju4y2p5je6k7zq6wzme7gnkv0ja4smmrhum It may work again after our recent changes to work around Revolut banning GrapheneOS. They may be using the same SDK as Revolut to ban using GrapheneOS. Neither appears to be enforcing a Play Integrity API device or strong integrity level yet, only their own very weak checks which we can easily bypass if we work on it. The issue is that there are a huge number of apps and they're creating work for us doing this.

Bah, you got my hopes up then! No dice. I realise this isn't in you, so no probs.