-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DataStore multi-auth is not working with mixed owner and public auth rules #2873
Labels
bug
Something isn't working
datastore
Issues related to the DataStore category
work in progress
Issues was triaged and investigation done
Comments
1 task
royjit
added
bug
Something isn't working
investigating
This issue is being investigated
labels
Jun 9, 2023
9 tasks
Datastore plugin was not creating subscription for onCreate, onUpdate or onDelete for |
This was referenced Jun 30, 2023
Fix is released in v1, next step to verify the behavior in v2. |
Any plans for fixing this issue for v2? |
Next steps, this PR #3029 should be cherry-picked to |
9 tasks
thisisabhash
added
work in progress
Issues was triaged and investigation done
and removed
investigating
This issue is being investigated
labels
Oct 20, 2023
9 tasks
This is released in Amplify Swift v2.21.5. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
datastore
Issues related to the DataStore category
work in progress
Issues was triaged and investigation done
Describe the bug
Original issue report aws-amplify/amplify-flutter#2527 | aws-amplify/amplify-flutter#1693
Related amplify-android issue: aws-amplify/amplify-android#2399
DataStore multi-auth is not working as expected.
Take schema
When configure DataStore to use multi-auth mode with NO authenticated session:
Expected Behavior
As a developer, I want my end users to have
read
access to Model A B and C, including receiving subscription events.Actual Behavior
What happened: amplify-swift attempted to establish subscriptions for
ModelB
andModelC
using user credentials, after failure, it doesn’t attempt to establish subscriptions with API key. So the App cannot receive any update ofModelB
andModelC
while the public read is allowed on these two models.This issue is reproducible in v1, I believe it exists in v2 as well.
Steps To Reproduce
Expected behavior
See above.
Amplify Framework Version
1.29.2
Amplify Categories
DataStore
Dependency manager
Cocoapods
Swift version
5
CLI version
The latest
Xcode version
The latest
Relevant log output
Is this a regression?
No
Regression additional context
No response
Device
iPhone 14 simulators
iOS Version
iOS 16
Specific to simulators
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: