gradle-release | like release process for projects using Gradle | Plugin library

It finally worked for me. I changed the gradle version used to 6.7.1 and reinstall some outdated cordova plugins.

plugins used:

Really big thanks for your question & description of the problem, because it helped me to upgrade from cordova-android 9.1.0 to 10.1.1 :-).

And i think i can solve your problem. This error is thrown, because google services plugin is registered twice (apply plugin: 'com.google.gms.google-services') in gradle files, e.g.: platforms/android/app/build.gradle. You just have to comment/remove one of these imports.

Because cleaning files manually every time is very annoying, i created a bash script (= working on Mac OS), which comments the second import automatically: fix_android.sh

modification needed to avoid mixing libraries. Mainly explained in app.module:

• removed after Import firebase.initializeApp(environment.firebase);
• added in imports: AngularFireModule.initializeApp(environment.firebase),
• removed: AngularFireAuthModule
• removed in providers: { provide: AngularFirestore, useValue: {} },
• instead added in providers: { provide: SETTINGS, useValue: {} },
• removed in providers: Firebase,

I believe that this is all related to the repo URL problems over the last week or so. More info is here https://github.com/grails/grails-core/issues/11825 but in general it sounds like the http URLs are either going away, or gone already.

Specifically reference https://github.com/grails/grails-core/issues/11825#issuecomment-859692299 in which Jeff Brown states

If the HTTP URLs do resume working without a redirect that will be for a limited period. I would not suggest reverting any updates you have already made to the HTTPS repository URLs. I would also strongly consider taking the time to update your remaining applications.

Change to https and come back with whatever problems you run into then...I would expect someone here can help work through those.

Use this plugin.

You can install it with npm i openforge/capacitor-game-services into your capacitor project.

Follow the instructions on the GitHub page to the end before trying to fix errors plopping up.

Maybe use proper file naming, rename your

Android fully supports java 7 and a subset of java 8 and 9 features. So, yes, the JDK 15 you downloaded is not compatible with the Android development platform.

AdoptOpenJDK 1.8 is the preferred JDK for Android development (don't quote me on this, there may be disagreements)

Then, from the build log you can see ANDROID_SDK_ROOT=undefined (recommended setting). That's fine, ANDROID_SDK_ROOT can be undefined.

After you've downloaded the correct JDK, the only two environment you need to set are:

I did it!!!!!

First of all, keep in mind you have to use only one image for the iOS splash screen, although the Cordova docs says you can also use multiple images like in the past.

So, in the root folder you need this:

Based on error log snippet, I could see that the error is related to the deadlock in the DB transactions. I think Artifactory is running with the default derby DB. The below error log snippet tells that there was deadlock situation in Derby,

Caused by: org.apache.derby.iapi.error.StandardException: A lock could not be obtained due to a deadlock, cycle of locks and waiters is: Lock : ROW, NODES, (2975,6) Waiting XID : {230127895, S} , APP, SELECT * FROM nodes WHERE repo = ? AND node_path = ? AND depth = ? Granted XID : {230127897, X} Lock : ROW, NODES, (991,272) Waiting XID : {230127897, S} , APP, SELECT * FROM nodes WHERE repo = ? AND node_path = ? AND depth = ? Granted XID : {230127895, X}

I had a similar JenkinFile which deploys Artifacts to Artifactory and never faced this issue. I believe a simple restart of Artifactory should be enough to remove the Derby DB from the deadlock state.