w: Detected multiple Kotlin daemon sessions at build/kotlin/sessions

Solution 1:

UNBELIEVABLE FIXED, seems to be a 63.x issue? As there's another person having this issue after upgrading from 62.2 to 63.3

The fixed was done as suggested here

Solved this issue by deleting the .gradle folder from /android and again run npm run android, and it solved this error.

Solution 2:

What resolved this error for me, was killing all running Java processes in Task Manager.

I had an actual bug in my code, which caused dangling processes, so I was getting only this error and not the one related to the bug.

After killing all processes & running the usual gradle cleanup, I got the right error message I could work with further.

Solution 3:

I solve this issue with this solution.

In gradle.properties add following code

org.gradle.daemon=true
org.gradle.configureondemand=true
org.gradle.jvmargs=-Xmx4g -XX:MaxPermSize=2048m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8

Additionally, insert these lines in app/build.gradle

android{

    dexOptions {
       javaMaxHeapSize "3g"
    }
}

After making these changes run .\gradle clean and .\gradle assembleRelease