The normal flow
Registration and login use the same mechanism. You enter a mobile number, the app sends a one-time code, you enter the code, and a session is created and bound to that device. Some builds add a password, and some ask for an invitation code during first registration.
- Enter the number in full. A missing or duplicated country code is the most common cause of a code that never arrives.
- Wait out the timer. Requesting a new code before the cooldown expires frequently invalidates the one already in flight.
- Set a password you use nowhere else. If the app offers one, this is the moment to isolate it from the rest of your accounts.
What a session actually is
The token stored after verification identifies your device, not just your account. That is why clearing app data, restoring a backup to a new phone, or installing a different build all end the session. None of these indicate a problem with your account.
Common failures and their real causes
Login problems in this ecosystem are usually environmental. Working through them in order saves a lot of time.
- Endless loading on submit. Almost always connectivity. Switch between mobile data and wi-fi before concluding anything else.
- Code rejected as invalid. Either it expired, or a newer code superseded it. Use only the most recent one.
- Immediate logout after signing in. Often a device clock that has drifted far enough to invalidate the token.
- Number already registered. An earlier registration exists, possibly from a different build using the same backend.
The login scams to expect
Because access is gated by a single code, the code is what attackers want. The approaches are formulaic and recognisable once you have seen them described.
- The support impersonator. Someone contacts you about a bonus or a problem and needs the code to proceed. No genuine operator ever needs it.
- The mirror login page. A link in a chat group opens a convincing login form that harvests whatever you type. Log in inside the app only.
- The helper tool. An app or script that offers to manage logins or predict outcomes and asks for your credentials to do it.
One rule handles all three: a code is a key. Anyone asking you to hand over a key is asking to enter, whatever explanation accompanies the request.
Frequently asked questions
My verification code never arrives. What now?
Check signal and any SMS filtering first, confirm the number including country code, then wait out the resend cooldown rather than requesting repeatedly — rapid resends often trigger a temporary block.
Why am I logged out after every update?
Sessions are usually tied to the installed build and the device. Reinstalling or updating replaces that binding, so a fresh verification is expected behaviour rather than a fault.
Can support recover my account without a code?
Legitimate support does not ask for your one-time code, and anyone who does is not support. Recovery normally runs through the registered number itself.
Should I use the same password as my email?
No. Treat any credential entered into a sideloaded app as potentially exposed, and make sure a compromise there cannot reach anything else you own.