-
Notifications
You must be signed in to change notification settings - Fork 206
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 sync failing for connected Model without auth directive #622
Comments
hi @aken27, It appears the provisioned backend requires owner authorization on Items when there is a connection from Categories when Categories require owner auth. The library is not aware of this requirement since it is not explicitly added on the Items type. We can take this as a bug and make sure the library can account for this case. A workaround here is to specify
|
This issue is stale because it has been open 14 days with no activity. Please, provide an update or this will be automatically closed in 7 days. |
@wooj2 and @diegocstn this seems related to the work you have been doing. Can you double check if this issue is still relevant? |
Hi @aken27, There's also a separate issue with the usage of I'd suggest as a workaround to update the schema
|
This issue is stale because it has been open for 14 days with no activity. Please, provide an update or it will be automatically closed in 7 days. |
This issue is being automatically closed due to inactivity. If you believe it was closed by mistake, provide an update and re-open it. |
Hi, I am also facing same issue while using graphql api with amazon cognito as default authentication. It continuously tries to connect to the api but always failing. I have taken care of everything as mentioned by @lawmicha for @auth directive. My ios App is unable to sync the data with the cloud. I have checked the recieptmodel app by @lawmicha and has done everything same like it but still I'm not able fulfill my purpose. I am attaching my schema with it and even though I have signed in still the app is unable to connect with the api.


Originally posted by @aken27 in #561 (comment)
The text was updated successfully, but these errors were encountered: