[Magisk] pndwal:
No problem.

I mentioned John's comment about "the already lost cat and mouse game" because, as this indicates, ability to have root (our cake) and working bank apps (and eat it too) is not only doomed*, it does take a lot of maintenance...

John has indicated for several years now that he is no longer interested in playing this game / leading such efforts any more... He has said this was just a fun persuit for a while, but not the real purpose of root or Magisk...

If you are "really fed up with all the maintaining [of your] phone" needed to have but hide 'root' (really broken TEE), imagine how he feels... In his 'State of Magisk 2021' article he said "if you have paid any attention to Magisk’s development in the past few years, you’ll know that I have basically stopped putting any effort on circumventing various “root detection” methods. It honestly is no longer enjoyable for quite a while, and this is the perfect time for me to shift focus on things I find more interesting and important"

Really he wants to develop Magisk's potential with a future.

This means improving compatibility and functionality for

1) it's basic use as a root solution (Providing root access for applications, dev vulnerability testing etc),

2) it's use as a "Magic Mask" (Ability to modify read-only partitions by installing Magisk modules who's files are magic mounted),

3) value-added 'poweruser' functionality like Zygisk (this can run code directly in every Android applications' processes when a part of Magisk runs in the Zygote daemon process).

Magisk hiding solutions (apart from hiding within userspace) has only a short-term future at best.

This means:

1) Hiding development, while made more powerful by John adding Zygisk and other features (eg. new sepolicy injection mechanism was introduced just 3 days ago in a Canary debug build), is now led by other's (keen module Devs), so solutions are of course more fragmented.

2) Hiding 'root' (read obtaining passing attestations to TEE) is not currently a game with Google; the active cats are now the banks and other security-centric app developers, so there's now a clowder of cats!

3) These cats are prowling, often together, since they understand that they simply cannot trust Google's SafetyNet API wheel ATM and are constantly reinventing it. (Actually Google already have the new wheel installed, but since the tyre is leaking it's no good to the banks).

4) Hiding in practice for Magisk users (the mice) is now more complex for all the reasons above, and is not a game for the faint of heart... Just as it's too much now for one dev, as the new mice we are being run ragged!... John lately described this as a war rather than a game... Hiders should also be realistic; it will be time consuming and challenging to keep up... Some have given up the fight already, others are more dogged.

5) Hiding in practice is currently still possible but no-one should be under any illusions that it will definitely be achievable even as soon as tomorrow... Proper HKA deployment could arrive at any tick of the clock... Yup, the big cat is not asleep despite the false sense of security some mice seem to have. When it will pounce is the cat-ch.

*Note: We're already on borrowed time it seems until final deployment of Hardware based Key Attestation; Google is likely only waiting for sufficient Android 8+ market saturation, or for OEMs to get their implementations right - we know OnePlus, and likely others, messed these up - which will spell the end of this cat-and-mouse-game without a practical way to circumvent SafetyNet API or it's upcoming new replacement, Play Integrity API.

There may be more than one way to skin a cat, but we need to remember we're only mice in the game... PW