[Magisk] V0latyle:
Yeah. It seems like a lot of instant reactions to this topic is "Google is trying to screw us rooted people!" when it's not Google at all; after all, THEY haven't implemented any sort of alternate root detection besides what we've already discussed regarding...uh, was it DroidGuard? I forget, but anyway - Play Services, GPay and Wallet are all happy with PI reporting BASIC and DEVICE only

The only things Google enforces for third party apps is their own requirements for the Play Store, i.e. your app can't be malicious, it can't block ads, and Play Store itself won't allow you to download certain apps if your device is Play Protect uncertified. But, beyond that, each developer has their own criteria for devices they'll allow their app to work on, as well as what function may be limited if not all elements of their criteria are available.

For example: I use this app for my main bank:

Navy Federal Credit Union - Apps on Google Play

Our Members Are the Mission

play.google.com

The only thing that doesn't work anymore is biometric sign in. I'm not sure why. I can still log in using password/passkey/2FA/etc

But, since the nearest branch for that bank is over an hour away from where we live, we have an account open with a local bank for when we need to withdraw cash or get a cashier's check, with this app:

Mid America Bank Mobile - Apps on Google Play

Bank conveniently and securely with Mid America Bank Mobile Banking.

play.google.com

This one has much more strict requirements - if it even THINKS your device is modified, even if you only have USB debugging enabled, it won't work at all.

My point in both of these is that this doesn't have anything to do with Google. Google's apps continue to work just fine on my unlocked + rooted device. Of course I have to use an easy fix in the form of Displax USNF+PI module but that's been the case since the early days of SafetyNet for those of us who have been around that long. I don't really know why they migrated from SN to PI, my guess would be to make things somewhat simpler while also more secure, but ultimately it doesn't matter because it doesn't really change anything for us - as long as basic attestation continues to work, we'll continue to be able to spoof it. And since Google probably doesn't want to force Android <=7.1.2 users into obsolescence, I don't think we have much to fear from them.

Developers on the other hand...Some don't seem to care what requirements they might impress upon their users. After all, there's iOS exclusive apps, right? Probably because those developers like the idea of the "walled garden" nature of iOS, despite Android being far more popular in the smart device market. There's also some that for whatever reason decide that a device has to be completely up to date and pristine - there's apps out there that have dropped support for Android 10 and below, despite the fact that Android 10 continues to be very dominant in the Android market, moreso than 12 and 13, with only 11 taking the majority.

And I don't want to sound like I'm defending Google here. I have a lot of problems with them in a lot of ways - privacy for example - but I think it's important to make sure we know who's actually to blame if something gets broken, and in this case it isn't Google...most of the time.