Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overrule using Semver for versions / just use string matching #2767

Open
sdossick opened this issue Oct 21, 2024 · 1 comment
Open

Overrule using Semver for versions / just use string matching #2767

sdossick opened this issue Oct 21, 2024 · 1 comment

Comments

@sdossick
Copy link

It's common practice on the iOS App Store to use non-semver strings for versions like 2.01. These fail with codepush with "Error: Invalid binary version(s) for a release."

Is there a simple way to work around this? Unfortunately the version of the app in the store that we'd like to target is called 2.01 and there's not much I can do to make that compatible version name...

Ideally, it would be nice if codepush were flexible enough to support any valid version number/string available on the app stores. It would be ok to have a mode switch or something where you give up some of the multi-version targeting you can do with semver versions in exchange for working codepush against these kinds of version names.

@DmitriyKirakosyan
Copy link
Contributor

Hi @sdossick , thank you for reaching out!

Please specify what appcenter-cli version and the exact command you are using to publish the codepush update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants