MMY app first launch

The MMY app installs as a Cocos shell. The game assets are not in the 19.98 MB file; the first open downloads them. That first open is the one to plan.

Use Wi-Fi for the first open

The asset fetch runs over whatever connection the phone has at that moment. On mobile data it spends the allowance, and on a weak signal it stalls in a way that looks like a frozen app. Switch to Wi-Fi before you tap Open, and leave the screen on. The WAKE_LOCK permission exists so the app can hold the screen awake during a round; it does not keep a fetch alive if you lock the phone and the system suspends it.

How long to wait

Give the first open a full minute before you decide it has stalled. The bar can sit still while a file finishes, and tapping around or backing out restarts the fetch. A minute of no movement on a connection you know is working is the point to treat it as stuck, not ten seconds.

If it is still stuck after that minute, the cause is usually the connection rather than the app. A wrong clock, a VPN, or a Private DNS provider can all block the host the fetch calls. Those three are on the connection page, and they are worth ruling out before you reinstall anything.

What force-closing mid-fetch does

Closing the app while the assets are still arriving leaves a partial cache. The next open may resume, or it may sit on the same bar because the partial files do not match what the app expects. Neither outcome is a broken install. The code is fine; the cache is incomplete.

The fix is cache only. Open Settings, Apps, MMY, Storage, and tap Clear cache. That drops the partial files and keeps the login, if you had one. Clear data is the other button on that screen and it is the wrong one here: it logs you out and wipes the app's local store. The difference is set out on the storage page.

After the assets land

Once the first fetch completes, later opens reuse what was stored. You do not pay that download again until the app updates or you clear its data. An update can fetch a fresh set of assets, which is why the app grows past the download size over time and why clearing cache is a normal maintenance step rather than a repair.

The fetch needs a working network every time it runs, so a phone that installed fine can still fail its first open in a dead spot. Move to Wi-Fi and open it again; there is nothing to reinstall.

What a stalled first open is not

• Not a sign the file is corrupt. A corrupt file fails at install, with a parse error, before you ever see the loading bar.
• Not a login problem. Registration comes after the assets land. If you have not reached a phone-number field, the account page will not help yet.
• Not something a second download fixes, unless the installed copy itself is the wrong package. Check the icon count first; two icons named MMY means two apps, covered on the two builds page.