Fixed — Zalo installs whose base APK container differs from the one a symbol profile was mapped from were rejected outright, disabling every feature while the symbol schema still reported valid. Google Play serves per-device bundle variants and re-stamps its signing block per download, so one Zalo release has several base APK hashes over identical code. Compatibility now matches on exact versionCode plus the Zalo signing certificate, with the container hash recorded as evidence.
Fixed — Adding an on-demand Zalo feature split, or reinstalling Zalo, no longer disarms features until a background re-check runs.
Added — On a Zalo version with no bundled profile, the module records which anchor families resolve, without hooking anything.
Privacy — Self-check detail and error text are excluded from diagnostic reports.
Known limits — Verified on one device. The multi-container path is covered by tests, not yet by hardware. The signed symbol catalog is still keyed by base APK hash, so symbol-only compatibility updates cannot yet reach installs with a different container; those rely on bundled profiles, which currently cover Zalo 26.06.02, 26.07.01 and 26.08.01.
APK SHA-256 c2ecdf315cc153e1c4f3c21b8cea5b3367f917f3cbca719ff3bd76f39a3fee45