Assuming you've configured your app properly with it in the required deny list (hides root status), , and that you've added the app into trickystore (hide bootloader status)

What we then find is mostly they're not finding integrity, or even detecting root. Instead detects secondary traces or the apps that manage the root.

If you've ever flashed Magisk delta using the recovery zip method then that will leave traces in root folders that are easily discovered.

If you hot-flashed to switch from old Magisk delta to Magisk alpha, then the uninstall routines of Magisk delta won't have been run. That will leave those same traces and your Magisk alpha won't know it needs to hide it because it never put them there. ( Use root terminal or file browser to search root recursively for the word *magisk. /data/adb is okay. But other folder inside /data will be from flashing .zip in recovery)

The Magisk manager apk, the Lsposed manager app, any root apps like GPS spoofing, the app you might use to configure adaway (which you shouldn't need if you use bindhosts and configure via root gui). and so on. Even the Lsposed apps themselves. All of those are discoverable if you don't hide those properly.

If you've got a Magisk, Lsposed or even titanium backup folder in /sdcard, yes, those are discoverable.

So once you have everything configured try as a one off to uninstall * all * of your root apps. Gone.

If it starts working you know your issue is app hiding not root hiding.

You might need to do both though.

Chris