docs: serve the Android demo from a release asset, not an expiring EAS link - #23
Merged
Merged
Conversation
…S link The README's "Install the Android demo" link pointed at an EAS internal-distribution build. Those artifacts are kept 30 days and that one was built 2026-08-27, so it expired on 09-10 and the APK behind it has been returning 404 since. The build *page* still returns 200, which is why a link check wouldn't have caught it — only fetching the artifact does. Rebuilt from 554a96e and published it as a GitHub release asset instead (demo-android-v1). A release asset doesn't expire and needs no Expo account, which matters more now that this link is the main call to action for anyone arriving from a post or article. Same signing key as the expired build (cert SHA-256 4fe3f6d5...90ac), so it installs over it rather than needing an uninstall. Verified the README's exact download URL serves the built bytes: 63954196 both sides, matching SHA-256 over the zip central directory. Also bump versionCode 1 -> 2. Android refuses to install over an installed APK with a lower code and there's no store to enforce ordering for an unlisted build, so this has to climb by hand. Note it lives here and not in app.json: EAS ignores app.json's values outright because this native android/ directory exists.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The problem
The README's Install the Android demo link has been broken since 2026-09-10.
It pointed at an EAS internal-distribution build. Expo keeps those artifacts 30 days; that build was made 2026-08-27, so the APK now 404s:
The build page still returns 200, so a link checker sees nothing wrong — only fetching the artifact reveals it. That link is the main call to action for anyone arriving from a launch post, so it matters more than a typical doc link.
The fix
Rebuilt from
554a96eand published the APK as a GitHub release asset —demo-android-v1. Release assets don't expire and need no Expo account.The release notes state explicitly that this is the demo app and not an SDK release, so the repo's first tag can't be misread as "blynk-deferlink 1.0".
Verified, not assumed
4fe3f6d5…90ac— identical, installs as an upgradedev.blynkdeferlink.demo200,application/vnd.android.package-archiveThe full round-trip download exceeded the 2-minute command limit, so integrity was checked by exact size plus a hash of the archive tail, which is the region that changes if any entry differs.
Also: versionCode 1 → 2
Android refuses to install an APK over an installed one with a lower version code, and an unlisted APK has no store to enforce ordering. Equal codes still reinstall, which is why shipping
1twice caused no trouble — but a third at1would have been refused.This lives in
android/app/build.gradle, notapp.json: EAS ignoresapp.json's values outright because a nativeandroid/directory exists, and says so in the build log. The released asset stays at code1— that's what was built and signed; relabelling a shipped binary would make the release misdescribe its own contents.