-
Notifications
You must be signed in to change notification settings - Fork 195
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
Unauthorized error when updating child object #3814
Comments
github-actions
bot
added
pending-triage
Issue is pending triage
pending-maintainer-response
Issue is pending response from an Amplify team member
labels
Aug 15, 2024
github-actions
bot
removed
pending-triage
Issue is pending triage
pending-maintainer-response
Issue is pending response from an Amplify team member
labels
Aug 15, 2024
This issue is now closed. Comments on closed issues are hard for our team to see. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I followed the solution described in issue - #3797 but when the child object is deleted by Admin within Lambda, it gets successfully deleted by iOS data sync does not remove it. Since all this happened within Lambda, I am not sure how to debug it. I am not seeing any failure in iOS logs. Most likely something is wrong with solution and auth rule. Below is the graphql schema
Child object is deleted via Lambda by calling GraphQL API via one of the user which is part of Admin group.
Below is the suggested schema update in Issue 3797
Below is what I have currently as I have given all permissions:
Steps To Reproduce
Expected behavior
iOS app should sync with DynamoDB as the item is deleted by DynamoDB
Amplify Framework Version
2.36
Amplify Categories
DataStore
Dependency manager
Swift PM
Swift version
5.10
CLI version
12.12.4
Xcode version
15.4
Relevant log output
Is this a regression?
Yes
Regression additional context
No response
Platforms
iOS
OS Version
iOS 17.5
Device
iPhone 15
Specific to simulators
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: