aws-amplify / aws-amplify/amplify-studio
data model with `subscriptions: {level: public}` causes `An error occurred while interacting with the data provider` error
- 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
d3agmbof1zzckq
### 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
Utilizing a model as follows
```
type Message @model(subscriptions: {level: public}) @auth(rules: [{allow: public}]) {
id: ID!
text: String
type: String @index(name: "messagesByDate", queryField: "messagesByDate", sortKeyFields: ["createdAt"])
createdAt: String
}
```
shows the following in data manager
redeploying as provided in the banner does not mitigate issue
additionally observed the following
data manager works as expected
### Expected behavior
dont show banner
### Reproduction steps
1. deploy the schema
2. open data manager and observe banner
3. click on redeploy
4. and still observe banner
### Project Identifier
_No response_
### Additional information
_No response_
Contributor guide
Research direction
Start by deploying the shown Message schema and opening Data Manager in the dev environment to reproduce the provider error banner. No source file or test is named; done means the banner no longer appears for this schema and redeploying is no longer required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, graphql
- Domain
- backend-api-design, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100