Skip to content

docs: name the battery restriction behind a wallet that wedges every time, and shorten the wait - #179

Merged
ehsan6sha merged 1 commit into
mainfrom
docs/wallet-battery-restriction
Sep 4, 2026
Merged

docs: name the battery restriction behind a wallet that wedges every time, and shorten the wait#179
ehsan6sha merged 1 commit into
mainfrom
docs/wallet-battery-restriction

Conversation

@ehsan6sha

Copy link
Copy Markdown
Member

Two updates to the wallet hand-off guidance, both tied to functionland/fxblox-web#36.

The wait after returning is now short, and the docs say so

The "give the page a few seconds" note becomes "a second or two". The app now restarts its relay socket the moment the tab comes back from a wallet, rather than trusting a socket that only claims to be open, so the approval is fetched at once instead of after Chrome's TCP stack notices. The advice not to tap again or reload in the meantime stands — that still cancels the request.

What to do when MetaMask wedges on its splash screen every time

The stuck-wallet tip now names the cause: Android restricting MetaMask in the background, so it is suspended or killed on every switch away and cannot handle the request it is resumed for. The fix is Settings → Apps → MetaMask → Battery → Unrestricted, and the same for the browser.

This is the setting the mobile FxBlox app always needed for the same prompts — the legacy section at the bottom of the page has said so for a long time — and the web app is subject to it in exactly the same way. A web page cannot change it for the user, so the page has to tell them.

Same line added to the troubleshooting list on that page and to Switch Chain Troubleshooting.

Testing

npm run build passes; onBrokenLinks: "throw" still covers the anchors.

🤖 Generated with Claude Code

https://claude.ai/code/session_013BpqXrkEPA9odTyRdK5Mnx

…time, and shorten the wait

Two updates to the wallet hand-off guidance.

The "give the page a few seconds" note now says "a second or two". As of
functionland/fxblox-web#36 the app restarts its relay socket the moment the tab
comes back from a wallet rather than trusting a socket that only claims to be
open, so the approval is fetched at once instead of after Chrome's TCP stack
notices. The advice not to tap again or reload in the meantime stands.

The stuck-splash-screen tip now says what to do when it happens EVERY time:
Android is restricting MetaMask in the background, so it is suspended or killed
on every switch away and cannot handle the request it is resumed for. Settings >
Apps > MetaMask > Battery > Unrestricted, and the same for the browser. This is
the setting the mobile FxBlox app always needed for the same prompts -- the
legacy section of this page has said so for a long time -- and the web app is
subject to it in exactly the same way. A web page cannot change it for the user,
so the page has to tell them.

Same line added to the troubleshooting list and to Switch Chain Troubleshooting.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013BpqXrkEPA9odTyRdK5Mnx
@ehsan6sha
ehsan6sha merged commit c3e839e into main Sep 4, 2026
1 check passed
@ehsan6sha
ehsan6sha deleted the docs/wallet-battery-restriction branch September 4, 2026 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant