Closed wzieba closed 1 week ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr21456-3b34197 | |
Commit | 3b341978fc6d7ee56a07a0f1516ff5ee566edd75 | |
Direct Download | jetpack-prototype-build-pr21456-3b34197.apk |
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr21456-3b34197 | |
Commit | 3b341978fc6d7ee56a07a0f1516ff5ee566edd75 | |
Direct Download | wordpress-prototype-build-pr21456-3b34197.apk |
I wonder if we need to also explicitly mark the debug build type as default
It seems we don't - we haven't in the past, and when you open project, it's debug
by default. I guess this is default behavior of AS, which makes sense - opening project in IDE prefers a debug variant if available.
This change triggers me again to ask another question, do we really need those product flavors,
I don't know - there probably was a reason to introduce them by product team, I'd leave the decission for them.
Description
As
wasabi
is "preferred variant for developers", it should be selected by default when opening Android Studio. AGP reference: https://developer.android.com/reference/tools/gradle-api/8.7/com/android/build/api/dsl/ApplicationProductFlavor#isDefault()Testing
Fresh clone the project and open it in AS:
wasabi
should be selected as the current build variant.