c-fu/arah2
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(03-04): log debug round 4 — settings CTA on the wrong instance

Browse Source
This commit is contained in:
araharah-executor
2026-10-23 01:19:41 +08:00
parent 38ce59b1ca
commit de07c99e8a
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.planning/phases/03-mini-app-shell-geolocation/03-DEVICE-MATRIX.md
+12
View File
@@ -171,3 +171,15 @@ Erratum recorded in 03-RESEARCH.md.
**Re-test:** restart Telegram client, reopen web app from the menu button — **Re-test:** restart Telegram client, reopen web app from the menu button —
expect the REAL boot (BOT-01 → BOT-02 → LIVE with an actual permission ask or expect the REAL boot (BOT-01 → BOT-02 → LIVE with an actual permission ask or
a live LocationManager read + LOCATION SETTINGS available on denial). a live LocationManager read + LOCATION SETTINGS available on denial).
## 2026-10-23 debug round 4 (missing LOCATION SETTINGS on the main denied card)
**Symptom:** user still sees only TRY AGAIN / ASK VIA CHAT — no LOCATION SETTINGS.
**Root cause:** executor patch-order bug — round 2 attached
`withLocationSettings` only to the awaiting-pin card instance; the primary
denied card (the one shown at denial) never got the CTA.
**Fix (deploy `253d7a3e`):** both denied-shaped instances now build with the
Telegram-only settings CTA. Deployed `index.html` verified to carry
telegram-web-app.js (round 3 fix verified live via curl).