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.
amplify env checkout <env> should update aws-exports.js file
See original GitHub issueDescribe the bug
When you do amplify env checkout <env> the aws-exports.js file does not update, it will still contain settings of the previous environment.
To work around this, you can do amplify init and choose an existing environment and choose the <env> you checkout to.
To Reproduce
- Check
aws-exports.js - Do
amplify env checkout <env> - Check
aws-exports.js - Realize that it hasn’t changed to reflect the environment settings you are in.
Expected behavior
amplify env checkout <env> should update aws-exports.js file to reflect the settings of the current environment you checkout to.
Additional context
To work around this, you can do amplify init and choose an existing environment and choose the <env> you checkout to.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
still not solved in amplify -v 4.40.0
@aprilmintacpineda it seems to be a valid request, I marked it as a bug, thanks for reporting it.