aws-amplify / aws-amplify/amplify-studio

Creating a Form and selecting create a new model causes error message once deployed

Open
#944 0 comments 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 with 2 fields causes the following behaviour.

https://github.com/aws-amplify/amplify-studio/assets/87995712/afd46dd3-54e2-4460-892e-10e366c5bd02

on deploying and clicking on associate a form to data model causes

https://github.com/aws-amplify/amplify-studio/assets/87995712/3997696a-ffd7-468e-8ece-1932c8114311

Workaround: refresh the page

### Expected behavior

throw appropriate errors and work as expected

### Reproduction steps

1. create form with some fields
2. click create a new model
3. click on update data model
4. deploy data model
5. click on associate a form to data model
6. click on view as end user
7. observe error message

### Project Identifier

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by following the seven reproduction steps in the issue, especially the transition from deploying the data model to associating the form and viewing it as an end user. Capture the error shown in the linked recordings and compare behavior before and after refreshing; done means the deployed form flow works without the error or has an appropriate reported error.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.