The second MMY file: same label, different package

mmy.apk is the second file on the same host. Same version label, same version code, different package, and the button on this site does not serve it.

For comparison, the channel file the button does serve:

Same label, different app

Both files report version name 2.2.5 and version code 225. Android does not identify an app by either number. It identifies an app by the package name, and these two differ: com.Mymuqiueb.ineb against com.mmyuionn.opp02. The system will install both, keep both, and update each one only from a file carrying its own package name.

The size gap is 94,929 bytes, with mmy.apk the larger of the two. The channel file carries a small channel record with an AppsFlyer source marker, and the two packages are otherwise built differently enough to land on opposite sides of that gap. Same label does not mean same bytes, which is the whole reason both hashes are printed.

What installing both looks like

Two icons, both labelled MMY, in the app drawer. Two entries in Settings, Apps, with different package names if you open each one. Separate storage, separate logins, separate data. Removing one does not remove the other, and updating one does not touch the other.

That surprises people who downloaded twice from two different pages and expected the second download to replace the first. It will not. If you only want one, uninstall the one you are not using before you install the other. Uninstalling deletes that app's local data, so take anything you need out of it first.

Which one the button serves

The button carries gz=2rwkt, so the host serves mmy.2rwkt.apk, the channel file, at 20,954,528 bytes. The hash for that file is b699d1480b19ec1fb28974c90df518bc7ff989e0900ec9fcc4beef7c353e6421. If your download lands at 21,049,457 bytes instead, the gz parameter was dropped somewhere along the way and you received the plain file. It is a measured file with a recorded hash, so you can still verify it. It is not the file the rest of this site's checks describe.

Confirming which one you hold

1. Read the byte count. 21,049,457 is this file. 20,954,528 is the channel file.
2. Hash it. This file's SHA-256 is 96c4f39099f1846cfc7eef4edf19d66f9302f9e17795d055908418217a189177.
3. If you have the tools, dump the package name. com.Mymuqiueb.ineb confirms this file.

A file that matches none of those values is a third file, and this page does not describe it. The stale record page covers what to do then.