Let’s see the following example: buildTypes The default behavior on Android Studio is to order alphabetically all the possible combinations between flavor and build types and then to select the first on the list. Typically you can replicate this on a project that has multiple build types/ flavors defined and on the following scenarios: - cloning a new repo - cleaning all untracked changes from a repo (removing build, *.iml, etc.) - switching between branches It happens a couple of times, it’s nothing dramatic, but it happens here and then. How many of you deal with the (small) struggle of compiling your Android project and when you look at the installed app, you realize that you had the wrong build variant selected? Or, on the opposite side, you weren’t even able to compile it because you’ve got a release build selected on one module and debug on the others?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |