docs: say that the page lags behind the wallet on the way back, and to wait it out - #177
Merged
Conversation
…o wait it out Every wallet round-trip on a phone -- signing the identity, adding a chain, switching to one -- ends the same way: the user approves in MetaMask, comes back, and the tab still says "Connecting Wallet...". Android suspends the browser's connection while it is in the background, so the page only sees the approval once that connection is re-established. Nothing here said so, and the natural reaction is to tap again or reload -- which cancels the request they just approved and sends them round the loop a second time. So: an admonition at "Set your identity", one at the return step of both chain-switch walkthroughs, and troubleshooting entries in both places. Each says the same two things -- this is expected, and helping makes it worse. Also brings the stuck-wallet advice in line with what the app now tells you. The app leads with "tap Open wallet to approve again" and only falls back to the force-quit; the docs led with the force-quit, which is the heavier step and skips straight past the cheap one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BpqXrkEPA9odTyRdK5Mnx
ehsan6sha
added a commit
that referenced
this pull request
Sep 4, 2026
…178) #177 reordered the stuck-wallet advice to lead with "tap Open wallet to approve again", on the theory -- shipped alongside it in functionland/fxblox-web#33 -- that a second tap opened the wallet a different way and would usually get past the splash screen. Tested on a phone since: it does not. A warm MetaMask hangs on the retry exactly as it hangs on the first attempt. Only closing MetaMask from recents and then tapping clears it, which is what these pages said before #177 and what functionland/fxblox-web#35 puts back in the app's own hint. So the force-quit leads again, and each place now says plainly that tapping without closing the wallet first returns you to the same stuck screen -- the thing a user will otherwise try twice before giving up. Also says where the fault is: inside the wallet app, where a web page cannot reach. The "give the page a few seconds when you come back" guidance from #177 is untouched -- that part was about our own reconnect and is still right. Claude-Session: https://claude.ai/code/session_013BpqXrkEPA9odTyRdK5Mnx Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Every wallet round-trip on a phone — signing the identity, adding a chain, switching to one — ends the same way: you approve in MetaMask, come back to the tab, and it still says Connecting Wallet…. Android suspends the browser's connection while it is in the background, so the page only sees your approval once that connection has been re-established.
Nothing in the docs said so. The natural reaction is to tap the button again or reload — and that cancels the request you just approved, sending you round the loop a second time.
What changed
Also: the stuck-wallet advice now matches the app
The app's own hint used to lead with "close it from your recent apps"; as of functionland/fxblox-web#33 it leads with "tap Open wallet to approve again" and keeps the force-quit as the fallback, because the second tap now opens the wallet a different way. The docs still led with the force-quit — the heavier step, and the one that skips straight past the cheap fix. Both pages now follow the app.
Testing
npm run buildpasses. The config hasonBrokenLinks: "throw", so the new#3-set-your-identityanchors are verified by the build. TheComponent Note was not importedwarnings are pre-existing and come from other pages.🤖 Generated with Claude Code
https://claude.ai/code/session_013BpqXrkEPA9odTyRdK5Mnx