You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Mobile.BuildTools 2.0.245 in Azure Devops Pipeline with iOS and the Bundle Version does not get replaced with the Build Number. I've this in buildtools.json:
Also added this in the .csproj: <AutomaticVersionBehavior>PreferBuildNumber</AutomaticVersionBehavior>
I see this in the build log:
AutomaticBuildVersioning:
Executing Automatic Version Generator
Build Number: 8205
Processing Manifest
And still the Bundle Version is 1.0 when I check the build.
What is also interesting is that when I build Android, the setting does not have any effect. When I change to Timestamp it still uses the build number and even when I turn off buildtools automatic versioning it used the build number in the AndroidManifest.
I get the impression it just doesn't work on iOS (either bug or I missed something) and it uses some default functionality outside of Mobile.BuildTools on Azure Pipeline.
Apologies for the confusing report, but any pointers would be appreciated.
The text was updated successfully, but these errors were encountered:
I'm using Mobile.BuildTools 2.0.245 in Azure Devops Pipeline with iOS and the Bundle Version does not get replaced with the Build Number. I've this in buildtools.json:
Also added this in the .csproj:
<AutomaticVersionBehavior>PreferBuildNumber</AutomaticVersionBehavior>
I see this in the build log:
And still the Bundle Version is 1.0 when I check the build.
What is also interesting is that when I build Android, the setting does not have any effect. When I change to Timestamp it still uses the build number and even when I turn off buildtools automatic versioning it used the build number in the AndroidManifest.
I get the impression it just doesn't work on iOS (either bug or I missed something) and it uses some default functionality outside of Mobile.BuildTools on Azure Pipeline.
Apologies for the confusing report, but any pointers would be appreciated.
The text was updated successfully, but these errors were encountered: