Skip to content

Removed - #1

Closed
amarinne wants to merge 1 commit into
mainfrom
release/v0.4.156
Closed

amarinne wants to merge 1 commit into
mainfrom
release/v0.4.156

Conversation

@amarinne

@amarinne amarinne commented Aug 16, 2026 •

Copy link
Copy Markdown
Owner

No description provided.

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. Requiring the installed base APK hash to equal the hash a
symbol profile was mapped from rejected those installs outright and left
every feature disabled while the symbol schema still reported valid.

Compatibility now matches on exact versionCode plus the Zalo signing
certificate, and records the container hash as evidence with a match
tier. The install identity, which covers splits, install path and install
time, became a re-check trigger rather than a gate, so adding an
on-demand feature split no longer disarms features.

A Zalo version with no bundled profile now records which anchor families
resolve, without hooking anything.

Self-check detail and error text stay out of diagnostic reports, per the
reporting spec.
Copilot AI lite review requested due to automatic review settings August 16, 2026 22:50
@amarinne amarinne closed this Aug 16, 2026
@amarinne
amarinne deleted the release/v0.4.156 branch August 16, 2026 22:52

Copilot AI left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.

Comment on lines +198 to +201
int separator = error.indexOf(": ");
if (separator <= 0) {
return error;
}
@amarinne amarinne changed the title Match Zalo installs on versionCode and signing certificate Removed Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants