5 min read
Save the visible facts before changing the screen
If a Crash screen freezes, first note the round reference if visible, the time and time zone, and the exact message. Distinguish a stopped animation from an explicit “disconnected” or “request failed” message. They are different observations. Save a screenshot when practical, with no passwords, OTPs or unrelated private notifications included.
Also write down what you did immediately before the problem: opened the game, requested an entry, tapped cash out or returned from another app. “Tapped cash out, no confirmation appeared, then the image stopped” gives support a sequence to investigate. It does not assert that the exit was accepted, rejected or even received by the service.
Separate screen, connection and result
A screen is the information your device is displaying. A connection carries requests and updates. A settled entry is the result recorded under the game’s rules. A problem in the first two does not tell you what the third contains. The final multiplier still visible on a stalled screen may simply be the last update your phone received.
Do not treat repeated taps as proof that a request has gone through. A reconnect can show a newer round while leaving your earlier entry unresolved on screen. When the service becomes readable again, match the original round identifier and your own entry. Avoid using another player’s result or the latest history value as a substitute.
- Save what is visible
Round reference, exact message, time and time zone. Note your last action.
- Check the connection separately
After saving the facts, see whether an ordinary webpage loads. This does not settle the game entry.
- Match the original entry
After reconnecting, find the same round and read its pending, accepted or settled status.
- Report an unresolved mismatch
Send the sequence and reference through the product’s support route, with private details hidden.
Reconnecting, refreshing or tapping again cannot by itself prove that an earlier cash-out request was accepted.
Make a small network check outside the round
Once you have saved the available facts, check whether an ordinary webpage loads on the same connection. If it does not, the issue may extend beyond the game. Google’s Android guidance suggests comparing Wi-Fi and mobile data when diagnosing internet problems. Do this as a connection check after recording the issue, not as a technique for rescuing an active entry.
If other pages work but the game does not, record that comparison. It narrows the description without proving the cause: an app, session or service can fail while general browsing works. Network changes can also interrupt a session. Do not uninstall the app, clear its data or reset the phone as a first response to a single unresolved round.
Read the interruption rule before assuming a refund
Different products can handle accepted entries, failed requests and interrupted rounds differently. Read the installed game’s interruption policy and the final status. A disconnection by itself does not establish that an entry was cancelled, refunded or cashed out. An automatic target visible earlier also does not prove how the service handled it during the interruption.
The UK Gambling Commission’s RTS 10 discusses interruption policies and recovery for services within its remit. We cite it as an example of the information a policy should address, not a rule that this site can apply to Master Crash. We have not independently tested the linked APK’s handling of connection failures, and cannot promise a particular settlement.
Send one record with the sequence of events
A concise report can read: “Round R-204, 13 October at 20:14 IST. I requested cash out; no confirmation appeared. The app showed a connection message. After reconnecting, my entry is still pending.” Add the device model, Android version and whether you were using Wi-Fi or mobile data. The example reference is fictional; replace it with the identifier shown in your own record.
Ask for the accepted entry status and settled result to be checked against the round. Use the support route shown by the product, and keep the case reference with any replies. If a result later appears, add that new fact to the same report. Do not open several unrelated reports containing different guesses about the outcome.
Keep recovery separate from account secrets
A person investigating a round does not need your OTP, password or payment PIN in a screenshot. Hide full identity documents and unrelated balances. Do not install a remote-control tool or send a transfer because someone says it will release a frozen result. Verify unexpected requests through a separate contact route already shown by the product.
A later successful connection only confirms that you can connect now; it does not resolve the earlier record. Keep the unresolved entry visible in your notes until the product supplies a clear status. This guide helps organise the checks and evidence. It cannot access the game’s records, reverse a result or guarantee that any troubleshooting step will fix it.
Two clocks do not measure request delay
A screenshot might show 10:05 on the phone while an entry row shows 10:04. Those labels may refer to different events, time zones or levels of precision. Subtracting them does not establish a one-minute network delay. The capture clock says when the image was taken; the record clock needs its own label. Neither necessarily gives the time at which a cash-out request reached the service.
Example note: “Captured at 10:05 on my device. The entry row displays 10:04; its time zone and event label are not shown. Round R-41 is still marked pending.”
This preserves what was visible without inventing a transmission time. Include seconds only if actually displayed, and do not adjust a screenshot’s timestamp to make two records agree. A support request can ask which event the record time represents.
Sources and scope
- Google Android Help — internet connection checks
- UK Gambling Commission — RTS 10: interrupted gambling (background, not Master Crash policy)
- Crash round history
- Prepare a support request
Product-specific controls remain subject to the installed app. Illustrations are explanatory and do not represent measured game results or genuine app screenshots.
