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.
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.
The scanning is done on your device. You could theoretically only overload the CSAM reporting feature if such a thing will exist.
Last time I checked, it was broken for years already. It’s been a while though. Confirmed: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/ Only basic/device attestation is working.