aws-amplify / aws-amplify/amplify-studio
switching to a new env after selecting a collection causes the page to show a blank page
- Dominant language
- No language data
- Stars
- 135
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-adminui/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-adminui/blob/main/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
### App Id
dov97cg8yn8j5
### Region
us-east-1
### Environment name
staging
### Figma File Version (if applicable)
_No response_
### Amplify CLI Version
_No response_
### If applicable, what version of Node.js are you using?
_No response_
### What operating system are you using?
_No response_
### Browser type?
_No response_
### Describe the bug
When switching environment after selecting a collection causes the page to redirect to a empty page
https://github.com/aws-amplify/amplify-studio/assets/87995712/fe629c63-0e25-4e49-8ba9-d0d932978e6e
### Expected behavior
redirect to the UI-builder root page or the Studio root page
### Reproduction steps
1. create 2 environments in AWS Console
2. open on env and add a component
3. create a collection and open it
4. drop the env dropdown, switch env
5. observe an empty page
### Project Identifier
_No response_
### Additional information
_No response_
Contributor guide
Research direction
Reproduce the issue through the environment dropdown after opening a collection, following the listed steps. Start at the collection view and environment-switching flow; done means switching environments no longer shows an empty page and instead redirects to the UI-builder root or Studio root page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100