Store upload: the app version is free text, unchecked against the .iq that already carries it

## The form

Updating an app in the developer dashboard starts with **Step 1: Attach File**, which has two fields:

- **File Path**, for the `.iq` bundle;
- **App Version (Maximum 20 Characters)**, a free text field, with the latest version shown below it,
for example "(Latest app version: v1.0.1)".

The version is typed by hand, although the bundle already carries it. The `manifest.xml` inside
every `.iq` has it on the application element:

```xml
<iq:application id="..." type="watchface" version="1.0.2" ...>
```

## What the store accepts

- **any string** as the version, for example `foo bar`;
- a version that **does not match the bundle's**: a bundle built as one version, uploaded as another;
- a version **earlier** than the latest, for example 0.9.0 after 1.0.0;
- the **same bundle again**, under a different typed version.

The one thing it **refuses** is a version string that has already been used for an earlier upload,
whatever the file.

## Why it matters

The typed version is the one thing the store checks, and it is not checked against anything in the bundle. A
typo, or the wrong file attached, is accepted, and the version string it used can never be used
again.

Step 1 is also the step that publishes: its button is "Upload and publish", and the new file and
version are live as soon as it completes, before Step 2, where the description and release notes
are updated. There is no review point between typing the number and the app going live. A developer
who stops after Step 1 (by intent or accident) leaves the app in limbo, with the new file and version live under the
previous release's description and notes.

The version the store shows can also differ from the version the app was built with, and nothing
warns about it. A developer who keeps the manifest version as the single source of truth gets no
help from the store in keeping the two the same.

## Suggestion

Upload, review, then publish, as one flow:

1. **Upload the bundle.** It is stored and parsed, but not published.
2. **Review the details**, with the version prefilled from the bundle's `manifest.xml`. The developer
may change it, as long as it does not collide with a version already used. The description and the
release notes are edited on the same page.
3. **Publish.** Only this step makes the new version live, with all of its details in place.

The version is then the one the developer already stated, in the manifest, unless they choose
otherwise. Checking it against the versions already used is the only check needed: it also refuses
the same bundle uploaded twice, since an identical bundle carries the identical version. And an
update that is abandoned halfway leaves nothing live, instead of a new version under old notes.
  • The version in project's manifest.xml is only used for barrels,

    When you export the barrel, it's included in the name

  • Thanks, that matches the Manifest documentation, which describes version only for barrels. For an app, monkeyc still writes it into the exported bundle: the manifest.xml inside the .iq carries version="1.0.1" on iq:application, which is what made it look like the app's version. So the suggestion stands in a smaller form: either the store reads that attribute for apps, or monkeyc leaves it out of app bundles, so there is one version and it is the one typed at upload. The publish-on-upload part is unaffected.

  • It sounds like something that could impact any app started/exported in the last 11 years. I don't see any benifit.

  • Fair enough on monkeyc; that half is about tidiness.
    However, parsing a version string out of an iq file and making it the default for the developer to approve or modify can't possibly break 11 years of past app submissions.

    The part I care about is the first one: "Upload and publish" makes the bundle and the typed version live before the notes are written, with no step in between to review them. Fixing this can't break the past apps either.

  • I haven't changed the version number in the manifest for anything but barrels in 11 years but the store shows what I set as a version there on all my apps.  A change like this would impact all the apps. And I can't see a benefit.

  • As mentioned, the version is the minor part of my request. I understand your view, and let's leave it there. I'd rather hear Garmin's perspective.

    The ask is to fix the app update process: today "Upload and publish" makes the uploaded bundle live before the release data (description, version, release notes, images) can be updated. Upload, review, then publish would solve it.