Yes.
Revolut prevented new users to login in a specific version of their app (the newer). Users that were already logged in could update the app without issue and users could use an older APK of Revolut to sign in. However the PlayIntegrity process that was banning their GrapheneOS users have been resolved and now the harden OS is whitelisted from Revolut.
At least that’s what I have followed/understood from the whole thing but I am not a Revolut user.
There’s more to it. It wasn’t Play Integrity blocking Graphene per se, but the fact that Revolut checked the build ID string, which was uniquely identifiable as Graphene for any build. This was then made more generic, so the block doesn’t work for now, but the workaround could break any moment and be made impossible by Revolut enforcing “strong” level of Play Integrity. Such bullshit.
Yes. Revolut prevented new users to login in a specific version of their app (the newer). Users that were already logged in could update the app without issue and users could use an older APK of Revolut to sign in. However the PlayIntegrity process that was banning their GrapheneOS users have been resolved and now the harden OS is whitelisted from Revolut.
At least that’s what I have followed/understood from the whole thing but I am not a Revolut user.
There’s more to it. It wasn’t Play Integrity blocking Graphene per se, but the fact that Revolut checked the build ID string, which was uniquely identifiable as Graphene for any build. This was then made more generic, so the block doesn’t work for now, but the workaround could break any moment and be made impossible by Revolut enforcing “strong” level of Play Integrity. Such bullshit.
Monopolistic behavior…