gradle

Using Firebase in a multi-module project

给你一囗甜甜゛ 提交于 2020-08-04 11:54:49
问题 I have a multi-module multi-flavor android project, the modules are as follows: core module, which is an android library that holds common stuff, including library dependencies. authentication module, which is as the name suggests, a module that contains a bunch of UI activities and is responsible for authenticating users. It's also the module that has the launcher activity. user module, which is another android library module. It is responsible for handling user profile UI, user data, along

Using Firebase in a multi-module project

拜拜、爱过 提交于 2020-08-04 11:54:02
问题 I have a multi-module multi-flavor android project, the modules are as follows: core module, which is an android library that holds common stuff, including library dependencies. authentication module, which is as the name suggests, a module that contains a bunch of UI activities and is responsible for authenticating users. It's also the module that has the launcher activity. user module, which is another android library module. It is responsible for handling user profile UI, user data, along

Cannot create variant 'android-manifest-metadata'

喜夏-厌秋 提交于 2020-08-03 14:20:39
问题 I uploaded my app on Playstore (bundle.aab method) and it works fine with no errors on android 6.0 but got error on android 7.0 device and doens't run the app. I used the Gradle build classpath 3.1.0 - Trying to solve the problem by updating the Gradle version build to 3.2.0-alpha14' so the compile failed giving me the error message bellow. Does anyone know how may I fix this to make my app run on Android 7.0 devices with Gradle 4.7? Perhaps this upgrade fix the device error I think. Thank

The module name specified in 'application.mainModule' (null) has not the expected value (hellofx) [closed]

折月煮酒 提交于 2020-08-03 11:31:48
问题 Closed. This question needs debugging details. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 6 days ago . Improve this question Running the JavaFX project with the run function in Gradle works fine, but using the jpackage function in Gradle does not work properly. An error occurs while executing the jpackage function: 12:56:41 AM: Executing task 'jpackage'... > Configure project : Project : => 'hellofx'

Android Studio setting node directory for build (Cause: error=2, No such file or directory)

一曲冷凌霜 提交于 2020-08-03 05:48:13
问题 My project build fails because it's using the incorrect directory to run Node. How do I go about setting the Node directory for these compile-time tasks? The specific task is: app:recordFilesBeforeBundleCommandDebug And the related error: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:recordFilesBeforeBundleCommandDebug'. Caused by: org.gradle.process.internal.ExecException: A problem occurred starting process 'command 'node'' Caused by: net.rubygrapefruit

Android Studio setting node directory for build (Cause: error=2, No such file or directory)

有些话、适合烂在心里 提交于 2020-08-03 05:47:47
问题 My project build fails because it's using the incorrect directory to run Node. How do I go about setting the Node directory for these compile-time tasks? The specific task is: app:recordFilesBeforeBundleCommandDebug And the related error: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:recordFilesBeforeBundleCommandDebug'. Caused by: org.gradle.process.internal.ExecException: A problem occurred starting process 'command 'node'' Caused by: net.rubygrapefruit

Force to use same certificate to sign different “buildTypes” that are configured for a particular “productFlavor”?

有些话、适合烂在心里 提交于 2020-08-01 17:29:43
问题 Background: I am generating builds using build variant. Below are the configurations: signingConfigs { production { storeFile file("some_path/buildsystem/keystore/some.release.keystore.jks") storePassword "somepassword" keyAlias "somekeyalias" keyPassword "some" v2SigningEnabled false } develop { storeFile file(".some_path./buildsystem/keystore/someother.debug.keystore.jks") storePassword "someother" keyAlias "someotherkeyalias" keyPassword "someother" v2SigningEnabled false } }

Force to use same certificate to sign different “buildTypes” that are configured for a particular “productFlavor”?

安稳与你 提交于 2020-08-01 17:27:26
问题 Background: I am generating builds using build variant. Below are the configurations: signingConfigs { production { storeFile file("some_path/buildsystem/keystore/some.release.keystore.jks") storePassword "somepassword" keyAlias "somekeyalias" keyPassword "some" v2SigningEnabled false } develop { storeFile file(".some_path./buildsystem/keystore/someother.debug.keystore.jks") storePassword "someother" keyAlias "someotherkeyalias" keyPassword "someother" v2SigningEnabled false } }

Force to use same certificate to sign different “buildTypes” that are configured for a particular “productFlavor”?

青春壹個敷衍的年華 提交于 2020-08-01 17:27:21
问题 Background: I am generating builds using build variant. Below are the configurations: signingConfigs { production { storeFile file("some_path/buildsystem/keystore/some.release.keystore.jks") storePassword "somepassword" keyAlias "somekeyalias" keyPassword "some" v2SigningEnabled false } develop { storeFile file(".some_path./buildsystem/keystore/someother.debug.keystore.jks") storePassword "someother" keyAlias "someotherkeyalias" keyPassword "someother" v2SigningEnabled false } }

Force to use same certificate to sign different “buildTypes” that are configured for a particular “productFlavor”?

半腔热情 提交于 2020-08-01 17:27:18
问题 Background: I am generating builds using build variant. Below are the configurations: signingConfigs { production { storeFile file("some_path/buildsystem/keystore/some.release.keystore.jks") storePassword "somepassword" keyAlias "somekeyalias" keyPassword "some" v2SigningEnabled false } develop { storeFile file(".some_path./buildsystem/keystore/someother.debug.keystore.jks") storePassword "someother" keyAlias "someotherkeyalias" keyPassword "someother" v2SigningEnabled false } }