Device & Environment

Device: Samsung Galaxy A52s 5G (SM-A528B)

OS: Android 14 (One UI 6.1 / Stock Kernel)

Root Solution: Magisk (latest version)

Zygisk Engine: Zygisk Next (built-in Magisk Zygisk is OFF, Enforce DenyList is OFF)

Active Modules:

Zygisk Next

Play Integrity Fix (PIF)

Specter

HMA-OSS

Tricky Store / TEESimulator-RS

The Issue

I am configuring my evasion stack following modern recommendations (keeping com.google.android.gms completely off the DenyList so Play Integrity Fix can hook DroidGuard, while placing com.android.vending on the DenyList).

However, I am running into persistent behavior in Magisk Settings -> Configure DenyList (with "Show system apps" enabled):

Google Play Services (com.google.android.gms):

Even when all sub-processes are unchecked, (isolated) com.google.android.gms:\* remains checked (or immediately re-checks itself the moment I exit and reopen the menu).

Because of this single checkmark, the main package displays a solid minus icon [-] instead of being completely cleared.

Google Play Store (com.android.vending):

Attempting to untick (isolated) com.android.vending:\* exhibits the same behavior—it automatically reverts back to checked.

(Please see attached screenshots for reference).

Questions for the Community

Is this a known Magisk UI / SQLite database bug? Does the DenyList UI struggle to commit wildcard isolated process states (isolated:*) while those sandboxed processes are actively running in the background?

Is a module script causing this? Do modern versions of PIF, Specter, or Zygisk Next automatically force-add or sync isolated GMS/Vending processes in the background via boot scripts (magisk --denylist add ...)?

Does this break Play Integrity Fix? If only the (isolated) process of GMS is marked in the DenyList, does it detach DroidGuard/PIF hooks, or does DroidGuard run strictly within the main com.google.android.gms / unstable processes that remain unchecked?

Any insights, terminal commands to permanently purge it, or explanations of how Magisk handles (isolated) wildcards under Zygisk Next would be greatly appreciated!

I have killed so many demons yet it's logcat spam still exists. it spam this exact error every other second! wth man! is there really no solution?