chore(ui): on-screen GCG export diagnostic (Android in-app WebView) #150
Reference in New Issue
Block a user
Delete Branch "feature/gcg-export-diagnostic"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Temporary diagnostic, not a fix — to learn why GCG export silently does nothing on Android Telegram/VK in-app WebViews (no devtools there). You picked diagnostic-first.
On the contour, open a finished game → history → Export GCG on your Android Telegram/VK. Instead of (silently) sharing/downloading, a dark on-screen panel shows:
channel/insideVK/uanavigator.share/navigator.canSharepresent?canShare({files})→ true/false (the crux)decision→ share | downloadshare(): resolved/share(): rejected — <err>/download(): anchor click issued, no throwTap Share to send me the panel text, or screenshot it. Tap anywhere else to dismiss. That reading tells us which branch dies, and I ship the targeted fix (then revert this).
Self-contained (Game.svelte + a probe in share.ts), clearly marked TEMPORARY. Verified:
pnpm check(0/0), unit (356), build, e2e (160).TEMPORARY diagnostic to find why GCG export silently does nothing on Android Telegram/VK in-app WebViews, where there is no developer console to read. Tapping Export now probes the delivery path — navigator.share / canShare presence, canShare({files}), the share-vs-download decision — performs the real attempt and captures its outcome, then renders it all in an on-screen overlay (with a Share control to send the report back). No fix yet by design (owner chose diagnostic-first): once the on-device readings come back, this is replaced by the targeted Android delivery fix.Superseded by #151 — the real fix (clipboard copy on Android in-app WebViews). The diagnostic did its job: your readings confirmed no
navigator.share/canShareon Android Telegram+VK. Closing.Pull request closed