aws-amplify / aws-amplify/amplify-studio
Error keeps appearing, preventing me from syncing with Figma or updating forms
- Dominant language
- No language data
- Stars
- 135
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
### Before creating a new issue, please confirm:
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-ui/issues?q=is%3Aissue+) and [discussions](https://github.com/aws-amplify/amplify-ui/discussions).
- [X] I have tried disabling all browser extensions or using a different browser
- [X] I have tried deleting the node_modules folder and reinstalling my dependencies
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-ui/blob/main/CONTRIBUTING.md#bug-reports).
### On which framework/platform are you having an issue?
React
### Which UI component?
Other
### How is your app built?
cra
### What browsers are you seeing the problem on?
Chrome
### Which region are you seeing the problem in?
us-east-1
### Please describe your bug.
I have seen this error appear that says "failed to save The number of resources passed must be greater than 0 and less than 100". this appears usually when I'm configuring a form or imported component from Figma. At the top, instead of saying "changes saved", it shows this error. Now I can't import from Figma without getting this error.

importing
### What's the expected behaviour?
this should not appear, or point to a previous form configuration where the problem is originating from.
### Help us reproduce the bug!
I'm not sure how to
### Code Snippet
```typescript
// Put your code below this line.
```
### Console log output
_No response_
### Additional information and screenshots
_No response_
Contributor guide
Research direction
Start with the Figma import and form-configuration flow described in the report, using the reported resource-count error as the first observation. Reproduce the failed save if possible and trace it to the earlier form configuration; done means imports and form updates no longer show the error, or the UI identifies the originating configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- figma, react
- Domain
- design, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100