Error Running Amplify Push after Running Amplify Auth Update
I followed the instructions here to add authentication for my iOS app. I first ran amplify auth update, followed through all the steps, and then ran amplify push. However, amplify push failed with the following error:
/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/index.js:13
throw up;
^
Error: ENOENT: no such file or directory, stat '/Users/yunfeiguo/Documents/programming/zhiyouios/amplify/#current-cloud-backend/api/zhiyou'
Any idea what might the issue be here?
amazon-web-services aws-appsync aws-amplify aws-ios
asked Nov 28 '18 at 19:56
Sarah GuoSarah Guo
668
add a comment |
I followed the instructions here to add authentication for my iOS app. I first ran amplify auth update, followed through all the steps, and then ran amplify push. However, amplify push failed with the following error:
/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/index.js:13
throw up;
^
Error: ENOENT: no such file or directory, stat '/Users/yunfeiguo/Documents/programming/zhiyouios/amplify/#current-cloud-backend/api/zhiyou'
Any idea what might the issue be here?
amazon-web-services aws-appsync aws-amplify aws-ios
asked Nov 28 '18 at 19:56
Sarah GuoSarah Guo
668
add a comment |
I followed the instructions here to add authentication for my iOS app. I first ran amplify auth update, followed through all the steps, and then ran amplify push. However, amplify push failed with the following error:
/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/index.js:13
throw up;
^
Error: ENOENT: no such file or directory, stat '/Users/yunfeiguo/Documents/programming/zhiyouios/amplify/#current-cloud-backend/api/zhiyou'
Any idea what might the issue be here?
amazon-web-services aws-appsync aws-amplify aws-ios
asked Nov 28 '18 at 19:56
Sarah GuoSarah Guo
668
I followed the instructions here to add authentication for my iOS app. I first ran amplify auth update, followed through all the steps, and then ran amplify push. However, amplify push failed with the following error:
/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/index.js:13
throw up;
^
Error: ENOENT: no such file or directory, stat '/Users/yunfeiguo/Documents/programming/zhiyouios/amplify/#current-cloud-backend/api/zhiyou'
Any idea what might the issue be here?
amazon-web-services aws-appsync aws-amplify aws-ios
amazon-web-services aws-appsync aws-amplify aws-ios
asked Nov 28 '18 at 19:56
Sarah GuoSarah Guo
668
asked Nov 28 '18 at 19:56
Sarah GuoSarah Guo
668
asked Nov 28 '18 at 19:56
Sarah GuoSarah Guo
668
asked Nov 28 '18 at 19:56
Sarah GuoSarah Guo
668
asked Nov 28 '18 at 19:56
Sarah GuoSarah Guo
668
668
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I did the following and it resolved my issues.
Follow the instructions here and call amplify hosting add.
Then move the api and auth folders and their content from the backend folder to the #current-cloud-backend folder.
Then run amplify push.
answered Nov 29 '18 at 19:17
Sarah GuoSarah Guo
668
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53527155%2ferror-running-amplify-push-after-running-amplify-auth-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I did the following and it resolved my issues.
Follow the instructions here and call amplify hosting add.
Then move the api and auth folders and their content from the backend folder to the #current-cloud-backend folder.
Then run amplify push.
answered Nov 29 '18 at 19:17
Sarah GuoSarah Guo
668
add a comment |
I did the following and it resolved my issues.
Follow the instructions here and call amplify hosting add.
Then move the api and auth folders and their content from the backend folder to the #current-cloud-backend folder.
Then run amplify push.
answered Nov 29 '18 at 19:17
Sarah GuoSarah Guo
668
add a comment |
I did the following and it resolved my issues.
Follow the instructions here and call amplify hosting add.
Then move the api and auth folders and their content from the backend folder to the #current-cloud-backend folder.
Then run amplify push.
answered Nov 29 '18 at 19:17
Sarah GuoSarah Guo
668
I did the following and it resolved my issues.
Follow the instructions here and call amplify hosting add.
Then move the api and auth folders and their content from the backend folder to the #current-cloud-backend folder.
Then run amplify push.
answered Nov 29 '18 at 19:17
Sarah GuoSarah Guo
668
answered Nov 29 '18 at 19:17
Sarah GuoSarah Guo
668
answered Nov 29 '18 at 19:17
Sarah GuoSarah Guo
668
answered Nov 29 '18 at 19:17
Sarah GuoSarah Guo
668
668
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53527155%2ferror-running-amplify-push-after-running-amplify-auth-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
