build-variant

How to synchronize build variants among apps

由 淺唱寂寞╮ 提交于 2020-07-10 08:31:39
问题 I am working on a project that contains multiple applications. Several of them contain the same flavors. The same values on a flavor dimension, precisely. I would like to have their value synchronized, if possible automatically. Otherwise, I would like it to show there is a conflict. To summarize the situation, I would like the build variant selection pane to behave for unrelated applications of the same project the same as it works for module being a dependency of an app. How can I achieve

Getting error says - “Entry name 'res/layout/test_toolbar.xml' collided” while creating signed apk

由 穿精又带淫゛_ 提交于 2020-03-18 11:47:05
问题 I have updated my android studio from 3.5.x to 3.6 today and getting error while generating signed apk for build variant showing the following message - Entry name 'res/layout/test_toolbar.xml' collided I don't have any layout named like this one in the whole project at all. I have custom build variant named " stage " and whenever I am trying to build an signed apk, it always fails. I count find any solution yet. Please help me with this issue. Thanks 回答1: I've got the same problem after this

Android Studio build variant problems

由 回眸只為那壹抹淺笑 提交于 2020-02-02 11:11:50
问题 I am having difficulty getting Android Studio to build the right build variant — or even to let me select a build variant at all, sometimes. Basically I have two different versions of my project a free and a "full" version. Package ids are "com.mycompany.myproj" and "com.mycompany.myprojfree". Once I've specified "myproj" and "myprojfree" flavors and "release" and "debug" buildtypes, Android Studio produces four variants in the list: myprojDebug, myprojfreeDebug, myprojfreeRelease, and

Promotion of app from beta to production on Google Play working with Build Variants

由 最后都变了- 提交于 2020-01-03 05:21:12
问题 I have the follow situation Scenario Part 1. An app working with Build Variants : debug , beta and release as follow buildTypes { debug { versionNameSuffix '-DEBUG' applicationIdSuffix '.debug' buildConfigField "String", "SERVER_URL", '"url local test"' debuggable true signingConfig signingConfigs.config } beta { versionNameSuffix '-BETA' buildConfigField "String", "SERVER_URL", '"url homologation"' signingConfig signingConfigs.config } release { buildConfigField "String", "SERVER_URL", '"url

Android Studio CMake build once for all build variants

由 不打扰是莪最后的温柔 提交于 2019-12-19 10:24:51
问题 I have a project with C++ code (JNI) and lots of build variants and combinations. These are used to implement different brandings / flavors of the app (i.e. colors, styles, icons, ...). For example there could be build variants for n customers : customerNDebug customerNDebugproguard customerNRelease . Anyway, the C/C++ layer is the same for each product flavor . Normally CMake in Android Studio compiles C code for every build variant. This makes sense if you have build variants like " debug "

ERROR: No signature of method: com.crashlytics.tools.gradle.CrashlyticsPlugin.findObfuscationTransformTask()

由 别来无恙 提交于 2019-12-03 04:41:37
问题 I am getting the following error while trying to build my project on Android Studio: ERROR: No signature of method: com.crashlytics.tools.gradle.CrashlyticsPlugin.findObfuscationTransformTask() is applicable for argument types: (java.lang.String) values: [DevDebug] How to solve this? 回答1: This seems to be an issue related to version "1.28.0" of "io.fabric.tools:gradle" . Usually this kind of problem occurs if groupId:artifactId:n.+ structure of versioning is used inside dependency (app level

android test support flavors and build type variants?

由 瘦欲@ 提交于 2019-12-02 00:43:30
问题 android test support flavors and build type variants? flavorDimensions "foo" productFlavors { full { dimension "foo" } trial { dimension "foo" } } If there is only src/androidTest/java, which variant to test? 回答1: You can create tests for specific flavors in src/androidTestFull and src/androidTestTrial . Any tests that are common to all flavors go in src/androidTest . The instrumented tests in src/androidTest/ source set are shared by all build variants. When building a test APK for the

android test support flavors and build type variants?

由 杀马特。学长 韩版系。学妹 提交于 2019-12-01 20:32:44
android test support flavors and build type variants? flavorDimensions "foo" productFlavors { full { dimension "foo" } trial { dimension "foo" } } If there is only src/androidTest/java, which variant to test? You can create tests for specific flavors in src/androidTestFull and src/androidTestTrial . Any tests that are common to all flavors go in src/androidTest . The instrumented tests in src/androidTest/ source set are shared by all build variants. When building a test APK for the "MyFlavor" variant of your app, Gradle combines both the src/androidTest/ and src/androidTestMyFlavor/ source

variantOutput.getPackageApplication() is obsolete

由 試著忘記壹切 提交于 2019-11-26 06:39:39
问题 with Gradle 4.10.1 and the Android Gradle plugin updated to 3.3.0 , I get the following warning: WARNING: API \' variantOutput.getPackageApplication() \' is obsolete and has been replaced with \' variant.getPackageApplicationProvider() \'. the line, with the surrounding context (which is assigning output file-names by build variant): applicationVariants.all { variant -> variant.outputs.all { output -> if (variant.getBuildType().getName() in rootProject.archiveBuildTypes) { def buildType =
订阅 build-variant