MMY download file record: both files
Both files came off the same host on 10 November 2026 and were dumped with the same tool. The table is byte-exact.
| Channel file | Second file | |
|---|---|---|
| Name | mmy.2rwkt.apk | mmy.apk |
| Bytes | 20,954,528 | 21,049,457 |
| Difference | 94,929 bytes, about 95 KB, the second file being the larger one | |
| SHA-256 | b699d1480b19ec1fb28974c90df518bc7ff989e0900ec9fcc4beef7c353e6421 | 96c4f39099f1846cfc7eef4edf19d66f9302f9e17795d055908418217a189177 |
| Package | com.mmyuionn.opp02 | com.Mymuqiueb.ineb |
| versionName | 2.2.5 | 2.2.5 |
| versionCode | 225 | 225 |
| minSdk | 24 | 24 |
| targetSdk | 35 | 35 |
| CPU | arm64-v8a only | arm64-v8a only |
The button on this site serves the channel file. The second file is recorded so you can recognise it if you already have it, not so you can fetch it from here.
Why the same version differs by roughly 95 KB
The channel file contains a small channel record that repeats the app id and the version and carries an AppsFlyer source marker. That record is how the vendor attributes the install to the link that produced it. The plain file lacks it. The rest of the package, including the version label and the version code, matches.
So the gap is not a newer build and not extra game content. It is attribution data. Two files with the same version label can still differ, and the byte count is what shows it.
Why the package names differ too
Android identifies an app by its package name, not by the label on the icon. com.mmyuionn.opp02 and com.Mymuqiueb.ineb are different apps as far as the system is concerned, even though both icons read MMY and both report version 2.2.5. Installing the second does not update the first, and uninstalling one leaves the other in place. The consequences, spelled out.
Which row is yours
Read the byte count off the file you downloaded. 20,954,528 is the left column. 21,049,457 is the right column. Anything else matches neither row, and neither hash applies. How to see the exact byte count.
The file name is a weaker clue. The channel token 2rwkt appears in the served name only when the link carries the gz parameter; a browser that renames downloads, or a page that re-hosts the file, can drop it. The byte count survives renaming. The hash survives everything short of editing the file.
What the dump also fixed
Both files were dumped with the same tool on the same day, so the shared rows are genuinely shared rather than assumed. minSdk 24, targetSdk 35 and arm64-v8a only appear in both dumps. A page that quotes a different Android floor or a second CPU architecture for either file is describing something that was not in the package on 10 November 2026.