This guide covers the window after you trust the install: permissions prompts, mobile verification, and staying signed in on Indian networks. Package and listing forensics stay on the download checklist; once you are past the gate, compare app workflow covers squad screens and lock behaviour.
Most readers pause on three checks: the app identity matches what they expected from the store or file source, the OS permission sheet lists sensible scopes (not a grab bag unrelated to fantasy play), and the first screen is a branded flow—not a generic WebView login with no operator cues. If the first two fail, stop and return to install forensics; if they pass, you are in login territory. After a clean entry, lineup and lock UX is the next layer to stress-test.
OTP delivery often needs read permissions on some Android builds; the question is whether the prompt explains the use and whether you can revoke later without bricking the session. If the sheet looks nothing like what the install checklist prepared you for, treat it as a package-trust signal first.
Unrelated device admin requests, overlay capture, or contacts scraping are red flags for any fantasy product—log the screen name and bail to support channels you trust.
Indian carriers and SMS gateways jitter during peak hours; a 30–60 second wait is common. Retry caps and clear “resend after” timers reduce guesswork. Rule out a stale build first—re-check install forensics and update—before blaming only SMS or the handset. If OTPs never arrive across two numbers and two networks, split the problem: SIM vs app backend vs clock skew—note timestamps for any support ticket.
If you used a shared APK path, first login is when you finally exercise the live API. Keep one device screenshot of the publisher line from install—cross-check with download guidance—then complete OTP on cellular data you control. Once inside, sanity-check squad flow on the app workflow page. Avoid parallel logins on borrowed hotspots; session hijack is rare but confusion about which number is bound is common.
Download guidance answers “is this file and listing legitimate?” Login help answers “does the account path behave once the app is real?” Squads and lock timers sit on the app workflow page; judgment on policies and support lives in the review notebook.