Android-runtime: Gradle daemon setting 'org.gradle.parallel=true' not supported

Created on 14 Jul 2017 · 22Comments · Source: NativeScript/android-runtime

@KingAndroid commented on Thu Jul 06 2017

I've upgrade ns.

| Component | Current version | Latest version | Information |
| - | - | - | - |
| nativescript | 3.1.1 | 3.1.1 | Up to date |
| tns-core-modules | 3.1.0 | 3.1.0 | Up to date |
| tns-android | 3.1.1 | 3.1.1 | Up to date |
| tns-ios | 3.1.0 | 3.1.0 | Up to date |

Now I can compile ios successfully, but not on android.
While I compile android, it stops on here.
`:asbg:generateBindings
Exception in thread "main" java.lang.NullPointerException
at org.nativescript.staticbindinggenerator.Generator.readDir(Generator.java:289)
at org.nativescript.staticbindinggenerator.Generator.readClasses(Generator.java:244)
at org.nativescript.staticbindinggenerator.Generator.(Generator.java:50)
at org.nativescript.staticbindinggenerator.Generator.(Generator.java:44)
at org.nativescript.staticbindinggenerator.Main.main(Main.java:15)
:asbg:generateBindings FAILED

FAILURE: Build failed with an exception.

Where:
Build file '/Users/admin/Desktop/WORK/barcode/platforms/android/build-tools/android-static-binding-generator/build.
gradle' line: 254
What went wrong:
Execution failed for task ':asbg:generateBindings'.`

Could you please let me know resolution and why?
Thank you.

@Pip3r4o commented on Thu Jul 06 2017

Hey @KingAndroid, in order to help you, we need additional information regarding your setup, as well as the plugins used in your project, so ideally sharing your package.json content, and whether you extend a native class would help us.

In addition you could run the build with the --log trace flag like so - tns run android --log trace and share the output, so we get a clue at what might be failing the build.

Please fill out the template accordingly when logging an issue or a feature request in the future.

Thank you!

@KingAndroid commented on Wed Jul 12 2017

Hey @Pip3r4o
I am sorry, I have tried for 5 hrs and I give up.
I have downgrade 3.0.3 and all works well now.

Here are what I can provide for now.

node : 6.11.0
npm : 3.10.0
Package.json
{ "nativescript": { "id": "uk.co.barcodeapp", "tns-android": { "version": "3.0.1" }, "tns-ios": { "version": "3.0.1" } }, "dependencies": { "moment": "2.18.1", "nativescript-geolocation": "^3.0.0", "nativescript-ios-uuid": "^1.0.0", "nativescript-loading-indicator": "^2.3.2", "nativescript-plugin-firebase": "^3.12.0", "nativescript-screen-orientation": "^2.0.0", "tns-core-modules": "^3.0.1" }, "devDependencies": { "babel-traverse": "^6.25.0", "babel-types": "^6.25.0", "babylon": "^6.17.3", "lazy": "^1.0.11" } }
Thank you.

@sveri commented on Sun Jul 09 2017

I have the same problem here, just installed nativescript from scratch, created a new project and ran:

tns rund android

tns --version 3.1.2
npm --version 3.10.9
node --version v6.9.2

@Pip3r4o commented on Sun Jul 09 2017

Hey @sveri unfortunately that information isn't sufficient, as I can't reproduce the problem locally. Please provide the information as requested in my previous comment. Thank you!

@sveri commented on Sun Jul 09 2017

log.txt

On your demand :-)

@sveri commented on Sun Jul 09 2017

I also have the same problem when using nativescript 3.0.3

@Pip3r4o commented on Thu Jul 13 2017

@sveri thanks for the log! I discovered that the generateBindings is not passed any jars as inputs, thus causing the build error. There wasn't anything else out of the ordinary that I could spot based on the log.

I'd advise you to invalidate the gradle cache located in the user directory/.gradle/cache, re-add the platform and retry a build.

Thanks

@sveri commented on Fri Jul 14 2017

I just tried that and the error is still the same.
I also deleted my nodejs installation and reinstalled everything, my versions are now these:

npm -v && node -v
4.0.0

v6.11.0

@pkoleva commented on Fri Jul 14 2017

Issue moved to NativeScript/NativeScript #4553 via ZenHub

feature

Source

pkoleva

Most helpful comment

Also worth mentioning, still doesn't work with the gradle daemon -- if you try to use it, the APK will not install because the manifest is corrupted somehow, using any version, @latest, or @next.

ghost on 28 Jul 2017

👍2 ❤1 🎉1 😄1

All 22 comments

@Pip3r4o @KingAndroid This is happens to me too with everything on @latest. Tried delete ~/.gradle/caches/ folder and it had no effect. This is a showstopper.

ghost on 17 Jul 2017

@Pip3r4o @kingandroid @vbresults,

The error and lines that fail out are:
https://github.com/NativeScript/android-runtime/blob/master/android-static-binding-generator/project/staticbindinggenerator/src/main/java/org/nativescript/staticbindinggenerator/Generator.java#L288-L289

Based on the Error 288 is returning null. Which causes 289 to fail.
The docs state that listFiles returns:
An array of abstract pathnames denoting the files and directories in the directory denoted by this abstract pathname. The array will be empty if the directory is empty. Returns null if this abstract pathname does not denote a directory, or if an I/O error occurs.

The issue that leads to this failure is this line:
https://github.com/NativeScript/android-runtime/blob/master/android-static-binding-generator/project/staticbindinggenerator/src/main/java/org/nativescript/staticbindinggenerator/Generator.java#L244

It ASSUMES that if it isn't a file; it must be a directory. However, there is at least a couple cases I can think of that isFile will fail.

the primary one is the permissions. If you did a tns plugin add x as sudo (or another user) then the permissions of the folder and files will be wrong and so the build will not be able to read the files properly. You might try doing sudo chown -R USERNAME APP where USERNAME is your normal username, and APP is your primary app folder. (you can type whoami to see your username)

The file is a symlink, device, or socket, or named pipe. All these are not normal files or directories and should be excluded from being processed. If this is the case; you (the user running into this) needs to check the node_modules folder for any non-traditional files and remove them.

NathanaelA on 19 Jul 2017

@NathanaelA

So I tried step one and made sure all files are owned by my user. Still the same problem.

For step 2, how would you suggest I find the faulty files?

sveri on 19 Jul 2017

Hello @pkoleva
How are you?
Any news to resolve this problem?
I have worry to select which framework for my next project.
I have options with NS, RN and Ionic3.
But I crazily love NS, but I can't go through this issue.
So, could you please let me know any great news?

Thank you