a86a0a45bd
Drops `/.well-known/assetlinks.json` so the Trusted Web Activity APK (dev.velxio.twa, generated by bubblewrap from this same manifest.webmanifest) can prove to Chrome that it's allowed to claim velxio.dev as its own origin. Without this file the TWA falls back to a Custom Tab with the URL bar visible — losing the whole "feels native" UX that TWAs exist for. The sha256_cert_fingerprints entry pins the production signing key held locally as android.keystore in the velxio-twa/ build dir (NOT in any repo). If we ever lose that key + need to re-issue, this file has to be updated with the new fingerprint and re-deployed BEFORE the new APK reaches users; otherwise their previously- installed TWA verifies against an asset link that no longer matches the APK signature and breaks. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| .well-known | ||
| boards | ||
| component-svgs | ||
| examples-thumbs | ||
| firmware | ||
| fonts | ||
| marketing | ||
| wasm/ngspice-interactive | ||
| android-chrome-192.png | ||
| android-chrome-512.png | ||
| apple-touch-icon.png | ||
| components-metadata.json | ||
| favicon-16x16.png | ||
| favicon-32x32.png | ||
| favicon-48x48.png | ||
| favicon.ico | ||
| favicon.svg | ||
| image.png | ||
| image.webp | ||
| manifest.webmanifest | ||
| og-image.png | ||
| og-image.svg | ||
| robots.txt | ||
| sitemap.xml | ||
| vite.svg | ||
