Why two COME APK pages can list different sizes
The pages may describe different releases, formats or measurements; the numbers alone do not diagnose the difference.
Work through this situation
One page might quote a package while another quotes installed storage or an old listing. Match each number to its version and source. Do not average the figures or pick the smallest file as the correct one.
What to check and why
Create a like-for-like comparison. For each number, note the release, the file format, the source and whether the figure refers to a download or installed storage. A current package listing and an old cached article can legitimately refer to different objects. Their discrepancy cannot be diagnosed by size alone.
If both pages claim the same release and measurement but disagree, keep the discrepancy unresolved until the intended source clarifies it. Do not average the sizes, assume the larger file is safer or select the smallest one to save data. Once an actual transfer completes, its saved size is another observation to compare with the offer, not a publisher certificate.
Use the current listing in its proper context
The COME listing checked on 21 September 2026 names version v1.12 and a package size of 3.1MB. These are listing details, not a measurement of an arbitrary file already on your device. Compare the actual offer before making an update decision. Keep source, release and file identity together instead of using one reassuring label as a substitute for all three.
What a completed answer looks like
Each measurement has an identified context, or the mismatch remains unresolved before installation.
Continue from the stage you have actually confirmed. Preserve the exact message when a step remains unresolved.
Choose another specific COME guide