Environment variable for VERSION_NAME is being changed when saved

Question & Answer Android
1

We use an environment variable to set the VERSION_NAME and VERSION_NUMBER for android release builds. We’ve been using this for years and it’s worked fine. It appears Bitrise just changed how it saves the environment values and is trying to “be smart” by now truncating numbers. VERSION_NAME is a string in android, but most people use a public version using a “number” as do we.

i.e. In the past we had a 3.9 release followed by a 3.10 release, floowed by a 3.11 release, no problem,

Now we just hit 3.20 and bitrise is changing the variable to 3.2. We go in change it to 3.20 and it detects that we made a change, enables the save button. Then after saving, behind the scenes changes it to 3.2 again (The screen still shows 3.20 as we set it - so you have no idea that bitrise is changing it, but if you close the editor and re-open you see that it changed). Very unintuitive and frustrating.

2

The workaround seems to be to quote the value “3.20”. Don’t really understand why this change was made though.

Changing how something works, not showing that change in the UI, and discovering it when trying to ship a product is not a great customer experience.

3

Unfortunately the workaround doesn’t work that well either.
We have the Git Tag set to:
v$VERSION_NAME
which screws up the tag in git (Your Git Tag step keeps the quotes).

Multiple working build steps were broken with this change, can you please provide guidance on how to fix them or alternatively undo the breaking change?

4

Hi @_jt

Thanks for highlighting this issue. We’re sorry that you experienced these difficulties.

We’ve made an update that should resolve this problem if you revert to your original setup i.e. return your env var back to 3.20 without the quotes. Let us know if you are still having difficulties.

1 Like