diff --git a/docs/functionyard/fxblox-app.md b/docs/functionyard/fxblox-app.md index 0d1d780..8645f93 100644 --- a/docs/functionyard/fxblox-app.md +++ b/docs/functionyard/fxblox-app.md @@ -67,9 +67,9 @@ After you approve in MetaMask — or any other wallet — and return to the FxBl :::tip Wallet opened but stuck on its splash screen? This happens on Android, most often on the first signature right after connecting: MetaMask comes to the front and then sits on its splash screen without ever showing the prompt. -**Close MetaMask completely from your recent apps**, return to the FxBlox tab, and tap **Open wallet to approve**. That is the step that clears it — tapping the button again *without* closing MetaMask first will simply open it back onto the same stuck screen. Your signature request stays valid throughout, so nothing is lost and you do not need to start setup again. +**Close MetaMask completely from your recent apps, then open it again** — from its icon, or by returning to the FxBlox tab and tapping **Open wallet to approve**. A freshly started MetaMask shows the waiting request straight away. Opening it again *without* closing it first only returns you to the same stuck screen. Your signature request stays valid throughout, so nothing is lost and you do not need to start setup again. -**If it happens every time, fix the cause:** Android is restricting MetaMask in the background, so it is suspended or killed the moment you switch away, and a wallet resumed from that state cannot handle the request it is being opened for. Go to **Settings → Apps → MetaMask → Battery** and choose **Unrestricted**; do the same for your browser (Chrome or Edge). This is the same setting the mobile FxBlox app always needed for the connect and sign prompts to appear, and with it in place the wallet comes forward already showing the prompt. A web page cannot change it for you. +This is a fault inside the MetaMask app — it cannot resume properly from the background on some phones — and a web page cannot reach into it. If it happens every time, check that MetaMask is up to date, and look at **MetaMask → Settings → Security & Privacy → Auto-lock**: a very short auto-lock puts every resume through the lock screen, which is where this tends to bite. ::: ### 4. Connect to your Blox @@ -177,7 +177,7 @@ The Blox reconnects to the network and saves chain history automatically. - **On Android**, the browser needs the location / nearby-devices permission before it can scan for Bluetooth devices. - **The page still says "Connecting Wallet…" after you approved.** Give it a second or two. The browser's connection is suspended while you are away in your wallet; the app reconnects when you return and then sees the approval. Do not tap again or reload — that cancels the request you just approved. - **The wallet does not come back after signing.** Switch back to the FxBlox tab yourself. If MetaMask is stuck on its splash screen, close it fully from your recent apps and then tap **Open wallet to approve** — tapping without closing it first only returns you to the same stuck screen. The signature request stays valid either way. -- **MetaMask sticks on its splash screen every time.** Android is restricting it in the background. Set **MetaMask** and your **browser** to **Unrestricted** under **Settings → Apps → (app) → Battery**. See the tip under [Set your identity](#3-set-your-identity). +- **MetaMask sticks on its splash screen every time.** It is failing to resume from the background — a MetaMask fault, not something the page controls. Closing it from recent apps and opening it again always clears it. Check MetaMask is up to date and look at its **Auto-lock** setting; see the tip under [Set your identity](#3-set-your-identity). - **Connection problems at the final step.** Connect to the same Wi-Fi as the Blox, reload the page, and use **Reconnect to existing blox**. If that does not work, restart the Blox, wait for the flashing light blue, and set it up again. - **Starting completely over.** The browser equivalent of uninstalling and reinstalling the app is **Clear app storage** on the *Set identity* screen. It deletes everything FxBlox stored in this browser — identity, Blox list, settings and caches — and reloads the page. - **Nothing loads after a new release.** Reload the tab. If a "new version available" prompt appears, accept it. diff --git a/docs/functionyard/troubleshooting/switch-chain.md b/docs/functionyard/troubleshooting/switch-chain.md index 83290a4..321664d 100644 --- a/docs/functionyard/troubleshooting/switch-chain.md +++ b/docs/functionyard/troubleshooting/switch-chain.md @@ -85,7 +85,7 @@ On a phone, the browser's connection to your wallet is suspended while you are a ### MetaMask Connection Problems - **Give it a few seconds first** if the app still says "Connecting Wallet…" after you came back from MetaMask — on a phone the page catches up a little after you do, and tapping again in the meantime cancels what you just approved - **On Android, if MetaMask opens and sits on its splash screen**, close it completely from your recent apps before coming back and tapping again — tapping without closing it first only returns you to the same stuck screen -- **If that happens every time**, Android is restricting MetaMask in the background: set MetaMask and your browser to **Unrestricted** under **Settings → Apps → (app) → Battery** +- **If that happens every time**, MetaMask is failing to resume from the background on your phone — closing it from recent apps and opening it again always clears it; check it is up to date and look at its **Auto-lock** setting - **Refresh the MetaMask extension** if it appears unresponsive - **Check MetaMask permissions** for the FxBlox app - **Try using a different browser** if issues persist