Last time I checked, it was broken for years already. It’s been a while though. edit: Confirmed: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/ Only basic/device attestation is working.
ByteWelder
joined 2 years ago
As far as I’m aware, there are no work-arounds that allow for circumventing the Play Integrity API. Probably because you cannot avoid the involvement of a Google backend API that is accessed by the app’s backend. It works like this: Play Services hands a token to the app, the app sends it to the app backend, and then the app backend lets a Google backend verify the token, which results in a verdict. You cannot manipulate the token.
More specifically, Play Integrity API will fail on the Play Service integrity check. If I recall correctly, this is why Google Pay won’t work on GrapheneOS.
Some banks require the app to be used as second factor to log into their website.
The main problem with case-insensitive is that software sometimes is lazily developed: If a file is named “File.txt” and a program opens “file.txt”, then on a case-insensitive file system it will work fine. If you then format your drive to case-sensitive, the same software now fails to load the file. Source: tried case-sensitive filesystem on macOS some years ago.
It can also be due to unsafe charging (over-voltage) or unsafe discharging (over-current, generating too much heat). The actual fire doesn’t necessarily happen immediately during charging/discharging.
Incorporates 3rd-party DRM: EA on-line activation and Origin client software installation and background use required
Requires 3rd-Party Account: EA Account (Supports Linking to Steam Account)
Seems like another cursed EA game with built-in spyware.
Have an upvote. I’d pay double what Affinity is currently asking to have their products on Linux. Gimp is the opposite of intuitive.
If they put the ads in the stream, you can just fast-forward. I don’t think it’ll work out well for Google.