-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build failure - \node-v6.7.0-win-x64\node.exe'' finished with non-zero exit value 1 #608
Comments
I'm having the exact same issue tried around with different node versions and tried different order of gradle tasks also. Happens to me on 'com.apollographql.apollo:gradle-plugin:0.4.0' and on 'com.apollographql.apollo:gradle-plugin:0.4.1-SNAPSHOT'. Any Idea how this could be solved? |
Can you try running with |
Apollo does not support anonymous operations
|
I had this issue with Apollo 0.4.1 and Kotlin 1.1.51 and the only thing that worked was downgrading Kotlin to 1.1.50. |
I'm also getting the same error. I double checked the schema.json and .graphql query file. Error:org.gradle.process.internal.ExecException: Process 'command I'm using apollo v0.4.4 and kotlin v1.2.20. Can anyone tell me why Apollo is throwing this error during code generation? |
Ok, I have the exact same problem but I could build in command line but not through Android Studio. Running with
So for me it seems to be a permissions problem |
I'm getting this error with Apollo v0.4.4 but the code-gen works fine with v0.4.3. Error:org.gradle.process.internal.ExecException: Process 'command |
Apollo 0.4.4
Same issue here as well, even with the sample project, only difference is instead of getting exit value of 1 I get exit value of 243 Update!! Exit Value 243 Solved So after checking the log file for:
I saw that the error I was getting was due to the .npm directory in my home folder belonging to root and not my current user which meant I wouldn't be able to run any npm commands without using sudo. Solution (Exit Value 243): sudo chown -R $(whoami) ~/.npm Credits: https://stackoverflow.com/questions/16151018/npm-throws-error-without-sudo Exit Value 1 (Error:Validation of GraphQL query document failed) My specific issue for:
Appears to be caused by using similar fragment names in my separate .graphql files, thus changing the name to assure they are different fixed my issue |
Pay attention that every query has a name... |
I had the same issue, and was able to resolve it by naming my query as mentioned above. |
I ran into the same problem today after trying to update my New information
While the new format is like this
The problem was solved by using the old version of |
@hshahdoost How did you downgrade the apollo-codegen cli ? |
@hopstad first make sure you are not using the And finally uninstall your current apollo-codegen and install it in the following format
PS: by the time I faced this error, Apollo android could not read the schema generated by |
@hshahdoost Solved by removing apollo and installing the new one. Then using new command for downloading schema : |
Nevermind.. Still not working. I thought it was, but was wrong. What I did was uninstall apollo and tried the new one (apollo schema:download). The error was now of a different type and said the following:
Tried to uninstall again and download a old apollo version (0.20.2) and did the same old "apollo-codegen" and them I'm back to the same error as before:
EDIT |
@hopstad I kind of got surprised because in your mention above, you were using
|
I am facing this error using AWS-Amplify.
|
.grade file? |
@kpjofficial no, There is nothing wrong with the .gradle file the |
I am using it as part of AWS Amplify, and it does not require separate apollo installation. For me, this error was due to bad query nomenclature in AppSync. Amplify automatically generates all the files in android based on the graphql queries and there was issue in it. I solved it by using new graphql schema with proper naming conventions, so that the files generated in Android does not throw this error.
|
Hey @kpjofficial, I am facing the same issue, which naming conventions have you used to fix it? |
@Nieltz By naming conventions, I meant to avoid usage of special characters and naming in camelcase but then you can also check |
I recently tried
I'm stuck here. |
Also having the same issue. I installed apollo-codegen to create the schema.json but I'm still getting a build failure with exit code 1. |
Fixed for me: The schema generated by results without the "data" name. Adding
with the corresponding spaces, finished the ':generateMainApolloIR' subtask, generating the classes for the queries on *.graphql files successfully. |
Been stuck on this , still not working , can you just walk me through what steps you took , Apollo gradle plugin version etc. :( |
I have installed Node Js version v6.11.0. But I'm getting the following error. Please help me on this.
Information:Gradle tasks [:apollo-android-support:generateDebugSources, :apollo-android-support:mockableAndroidJar, :apollo-android-support:prepareDebugUnitTestDependencies, :apollo-android-support:generateDebugAndroidTestSources, :apollo-espresso-support:generateDebugSources, :apollo-espresso-support:generateDebugAndroidTestSources, :apollo-espresso-support:mockableAndroidJar, :apollo-espresso-support:prepareDebugUnitTestDependencies, :apollo-integration:generateDebugSources, :apollo-integration:mockableAndroidJar, :apollo-integration:prepareDebugUnitTestDependencies, :apollo-integration:generateDebugAndroidTestSources, :apollo-sample:generateDebugSources, :apollo-sample:mockableAndroidJar, :apollo-sample:prepareDebugUnitTestDependencies, :apollo-sample:generateDebugAndroidTestSources]
Error:Execution failed for task ':apollo-integration:generateDebugApolloIR'.
The text was updated successfully, but these errors were encountered: