android-productflavors

My problem is that after I added flavors to my project the flavor with a package name different from the actual source seems to have problems with accessing the files in android_res/drawable . More specifically I have a html-view that calls the following image. <img src="file:///android_res/drawable/image.png"> The image shows up in the production flavor that has the package name which is the same as the directory of the java-files but it doesn't work for the beta flavor: productFlavors { production { packageName "com.company.myapp" } beta { packageName "com.company.beta" } } where the actual

This is in continuation to an answer which helped me on this post We can add the string resource as follows from build.gradle : productFlavors { main{ resValue "string", "app_name", "InTouch Messenger" } googlePlay{ resValue "string", "app_name", "InTouch Messenger: GPE Edition" } } It works like a charm and serves the purpose of having different app names per flavor. (with the original app_name string resource deleted from strings.xml file. But, how do we add localized strings for this string resource added from build.gradle ? Is there an additional parameter we can pass specifying the locale

I'm trying to define a buildConfigVariable depending on the flavor + buildType . Ideally, this is what I want productFlavors { strawberry { buildConfigField "String", "WS_API_KEY", name + variant.buildType.name } ... more flavors .. } name does contain "strawberry", but I don't know if it's possible to access the variant 's buildType . Placed outside the Android closure I do have access to the BuildType and variant , but then I can't invoke buildConfigField android.applicationVariants.all { variant -> println "****************************" println "variant: ${variant.name}" println "flavor: $

I have a multi-flavored, multi-build-typed android project and I want to integrate the NewRelic plugin. But I have to apply it only for one of the customers, thus only for one product flavor. NewRelic uses instrumentation and the plugin would generate code in other flavors if I applied the plugin there, and that is not permitted for us. So my question is: How can I use the apply plugin: something command in the gradle file to be applied to only one of my flavors? Pavel Santaev Use this code: if (!getGradle().getStartParameter().getTaskRequests() .toString().contains("Develop")){ apply plugin:

I can not get product flavours working. I have this gradle apply plugin: 'com.android.application' android { defaultConfig { minSdkVersion 14 targetSdkVersion 24 compileSdkVersion 27 } signingConfigs { release { } } buildTypes { release { minifyEnabled true proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-project.txt' signingConfig signingConfigs.release } } repositories { maven { url "https://jitpack.io" } } flavorDimensions "dim1", "dim2", "dim3" productFlavors { flavor1 { dimension "dim1" applicationId "com.example.dim1.app" } flavor3 { dimension "dim2" applicationId

I'm using the new gradle build system and I'm facing the following problem: UNEXPECTED TOP-LEVEL EXCEPTION: com.android.dex.DexException: Multiple dex files define Lcom/kibo/mobi/BuildConfig; at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:594) at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:552) at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:533) at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:170) at com.android.dx.merge.DexMerger.merge(DexMerger.java:188) at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:439