MMY login & registration on Android

Registration happens inside the app after it is installed. This page covers the points where the phone itself gets in the way.

Before the first open

The app fetches its assets on first launch. On a slow or metered connection that looks like a stuck screen. Use Wi-Fi for the first open, and give it a minute before force-closing it. Force-closing mid-download leaves a partial cache, which the reinstall steps clear.

The phone number and the OTP

The app asks for a mobile number and sends a one-time code by SMS. If the code does not arrive, check that the phone has a working SIM with SMS reception, and that no SMS-blocking app is filtering messages from unknown senders. A second request too quickly usually does nothing; wait out the timer the screen shows.

The manifest declares READ_PHONE_STATE but not READ_SMS, so the app cannot read the code out of your messages itself. You type it in.

Notifications

On Android 13 and newer the app asks for POST_NOTIFICATIONS at runtime. Declining it does not block login. It means you will not see the app's alerts. You can change it later under Settings, Apps, MMY, Notifications.

Two apps, one phone number

The channel file uses package com.mmyuionn.opp02. A second MMY file measured the same day uses com.Mymuqiueb.ineb. Android keeps their data apart. Signing in on one does not sign you in on the other, and uninstalling one does not touch the other. If you already registered under a different package, reinstalling this file will not bring that session back.

When the login screen will not load

• Check the date and time are set automatically. A wrong clock breaks the secure connection and the screen just spins.
• A VPN or a Private DNS setting can block the host the app calls. Turn it off for the attempt.
• If the app opens to a blank page after an update, clear its cache under Settings, Apps, MMY, Storage. Cache only; clearing data logs you out.