When I added Library in my Project And Library has a Google service
Old plugin version is 4.1.0 of Google Service in my Library
Verify gradle can configure itself, project builds
Set plugin version to 4.2.0 of Google Service
The only visible message is Cause: java.lang.NullPointerException
Gradle Version is 3.3.1
Please tell me what can I do in this situation ?
LogCat
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/4.10.1/userguide/command_line_interface.html#sec:command_line_warningsCONFIGURE FAILED in 11s
ERROR: Cause: java.lang.NullPointerException
if you want to out from this error
so please backward of your google service version from 4.2.0 to 4.1.0 this is jugad not a solution
Error is gone......:)
Related
i just joined android studio code java, however i am having a bit of difficulty: Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
I have consulted some workarounds like :gradle build --warning-mode=all . however I don't know where the following code is located? i tried using CMD and powershell but to no avail! what should i do to fix the above error.
Error:Unsupported method: BaseConfig.getApplicationIdSuffix().
The version of Gradle you connect to does not support that method.
To resolve the problem you can change/upgrade the target version of Gradle you connect to.
Alternatively, you can ignore this exception and read other information from the model.
I am trying to use ROSJava in Android Studio 3.0.1 but following the installation instructions given here leads to this error in Android Studio. Please advise.
I managed to solve the issue by using Android Studio 2.x.x instead of the newer 3.x.x version.
I have been using Cordova CLI v 6.5.0 to create my hybrid Android app which uses a custom plugin of my own making. The full toolchain is
Java 1.8 SDK
Cordova CLI 6.5.0
NPM 4.1.2
This has always worked without an issue. I had not upgraded to Cordova CLI 7.0.1 till today since I still supported Android 4.4 and the base version with 7.0.1 is 5.0. Having made the decision to drop support Android v 4.4 support today I decided to upgrade Cordova CLI and immediately ran into some unpleasant surprises
Creating a build-extras.gradle file that specifies using JavaVersion.VERSION_1_8 threw up errors that claimed that some of my source code files were not compatible. This in itself poses a problem since I make extensive use of some Java 8 features such as try_with_resources.
I decided to temporarily drop back to VERSION_1_7 and got the app to complile.
I then thought I would add my plugin to the project (expecting fully well that the system would frown at my use of Java 8 syntaxes) and ran into another unpleasant surprise which I reproduce below
16 error Windows_NT 10.0.15063
17 error argv "H:\nodejs\node.exe"
"H:\nodejs\node_modules\npm\bin\npm-cli.js" "install" "path:\to\my-plugin" "--save"
18 error node v7.5.0
19 error npm v4.1.2
20 error Invalid version: "1.0"
I do not understand these errors - perhaps someone here will be able to shed some light.
Try using --nofetch to install without using the new npm install mechanism:
cordova plugin add path:\to\my-plugin --nofetch
See https://cordova.apache.org/news/2017/05/04/cordova-7.html
I just upgraded my Android Studio preview release to the latest beta 0.8.3 and my gradle build script which was working perfectly fine until now fails with this:
Error:Build script error, unsupported Gradle DSL method found:
'getProguard()'!
Running the script in the command line with --stacktrace gives me:
Caused by: org.gradle.api.internal.MissingMethodException: Could not
find method getProguard() for arguments [] on
com.android.build.gradle.internal.api.ApplicationVariantImpl_Decorated#21939397.
As far as I know, I don't even have a ProGuard task configured for this project.
Android Studio is set to use the default gradle wrapper and querying the version shows I'm using gradle version 1.10.
Be aware that Studio 0.8.3 is a canary release, and bugs are to be expected.
Since updating to 0.8.3 seems to be the change that broke your build, I can only suggest that you file a bug report to the dev team and then downgrade and/or reinstall a more stable release.
I am developing an eclipse plugin which depends on Eclipse platform 4.2 (Juno) and cannot be installed on older versions of eclipse.
When the user tries to install my plugin (via update site) on an old eclipse, the Eclipse installer stops him and shows the following message:
Cannot complete the install because one or more required items could not be found.
Software being installed: Feature 1.0.3 (com.test.feature.feature.group 1.0.3)
Missing requirement: Test 1.0.3 (com.test 1.0.3) requires 'bundle org.eclipse.core.runtime 3.8.0' but it could not be found
Cannot satisfy dependency:
From: Feature 1.0.3 (com.test.feature.feature.group 1.0.3)
To: com.test 0.0.0
Not many people can understand from this error message that all they need is a newer version of Eclipse.
I would like to change this message and display something like:
"Error installing: this plugin requires Eclipse version 4.2 (Juno) or above"
Is that even possible?
You can't customize the error messages, but p2 just (with Kepler) got a lot smarter in trying to figure out what would need to be changed in the existing installation in order to allow the installation of something new.
So in this case, the p2 remediation support would probably propose to update the installed product so that the Feature can be installed.