question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to add existing amplify back end to the amplify front end?

See original GitHub issue

** Which Category is your question related to? ** Auth, Storage, API

** What AWS Services are you utilizing? ** Cognito, AWS AppSync,

** Provide additional details e.g. code snippets ** I accidentally deleted my amplify frontend and I created a new one. How do I add again the existing amplify back end to the newly created amplify app?

I followed the steps on the backend tab

  1. amplify init --appId ("ID OF YOUR NEW AMPLIFY APP").

  2. Instead of amplify add CATEGORY HERE. I use amplify update CATEGORY HERE

Then amplify push

But when I check the amplify app on the AWS console there still no backend integrated to it.

Am I doing correct?

aws-amplify": "^2.1.0 @aws-amplify/cli@4.13.4

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:10 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
UnleashedMindcommented, Mar 11, 2020

Recovering the deleted Amplify Console project is not in the Amplify CLI’s normal workflow. But there’s the following hack that triggers the CLI post push check that you can try:

  1. On your local amplify project, run amplify env checkout <the-missing-endName-on-Console>
  2. open the amplify-meta.json files in both the backend and #current-cloud-backend folder, make sure the providers.awscloudformation does not contain the field `AmplifyAppId", remove it if it’s there.
  3. open the team-provider-info.json file, make sure the \<the-missing-endName-on-Console\>.awscloudformation does not contain the field `AmplifyAppId", remove it if it’s there.
  4. make a tiny dummy change in the backend, such as adding a space in in the template file of amplify/backend/storage
  5. run amplify push
0reactions
github-actions[bot]commented, May 26, 2021

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Getting started with existing code - AWS Amplify Hosting
Step 1: Connect a repository · Step 2a: Confirm build settings for the front end · Step 2b: Confirm build settings for the...
Read more >
How to connect a new amplify front end project to an existing ...
amplify pull --appId <your-project-appId> --envName <your-existing-backend-env> · amplify init and select the existing backend env if prompted
Read more >
Authentication - Create or re-use existing backend - JavaScript
Learn more about how to create an auth resource or re-use an existing auth backend for Amplify. - JavaScript - AWS Amplify Docs....
Read more >
reactjs - How to use existing amplify backend in both react and ...
Despite React and React Native can share the same Amplify backend, according to my research, if your application ...
Read more >
Sharing an AWS Amplify back end across multiple client-side ...
In this video you'll learn how to clone an existing AWS Amplify back end environment and use it in a mobile back end....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found