MMY app account & the OTP
Registration in the MMY app is a mobile number plus a one-time code sent by SMS. The phone side of that is short, and most failures are the SMS rather than the app.
The number and the code
Enter the mobile number the account should live on, request the code, and type it into the field. The manifest does not declare READ_SMS, so the app cannot read the message itself and fill the field for you. That absence is a limit, not a bug: the code stays in your messages until you type it.
Use the number you can receive SMS on at that moment. A number forwarded to another handset, or a SIM that is in a second phone, delivers the code somewhere you are not looking.
When the code does not arrive
- Confirm the SIM has signal and can receive SMS from other senders. A phone that receives nothing from anyone has a network problem, not an app problem.
- Check for an SMS-blocking or spam-filter app. Codes from short numeric senders are exactly what those filters drop.
- Wait out the timer on screen before requesting again. A second request sent too quickly usually produces nothing, and several in a row can pause sending for a while.
- Check the date and time are automatic. A wrong clock breaks the secure connection, and the request never leaves the phone. That fix is on the connection page.
- Turn off a VPN or a Private DNS provider for the attempt. Either can block the host the app calls, which looks identical to a code that was never sent.
If the code arrives and the field rejects it, check you are typing the newest one. An older message still sitting in the thread is the usual mismatch.
One session per package
The login belongs to the package, not to the label on the icon. The channel build this site's button serves is com.mmyuionn.opp02. A second file, com.Mymuqiueb.ineb, is a separate app with its own data and its own session. Signing in on one does not sign you in on the other, and registering on one does not create an account on the other.
If you already had an account under the other package, installing this file starts you at registration again. Nothing in the phone moves a session between package names. Only the app's own account recovery can, and that happens inside the app, not in Settings.
What logs you out
Clearing the app's cache does not. Clearing its data does, and so does uninstalling. Both remove the local store the session sits in. A reinstall of the same package can log back in with the same number; it does not restore a session from the other package. The uninstall page covers moving to a new phone, which is the same situation: a fresh install plus the app's own recovery.