[Android Software Development] pndwal:
Must say I completely disagree with your assessment of John's current employer as 'the dark side' / 'the enemy'... His previous appointment was with Apple.... I suppose they're the light side / our friends in your book? 😝😜😬

I could argue Google are our benefactors, building in easy unlocking / modifying ability (that only certain manufacturers circumvent), and even knowingly allowing modding community (which their reps even describe as 'White Hat') to 'subvert their security model' and bypass SafetyNet until now... (Does the competition do this?) but sure, patching this obvious 'hole' is clearly on the agenda (to thwart 'black Hat' crooks / hackers / thieves / scammers / swindlers / fraudsters...), only it seems because their corporate partners (many having their own requirements as GPay & Samsung Pay partners for example) are demanding it & G risks loosing market share to their major competitor... and they have already...

I've mentioned before that many government / security concious entities already ban Android devices at work and often purchase / issue iPhones as a security measure... I think we just need to 'get real' here... I don't believe G will suddenly become anti-root anytime soon however...

Android will likely remain the only competitive out-of-the-box mod-able platform for some time despite tightening attestation to TEE (which really only safeguards proprietary software / interests), and this is largely thanks to Google and the Open Handset Alience they established having an inclusive vision re. custom mods incl many open source projects... They create all the major milestones that make Android what it is / keeps it innovative, usually in closed-shop builds for their own flagship devices before releasing AOSP code...

Xiaomi then takes this vanilla experience and gives you Mocha MIUI which you loathe having developed Sudden Chocolate Taste Aversion, so you tip the mug out and fill it with a more pure AOSP experience again... courtesy of...

...

GOOGLE!

Want more detail? Here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85140701

and here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85142363

Sorry for the OT folks!

Back to the subject, I missed that you run a custom ROM. This likely means you'll need Magisk Hide Props Config module w/ a certified fingerprint configured in addition to USNF as spoofing Compatibility Test Suite certified ROM is out of scope for USNF as mentioned in USNF GitHub instruction page.

Further, please say what Magisk App Check SafetyNet says for evalType. Are you seeing Basic, N/A or other? (If this check is no longer working, you can alternatively use new YASNAC checker).

Nb. Try toggling MagiskHide off then on again in settings to pass and then clear Google Play Services and Google Play Store data to get Play Protect (check in Play Store settings) device certification pass.

Nb. Several modules (eg EDXposed) break SafetyNet, so ensure all but Riru and USNF 2.1.2 are disabled initially.

If you still have issues, please give more details, eg what custom ROM? (Just remembered, some ROMs themselves, eg Pixel Experience, are themselves incompatible with new USNF solutions due to their manipulation of props in custom utils; swap to cleaner ROMs like LOS or petition ROM Dev to fix internally...)

🤠 PW

Edit:

Bit further re. you inability to hide Magisk App and / or use Check SafetyNet; this would indicate that something may be borked in Magisk setup, or you may have network issues (I believe public builds still have use online stub APK). Do you use a firewall / adblocker etc, or similar on modem / router if using a hotspot? (Try with mobile data if previously using wifi).