Seperate version/code information for build flavours
See original GitHub issueIs it currently possible to have multiple advancedVersioning
for multiple build flavours?
Issue Analytics
- State:
- Created 9 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Configure build variants | Android Developers
This page shows you how you can configure build variants to create different versions of your app from a single project and how...
Read more >Flavours with different versionCode and versionName - GitLab
Hi, we at nextcloud want to build a dev version from master with a different flavour (generic vs versionDev). Beside that we have...
Read more >Android gradle - different versionCode for different buildType
We have an app that has 3 build types (alpha, beta, release) and several product flavors that are dependent on a country where...
Read more >Android Build Types and Product Flavors - DigitalOcean
Android Product Flavors are used to create different app versions. App versions can be free or paid. They can have different themes and...
Read more >Creating Different Build Variants in Android - MindOrks
In this blog, we are going to learn how to create different build variants in any Android Project. By creating a build variant, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@bogdanRada It’s cool! I have that same problem with the versioning I have aswell… Not sure how I can stop it from increasing though
How about separate: versionCodeType ‘AUTO_INCREMENT_ONE_STEP’
For instance if you let us set the name for the variable in version.properties that would be enough