-
Notifications
You must be signed in to change notification settings - Fork 653
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
"Caused by: org.gradle.api.GradleException: Apollo-codegen was not found in node_modules. Please run the installApolloCodegen task." only on build server #1265
Comments
Is it possible to get full logs of build with |
We're running into this as well. Started happening out of the blue with no changes to the build server that I know of. Here's a stack trace:
|
My only assumption is that it get installed into different location than Does this issue happen only on CI but locally runs fine? |
Same here, local build runs ok but fails with the same error on C.I (CircleCI). |
@emanzanoaxa is this file exist on CI |
The strange part is that if it started out of the blue, means something on infrastructure side changed . |
Yes, it exists. |
I'm facing the same problem but locally |
Please give it a try with the latest release 1.0.0 |
I think I'm seeing the same (or similar) issue on CI on 1.0.1
But when I run the build while attached to the machine I see that the |
I work with @bishopmatthew and we were trying few things to solve this. In logs, we noticed label "UP-TO-DATE" with We also use Bitrise as @tir38. |
I am facing the same problem with |
Woooohoooo 🎉 worked great in version 1.0.3-SNAPSHOT |
We are seeing this on our build server (Bitrise)
This is only happening on our build server (Bitrise). This is still happening after I explicitly call
/gradlew installApolloCodegen
before trying to build our app.After adding the explicit install step I see this log as part of the install step (same as #1042)
I'm not sure if this last part is relevant.
I also tested by installing node package directly thx to #1043 (comment) and I'm still seeing the same problem
The text was updated successfully, but these errors were encountered: