Identify the last step that worked
- No completed file: start with download help.
- Android rejected installation: choose an installer symptom.
- The app closes before sign-in: record the launch failure and installed release.
- The app stays open but rejects access: record the exact sign-in message and the method being used.
These are different failure stages. A login message is not evidence that the APK transfer failed or that an older file is needed.
Use low-impact checks first
- Read the whole message. Distinguish a connection issue, rejected credentials, an unavailable service and an account restriction.
- Check ordinary connectivity. Confirm that the phone has normal internet access. For a service-status notice, use a publisher channel you can identify.
- Use the account’s established method. Follow the recovery options actually offered by that release. Do not substitute a new account if preserving progress matters.
- Keep the current app data. Record recovery details before considering steps that remove local state.
If the app offers a verification code
Use only the verification flow that the app actually presents. Check the destination shown there and follow any displayed wait or resend instructions; this guide does not invent a universal timer or claim that every release uses OTP sign-in.
Keep the code private. A person claiming to be support does not need your password or OTP to read an error description. Use a channel identified from the app or its established publisher source.
Prepare the details that can be acted on
- Phone model and Android version.
- Installed app version and the step where access fails.
- Exact message, excluding credentials and private account data.
- Whether the app closes or remains open at the sign-in screen.
Use the local support-note builder to organise the text. It does not send a ticket or access the game account. If an update is proposed, follow the release and recovery workflow.