You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Publish production-safe native link associations and fallbacks - #19
Remote key exchange links currently reach the website without published app associations. This change serves iOS and Android association files and separate static production/development fallbacks, so supported installed apps can claim their links while browser visitors receive the appropriate instructions.
Production Android trust includes the independently recorded standalone APK and Play App Signing certificates. Public debug signing trust is excluded; Android development links use coordinator instructions instead of advertising incompatible store apps. iOS production/development app identities and paths are preserved. Explicit JSON routes use Vercel's existing legacy routing configuration without mixing top-level routing fields.
Validation on the final correction: five source/certificate/routing tests passed, zero skipped, against submitted mobile source 1d8a86a7462d935cbd0e28b857934b5718c152fc; pinned pnpm10.4.1 frozen install; TypeScript and production build passed; @vercel/routing-utils6.6.0 validation passed; both built association files and both fallbacks match source bytes. Package and lockfile are unchanged. Fresh independent source review found no blocking findings across the complete PR delta.
The earlier local patch374fd05... was unavailable. This is a freshly reconstructed and independently reviewed correction (patch SHA256e10cbc00b2288c0287b0dd706ea2e6174a6867f9582271054273ce02029c2c2b), without claiming inherited review of that missing artifact.
Publication uses the existing GitHub main-to-Vercel production integration under the user's22 October R4 instruction to proceed. Hosted source/preview checks passed on4da972aff8248f09acfd7949bfbfb01e473cdbbf. PR19 merged asa9caa24e8e02f7bcce8b5e1c6d7c2ac687d385a4; Vercel Production7244208812 succeeded. Follow-up PR20 adds a read-only post-deployment HTTP check; final website source ddba13b, Vercel Production7244276168. Strict public acceptance39726344502 passed8/8 at22 Oct05:08:54UTC: direct JSON200/no redirects, both association and both fallback bytes exactly match source; HTML fallbacks, malformed404s and normal pages pass. Receipt: https://github.com/KeeperCommunity/bitcoin-keeper-website/actions/runs/39726344502 . Installed iOS/Android cold/warm association, phone-to-Desktop pairing and hardware acceptance remain open; cloud checks do not replace them.
State: NEEDS_LOCAL
PR: #19
Base: main
Head branch: codex/r4-native-links-site
Head commit: 56ae397
Goal and acceptance criteria: Valid production/development remote-key links open the correct installed app on iOS and Android; browser fallback stays generic and does not disclose the key.
Changes made: Direct AASA/assetlinks files and generic noindex remote-link fallback.
Cloud checks: native-links Node tests 3/3 passed on 12 October; www AASA/assetlinks and both valid dummy remote paths still returned 404. Preview's recorded Vercel status is successful, but this continuation did not bypass protection or claim preview/device acceptance.
Required local checks: IOS, ANDROID
Local checks requested: First verify a separately approved deployment gives direct HTTPS 200/application-json/no redirect for both association files and 200 generic fallback for valid dummy remote paths. Read actual iOS entitlement/appID and Android applicationId/signing SHA256 from the exact test builds; confirm against AASA/assetlinks, including authenticated Play App Signing certificate and eventual 2.6.4 production artifact. Use installed isolated development apps with disposable remote keys; exercise cold/warm start, app absent/present, malformed/extra-segment path, default browser and link return-to-app. Confirm browser shows no key and logs/screenshots contain no real key. Recheck network selection and remote-key ownership across account switch. Record IOS/ANDROID outcomes, service/website build identity and actual tested mobile SHA.
Risks / known gaps: Hosting approval/deployment, production/Play fingerprints and source approval are open. Current production 404 blocks live association acceptance. Do not replace the owner's app or use their wallet data.
antuz123
changed the title
R4: associate native remote links and serve safe browser fallback
Publish production-safe native link associations and fallbacks
Oct 22, 2026
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
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.
Remote key exchange links currently reach the website without published app associations. This change serves iOS and Android association files and separate static production/development fallbacks, so supported installed apps can claim their links while browser visitors receive the appropriate instructions.
Production Android trust includes the independently recorded standalone APK and Play App Signing certificates. Public debug signing trust is excluded; Android development links use coordinator instructions instead of advertising incompatible store apps. iOS production/development app identities and paths are preserved. Explicit JSON routes use Vercel's existing legacy routing configuration without mixing top-level routing fields.
Validation on the final correction: five source/certificate/routing tests passed, zero skipped, against submitted mobile source 1d8a86a7462d935cbd0e28b857934b5718c152fc; pinned pnpm10.4.1 frozen install; TypeScript and production build passed; @vercel/routing-utils6.6.0 validation passed; both built association files and both fallbacks match source bytes. Package and lockfile are unchanged. Fresh independent source review found no blocking findings across the complete PR delta.
The earlier local patch374fd05... was unavailable. This is a freshly reconstructed and independently reviewed correction (patch SHA256e10cbc00b2288c0287b0dd706ea2e6174a6867f9582271054273ce02029c2c2b), without claiming inherited review of that missing artifact.
Publication uses the existing GitHub main-to-Vercel production integration under the user's22 October R4 instruction to proceed. Hosted source/preview checks passed on4da972aff8248f09acfd7949bfbfb01e473cdbbf. PR19 merged asa9caa24e8e02f7bcce8b5e1c6d7c2ac687d385a4; Vercel Production7244208812 succeeded. Follow-up PR20 adds a read-only post-deployment HTTP check; final website source ddba13b, Vercel Production7244276168. Strict public acceptance39726344502 passed8/8 at22 Oct05:08:54UTC: direct JSON200/no redirects, both association and both fallback bytes exactly match source; HTML fallbacks, malformed404s and normal pages pass. Receipt: https://github.com/KeeperCommunity/bitcoin-keeper-website/actions/runs/39726344502 . Installed iOS/Android cold/warm association, phone-to-Desktop pairing and hardware acceptance remain open; cloud checks do not replace them.