Skip to content

maps(com.tranzmate): record signer_sha256 from device - #67

Merged
Xiddoc merged 1 commit into
masterfrom
claude/signer-sha-tranzmate
Jul 6, 2026
Merged

maps(com.tranzmate): record signer_sha256 from device#67
Xiddoc merged 1 commit into
masterfrom
claude/signer-sha-tranzmate

Conversation

@Xiddoc

@Xiddoc Xiddoc commented Jul 6, 2026

Copy link
Copy Markdown
Owner

What

Adds signer_sha256: c42f9060274bc622dd53d1ac25dc1c0167c3023ec3d87649c3c9ec10e3ad7db0 to both published com.tranzmate maps (1785.json, 1789.json), which previously recorded no signing cert.

Why

The maps carried no signer_sha256, so clients had no version-guard against applying them to the wrong app build. The value was read off the installed base APK with apksigner verify --print-certs (single signing certificate, no key rotation), which is exactly the canonical colon-free lowercase-hex form the field requires. The signing cert is the same for both version_codes.

Testing

  • scripts/validate_map_semantics.pyok on both files (self-test passes)
  • check-jsonschema --schemafile schema/rosetta-map.schema.jsonok -- validation done

🤖 Generated with Claude Code

https://claude.ai/code/session_01QXorW4zR6ABUWH5Ev4pMug


Generated by Claude Code

Read off the installed base APK via apksigner (single signing cert, no
rotation). Same cert across both published version_codes. Verified with the
schema + semantic validators locally.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QXorW4zR6ABUWH5Ev4pMug
@Xiddoc
Xiddoc merged commit b0dc177 into master Jul 6, 2026
1 check passed
@Xiddoc
Xiddoc deleted the claude/signer-sha-tranzmate branch July 6, 2026 10:58
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