android-productflavors

EDIT flavors and paths: Currently I have: sourceSets.whenObjectAdded { sourceSet -> def sourceData = rootProject.ext[sourceSet.name] sourceSet.java.srcDirs = sourceData.javaDirRelease } The rootProject.ext is a file where all the productFlavor specific configuration is defined like this: ext{ flavor1 = [ javaDirRelease : ['src/pathToJavaReleaseFiles'] javaDirDebug : ['src/pathToJavaDebugFiles'] ] } In the main build.gradle I also do: apply from: 'variants.gradle' which contains the above ext{} object. The sourceSets are defined as such: sourceSets { flavor1{} } This works but I want to do add

I have library which contains string resource: <string name="lib_name">MyLibrary</string> Reference to library in application build.gradle: dependencies{ compile project(':mylibrary') ... } In application module I have displayed this text resource: <TextView android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="@string/lib_name" /> There is no problem without using flavors. Now I want to add new flavor to library with different text. build.gradle of library: android { ... productFlavors { myFlavor {} } } Then I create new resource file for new flavor \mylibrary

I'm creating a very simple app with a free and paid version, for this I'm using the great productFlavors feature in the Android Gradle plugin. I understand how the build.gradle file should be configured and have written it so my build options are; freeRelease freeDebug paidRelease PaidDebug that looks as follows buildTypes { release { runProguard false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt' signingConfig signingConfigs.someconfig } } productFlavors { free { packageName "com.somepackagename.appfree" } paid { packageName "com.somepackagename.appPaid" }

How do I configure my project to be able to install the debug version alongside the release version when using GCM, ContentProvider, AccountType? (without the use of flavors) I keep getting errors such as: INSTALL_FAILED_CONFLICTING_PROVIDER or INSTALL_FAILED_DUPLICATE_PERMISSION Benoit Installing a debug apk and the release apk on the same device is tricky if you are only using build types and not flavors ( Why Build types and not flavors ) Most blog post are either outdated (talking about packageName) or force you to use flavors because the solution they propose does not support