aws-amplify / aws-amplify/amplify-studio

creating a new form and select create a new model causes loading state

Open
#943 1 comment 0 reactions 0 assignees View on GitHub
bug studio-ui ui-forms
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

di7zhb52ymmnt

### Region

us-east-1

### Environment name

dev

### 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

creating a new form in project that does not have API and uses a imported storage causes the following loading behaviour.

https://github.com/aws-amplify/amplify-studio/assets/87995712/300de801-c220-4844-9337-6a55bacfb46f

![image](https://github.com/aws-amplify/amplify-studio/assets/87995712/c289f890-cc1e-47ef-9258-2975ae0383aa)

### Expected behavior

throw error message

### Reproduction steps

1. create a new app
2. import a storage S3 bucket
3. create a form and and add a new field
4. click create a new data model

### Project Identifier

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the flow described: create an app without an API, import an S3 storage bucket, create a form, add a field, and choose “create a new data model.” Trace the form and data-model creation entry points to identify where the loading state fails; done means the flow reports an error instead of remaining stuck loading.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.