Closed nagyv closed 5 years ago
@nagyv Which version of the CLI are you using? You can check using the amplify -v
command.
I'm using 0.1.38
Kaustav Ghosh notifications@github.com ezt írta (időpont: 2019. jan. 7., H, 19:14):
@nagyv https://github.com/nagyv Which version of the CLI are you using? You can check using the amplify -v command.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aws-amplify/amplify-cli/issues/665#issuecomment-452028977, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHuz63WckQcsNPXsyByQ39Vwa-41Ce-ks5vA46hgaJpZM4ZykSM .
@nagey Can you upgrade to the latest version of the CLI and try this out? I beleive we fixed this issue in the lates version. Feel free to re-open this if you're still seeing the issue.
I think you mean @nagyv
Thanks. It works.
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server *-help
channels for those types of questions.
Describe the bug I've tried to move from my own AppSync setup to Amplify, thus I was using my existing schema file when I added the
api
plugin. When I tried to push the changes, an erroneous/
appeared in the path, despite being on windows.To Reproduce Steps to reproduce the behavior:
amplify push
Expected behavior The Appsync API is created in the AWS console.
Screenshots This is the error message:
Desktop (please complete the following information):
Additional context The auth plugin was already configured and pushed before.