Get the app

MMY app notifications

On Android 13 and newer the MMY app asks for notification permission at runtime. The prompt is one decision, and declining it changes less than it looks.

Why the prompt appears

The manifest declares POST_NOTIFICATIONS, and targetSdk 35 means the app follows the current rule: notification permission is requested while the app runs, not granted at install. Phones on Android 12 and older never show this prompt. On those versions the permission is granted with the install, and alerts arrive unless you later block them in Settings.

The prompt usually shows early, often before you have finished registering. You can answer it then or leave it; it does not gate the rest of the setup.

Declining does not block login

Saying no stops alerts. It does not stop registration, the OTP, or play. The login code arrives by SMS, which is a message, not a notification, so a declined prompt has no effect on whether the code shows up. If a code is missing, the checklist is on the account page, and notification settings are not on it.

What you do lose is anything the app chooses to surface as an alert: a prompt to return, a status the app wants to show outside its own screen. Those simply never appear.

Turn alerts back on

The path is Settings, then Apps, then MMY, then Notifications. Enable the switch there. If you have both builds installed, the settings list shows two entries named MMY; match the one you mean by opening it and checking it is the app you actually use. The two builds page explains why the list can contain two.

On some manufacturer skins the same screen sits under a different label, such as App info or Permission manager. The switch still lives with the app's own entry, not in a global list you have to hunt for.

When alerts are on but nothing arrives

None of this touches the session. Changing notification permission does not log you out, and it does not clear cache or data.