docs
docs copied to clipboard
Failed to build the project with aws amplify
Describe the bug pm ERR! Windows_NT 10.0.22000 npm ERR! argv "D:\AndroidStudioWorkspace\wowe-android-app\app\.gradle\nodejs\node-v6.7.0-win-x64\node.exe" "D:\AndroidStudioWorkspace\wowe-android-app\app\.gradle\nodejs\node-v6.7.0-win-x64\node_modules\npm\bin\npm-cli.js" "install" "[email protected]" "--save" "--save-exact" npm ERR! node v6.7.0 npm ERR! npm v3.10.3 npm ERR! code EPROTO npm ERR! errno EPROTO npm ERR! syscall write
npm ERR! write EPROTO 101057795:error:1408D07B:SSL routines:ssl3_get_key_exchange:bad signature:openssl\ssl\s3_clnt.c:2010: npm ERR! npm ERR! npm ERR! If you need help, you may report this error at: npm ERR! https://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request: npm ERR! D:\AndroidStudioWorkspace\wowe-android-app\app\build\apollo-codegen\npm-debug.log
Desktop (please complete the following information):
- OS: Windows 11
- Android Studio Chipmunk
- node: v16.17.0
- npm: 8.15.0
@umerk44 👋 Thanks for opening this issue. Are you building your project with Amplify Android Libraries and getting an error? Also, which documentation are you referring that causes the build error with Amplify?
I am using this guide https://docs.aws.amazon.com/appsync/latest/devguide/building-a-client-app.html
I recommend using the feedback feature on those docs: https://docs.aws.amazon.com/appsync/latest/devguide/building-a-client-app.html
I'm afraid there isn't enough information to help you with this problem. Those are AppSync docs, and this is the Amplify site. If you were using Amplify's documentation, please link to the pages where you ran into the problem.
@umerk44 Judging based on the error messages (npm ERR!: ... routines:ssl3_get_key_exchange:bad signature
), it seems like that may be an issue with your installation of NPM and nothing to do with Amplify or AppSync. Please check the steps in this StackOverflow post and let us know if you are still facing problems.
Closing this issue, please let us know if you have further questions by opening a new issue.