claims review Get the file

Two MMY packages, one label

Two files, one label, and a set of pages elsewhere quoting a version that matches neither. The way through is to stop trusting the label and anchor on the file identity.

What the two files share

Both were measured on 10 November 2026. Both report versionName 2.2.5 and versionCode 225. Both use the application label MMY. Both declare the same thirteen permissions, and both are arm64-v8a packages built on Cocos 3.8.2 with minSdk 24 and targetSdk 35. From the outside, from a screenshot of a phone screen, they are the same app.

Where they differ

The channel file is mmy.2rwkt.apk, 20,954,528 bytes, package com.mmyuionn.opp02, SHA-256 b699d1480b19ec1fb28974c90df518bc7ff989e0900ec9fcc4beef7c353e6421. The second file is mmy.apk, 21,049,457 bytes, package com.Mymuqiueb.ineb. The difference in size is about 95 KB, and the channel build carries an attribution marker the other file's identity does not share. Android does not care about the label. It cares about the package name, so the two install side by side, with two icons that both say MMY and two separate stores of data.

That is the confusion, and it is built into the files rather than into any one page. A reader who installs the second file and later installs the channel file does not get an update. They get a second app. Signing keys follow the package, so there is no path that merges the two. Account data kept inside one package stays inside it.

Pages that name a third thing

Several pages elsewhere describe an MMY APK as version 1.2.4, and give a size between 32 MB and 42 MB. No site is named here, because the point is the method rather than the list. Neither figure matches either file measured on 10 November 2026. 1.2.4 is not 2.2.5. A size in the thirties or forties of megabytes is not 20,954,528 bytes and not 21,049,457 bytes.

Two explanations survive contact with the files. The page could be describing an older build that this review has not measured, in which case it should say so and give a date. Or the page could be repeating a figure it never checked. A reader cannot tell those apart from the page itself. The byte count settles it: ask the page which file, and compare.

The label is a string the developer chose. The package name is the identity Android enforces. When a page gives you the label and withholds the package name, it has kept the part you cannot check and dropped the part you can.

How to anchor

  1. Get the byte count. 20,954,528 is the channel file. 21,049,457 is the second file. Anything else was not measured here.
  2. Read the package name off the install sheet or out of a dump. com.mmyuionn.opp02 or com.Mymuqiueb.ineb. A third package name is a third app, however the icon looks.
  3. If the decision matters, compute the hash and compare it with the channel hash above. The hash is the only check that does not depend on a label, a page, or a filename.

The checklist puts the same three steps among the seven, with the reasoning for each. The claims versus file page shows what the listing claims on top of these two files, which is a separate question from which file you hold.