Sessions · loops
11 Winner session restore and repeated login help guide
You keep seeing the sign-in screen, OTP arrives too often, or reopening the app forgets you. Login help covers correct number and one clean OTP attempt; this page covers patterns that repeat.
OTP repeat after reinstall
Removing the app clears local storage—expect another OTP the first time back. That is not a bug. If you reinstall weekly and feel stuck in a loop, check whether the package is crashing (hand off to support to split install vs auth). Field-level SMS advice stays on login help.
Session restore after app close
Some builds ask for verification when memory is tight or after an update. If every cold start forces OTP while others stay signed in on the same handset, note version and time pattern, then use support after you rule out battery saver killing background tasks.
Why login loops happen
Loops often mix two mistakes: using register when you already have an account, or chasing a browser page instead of the launcher app. Pause, open Winner11 from the drawer only, and pick login once. Definitions: FAQ.
Repeated mobile verification
Carriers and spam filters can delay SMS; repeatedly hitting resend creates a pile of codes and confusion about which one is current. Slow down: one request, wait, enter the latest code only inside the app—details on login help.
Route to register if session is lost
If the app insists the user does not exist, you may never have finished signup—switch to register guide instead of hammering login. If you are certain you finished onboarding once, return to login help for number format and OTP only.
Where this differs from login help
Login help is the single sign-in attempt playbook: right number, one OTP, safety inside the app. This guide is for recurring behaviour—reinstall cycles, reopen surprises, and “it keeps asking me.” Still lost on category? Support picks the next document.