What is the best way to manage app versioning across both app stores?

[engineerliz]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

1. I've been using pattern version: x.x.x+y in pubspec.yaml to version the app. For each incremental update y, so for example 1.0.1+1 -> 1.0.1+2
2. On ios app store, this versioning patterns works as expected. However on google playstore, the versioning shows up as y (x.x.x). below screenshot is for version: 1.0.2+39

3. I recently upgraded to 1.0.3+1 and now the playstore shows the version as 1 (1.0.3) which it thinks is a lower version than 39 (1.0.2) from above

4. This is blocking codemagic from uploading the newest app version to playstore because playstore blocks "lower version app builds"

Expected results

I would expect either the versioning in google playstore to correctly reflect the versioning pattern or for there to be an option in the code magic console to configure versioning.

Actual results

Right now I do not see a way to fix the current versioning situation for 1.0.3+1

Build id (optional)

No response

[himesh-cm]

Hi @engineerliz, I suggest checking the docs here with the docs on Auto build versioning.

[engineerliz]

thanks fro the quick response! the doc you linked shows how to do it via .yaml but is there a way to configure this using the workflow editor?

[himesh-cm]

You need to append the command to the Flutter build command, it can be yaml or workflow editor
--build-name=1.0.$PROJECT_BUILD_NUMBER --build-number=$PROJECT_BUILD_NUMBER.

[himesh-cm]

I'm tentatively closing the discussion since we haven't heard back from you. You can open the discussion again by replying to this message or opening a new discussion.