Target UID resolution fails at boot and Keys tab stays empty

[poqdavid]

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

[JingMatrix]

A Vector Xposed module is crashing the system_server, over Samsung's SemWallpaperThemeManager.

Please disable that module, and test TEESimulator again.

[gavdoc38]

A Vector Xposed module is crashing the system_server, over Samsung's SemWallpaperThemeManager.

Please disable that module, and test TEESimulator again.

Similar to my one:
#268

When this occurs, once system_server is restarted, is it possible to restart the daemon with a new PackageManager handle?

[gavdoc38]

@JingMatrix in service.sh, would "resetprop -w sys.boot_completed 0" before starting the daemon be problematic? I've checked and it stops a system_server crash during boot (for whatever reason) from causing TEESIM problems reading installed packages, but not sure whether there are good reasons for starting the daemon before this? That said, it's only a small delay if it crashes and restarts, and if it fails to fully load and get to "boot completed" then a system reboot will be required anyway. I've put through a PR which you are welcome to reject if this is a bad idea 😊

[poqdavid]

A Vector Xposed module is crashing the system_server, over Samsung's SemWallpaperThemeManager.

Please disable that module, and test TEESimulator again.

Which one i only use two one is KnoxPatch and another one is XPL-EX
And how do i figure out?

[JingMatrix]

@poqdavid Test them one by one, since you only have two.

[poqdavid]

@poqdavid Test them one by one, since you only have two.

So i did a test and i noticed this error happens right when i install the teesim 4 module and reboot and from what i noticed it seems to be the XPL-EX
And with a second reboot it seems to be just fine

[poqdavid]

is it possible to fix the crashes from module side cause i can't really disable XPL-EX

[gavdoc38]

is it possible to fix the crashes from module side cause i can't really disable XPL-EX

For now, as a simple workaround, try modifying /data/adb/modules/teesim/service.sh

as per this:

9baf40c

[JingMatrix]

@poqdavid Please report the module error on my Vector repo with debug logs, so that I can see what happened there.

[poqdavid]

@poqdavid Please report the module error on my Vector repo with debug logs, so that I can see what happened there.

I just installed the debug version of the Vector and tried to trigger the bug a few times by reinstalling teesim a few times and rebooting but it seems like its not happening anymore yet