Target UID resolution fails at boot and Keys tab stays empty

Environment

• Device: Samsung Galaxy A15 4G (SM-A155F), MediaTek MT6789/Helio G99
• Root: KernelSU-Next, ReZygisk
• TEESimulator: v4.0 (62-fa2f863-debug)
• Also installed: Vector, Play Integrity Fix, Tricky Addon (target list)

Summary

On this build, the control daemon's boot-time UID resolution for every configured target package fails outright, so the pushed profile ends up with 0 UIDs attached. The practical symptom is that the "Keys" tab in the companion app always shows "This module hasn't minted any keys for the target apps yet"

What the logs show

Right after the daemon starts (org.matrix.teesim.App), it tries to resolve a UID for each configured target and every single one fails:

TEESimulator: uidForPackage(com.google.android.gms) failed
TEESimulator: uidForPackage(com.android.vending) failed
TEESimulator: uidForPackage(com.eltavine.duckdetector) failed
TEESimulator: uidForPackage(com.henrikherzig.playintegritychecker) failed
... (all 15 configured packages fail, identically, twice in a row)

Which leads directly to:

TEESimulator: Scope[default]: 'com.google.android.gms' -> NOT INSTALLED for user 0 (dropped)
TEESimulator: Scope[default]: 'com.eltavine.duckdetector' -> NOT INSTALLED for user 0 (dropped)
... (same for all 15)
TEESimulator: Scope[default]: effective = 15 package-match name(s), 0 caller uid(s) [], 15 invalid/uninstalled, 0 auto
TEESimulator: Scope: published resolved snapshot epoch=..., 1 profile(s), 0 auto uid(s) total, baselineReady=true

TEESimulator-v4.0-62-fa2f863-debug-20260826-234507.log

Start at the control daemon launched by org.matrix.teesim.App and trace the boot-time uidForPackage failures through scope resolution. Reproduce with the attached log and configured target packages; done means valid UIDs are attached to the profile and the companion app's Keys tab no longer reports that no keys were minted.