Figuring out how to pull the current flavor from gradle While working on an update for one of our games, I needed to figure out how to get the current flavor and use it in code. Since there are a lot of ways to do this, I chose to create a custom build config parameter and…
In a previous post about Gradle Flavors and Build Types, we mentioned that we can set different dependencies inside dependencies{} block by flavors, by build type or both combined. Below we will see an example for each situation. By flavors <flavorName>Compile
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 |
apply plugin: 'com.android.application' android { compileSdkVersion 23 buildToolsVersion "23.0.3" defaultConfig { applicationId "com.example.diana.buildvariants" minSdkVersion 15 targetSdkVersion 23 versionCode 1 versionName "1.0" testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner" } buildTypes { release { minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } qa { applicationIdSuffix ".qa" // signingConfigs as debug key needed. Otherwise, the app won't run and it will ask // you to sign the apk signingConfig signingConfigs.debug } } productFlavors { free { applicationId "com.example.myapp.free" versionName "1.0-free" minSdkVersion 23 } paid { applicationId "com.example.myapp.paid" versionName "1.0-paid" } } } dependencies { paidCompile 'com.android.support:design:23.4.0' compile fileTree(dir: 'libs', include: ['*.jar']) compile 'com.android.support:appcompat-v7:23.4.0' compile 'com.android.support.constraint:constraint-layout:1.0.0-alpha3' testCompile 'junit:junit:4.12' androidTestCompile 'com.android.support.test.espresso:espresso-core:2.2.2' androidTestCompile 'com.android.support.test:runner:0.5' androidTestCompile 'com.android.support:support-annotations:23.4.0' } |
By build type <buildTypeName>Compile>
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 |
apply plugin: 'com.android.application' android { compileSdkVersion 23 buildToolsVersion "23.0.3" defaultConfig { applicationId "com.example.diana.buildvariants" minSdkVersion 15 targetSdkVersion 23 versionCode 1 versionName "1.0" testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner" } buildTypes { release { minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } qa { applicationIdSuffix ".qa" // signingConfigs as debug key needed. Otherwise, the app won't run and it will ask // you to sign the apk signingConfig signingConfigs.debug } } productFlavors { free { applicationId "com.example.myapp.free" versionName "1.0-free" minSdkVersion 23 } paid { applicationId "com.example.myapp.paid" versionName "1.0-paid" } } } dependencies { qaCompile 'com.android.support:design:23.4.0' compile fileTree(dir: 'libs', include: ['*.jar']) compile 'com.android.support:appcompat-v7:23.4.0' compile 'com.android.support.constraint:constraint-layout:1.0.0-alpha3' testCompile 'junit:junit:4.12' androidTestCompile 'com.android.support.test.espresso:espresso-core:2.2.2' androidTestCompile 'com.android.support.test:runner:0.5' androidTestCompile 'com.android.support:support-annotations:23.4.0' } |
By both flavor and build type <flavorName><BuildTypeName>Compile. In this case…
You might notice the new CardView widget on Android L preview presentation. The view can be used to display text or images and has a nice shadow. You can add that view into your project even if you don't have the minimum API level to "L"... to do that, follow the steps below: 1. Edit your gradle.build…
I have just updated my Android Studio to Android Studio 0.8.2. But, after the update I kept getting these 3 errors while I was trying to run my project: 1. First error
|
1 2 |
Error:Execution failed for task > java.io.FileNotFoundException: C:\Program Files (x86)\Android\android-studio\sdk\tools\proguard\proguard-android-optimize.txt (The system cannot find the path specified) |
2. Second error (this happened only after the 1st error had been fixed)
|
1 2 |
Error:Execution failed for task > Manifest merger failed : uses-sdk:minSdkVersion 9 cannot be smaller than version L declared in library com.android.support:appcompat-v7:21.0.0-rc1 |
3. Third Error (when running the app for Android…
[Deprecated] This post is now deprecated, the Manifest Merger has changed since my first post. You can find more about this on the android developers site. Manifest file & Gradle If you started using Android Studio and implicitly Gradle, or you just started using Gradle with other IDEs (like Intellij for example), then maybe you…
I had to re-install my windows, therefore I had to re-install all my programs too, including Android Studio :) So, after I had re-installed Android Studio, I kept getting a Gradle error: " Unable to load class 'com.android.builder.testing.api.DeviceProvider'". After I googled it I found the solution here. It seems that we have to delete gradle's cache.