Version number not updated in first build after version increment

[NightlandDriver]

Environment:

• Unity Version: 6.3 LTS (6000.3.2f1)
• Build Versions: 1.2.2

Description:
When using the tool to increment the application version, the next version number is generated correctly. However, the first build created after the version increment still displays the previous version number in-game.

Steps to Reproduce:

• Create a build with version 0.0.5.
• Use the tool to generate the next version (0.0.6).
• Create a new build.
• Check the version number displayed in-game.

Expected Behavior:
The first build after the version increment should display the new version number (0.0.6) in-game.

Actual Behavior:
The first build after the version increment still shows the previous version (0.0.5) in-game.
Only after building a second time does the correct version (0.0.6) appear.

Additional Notes / Question:
Is this behavior intended, or is it a bug?
If intended, is there a technical reason why the updated version number is only applied starting from the second build, or is there a way to ensure the correct version is applied on the first build?

Additionally, would it be possible to add support for displaying the build timestamp (time of the build) in-game?

[JonathanMCarter]

Hi,

So there may be an issue here. Which I'll double check. Assuming you incremented to 0.0.6 before making the build the 0.0.6 should've been the shown version at a minimum.

The system increments the version number after a build is made, it will either apply on successful builds or any build attempt dependant on the build update time setting set in the asset settings. So it'd normally increment after a build is made instead of before as that's usually when you'd want to increment it, ready for your next build.

As for supporting full timestamps, yea I can likely add that. Currently you can get the build date, but not an exact time.

I'll update you on progress when I have some to share.

[NightlandDriver]

Thank you for the quick response.

If I understand this correctly, the intended behavior is that when I set the version to 0.0.6 as the starting version, the build itself should use 0.0.6.

After the build is completed, the system then increments the version to 0.0.7, which would be stored and used for the next build.

If that is the case, then everything is working as expected on my end.
That said, it would be helpful to have an optional setting that allows the version to be incremented before the build is created, rather than only afterward.

I've also attached a video that shows exactly what is happening on my side, in case that helps clarify the behavior.
Video

[JonathanMCarter]

Hello again.

That is correct on the build number updating post build to the next one. Most of the time this is the flow you'd want, where the build you are making is the one set in the settings and the number updates ready for your next build when you've completed the current one.

I think I did once have the feature to choose when, but post build made the most sense for the usecase for the asset. Its a bit rare to increment when starting a build, thats all.

I can look to add that back in possibly... I'll see if I can fit it in.

Likely will be post Christmas to new year before anything is ready though.

[NightlandDriver]

Thank you for the clarification and for the quick responses - I appreciate it.

That makes sense, and I understand why updating the version post-build is the more common and sensible default for this use case.

No worries at all regarding adding the option back in - please don’t feel any pressure. Enjoy the holidays first, and thanks again for taking a look.