Skip to content

Verify published Android APKs and desktop binaries through native interaction - #3

Open
toZyn wants to merge 10 commits into
mainfrom
fix/distribution-validation
Open

toZyn wants to merge 10 commits into
mainfrom
fix/distribution-validation

Conversation

@toZyn

@toZyn toZyn commented Oct 4, 2026 •

Copy link
Copy Markdown
Owner

Adds a distribution check workflow that downloads assets for the exact release source commit, verifies GitHub's SHA-256 digest, and compares every shipped runtime file with the source checkout.

The game is launched from the published Linux AppImage/portable bundle, Windows x64/x86 executable, and universal/ARM64/ARMv7 signed APKs. Native input navigates title, main menu, Freeplay and a song. Desktop checks require a clean native shutdown. Android 11 emulator checks require the same process and a new PlayState diagnostic after returning from the background; shared-storage folders and .nomedia must exist. Screenshots and diagnostics are retained for visual input/pause review.

The separate signed overlay companion runs on an Android 15 emulator: consent/cancel, display above home, dragging, close, token-scoped hide and permission revocation. Windows also exercises the real desktop companion windows.

The underlying fast-tap regression and archive cleanup were fixed and merged in PR #4; these checks target release 0.1.16-advanced.7 built from 4c35ae0.

@toZyn toZyn changed the title Verify released desktop binaries and signed Android APKs in an emulator Verify published Android APKs and desktop binaries through native interaction Oct 4, 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.

1 participant