-
Notifications
You must be signed in to change notification settings - Fork 130
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
Optimistic update: Error at path "<query_with_pagination>.nextToken": missingValue #51
Comments
I'm having a similar issue, except I'm not using pagination. |
Is this bug is fixed in Release v2.6.18 ? Thanks |
@koingruc no, it's not fixed, I'm using 2.6.18 and it's bugged |
@richienko Thank you for the information. Hope it is fixed soon |
Same issue. Simply trying to implement a basic mutation with the sample code provided on the official doc page, yet getting "missingValue" from |
For those who have problem with
Reference: https://stackoverflow.com/questions/51932849/how-to-pass-aws-appsync-custom-request-header-in-ios-client/51950574#51950574 |
Any update on the issue, Is it fixed in latest 2.6.21 |
@hemant236 It is not yet fixed. You can check the changelog. |
@koingruc Is there any other framework/class that I need to import for using |
This is now fixed with SDK Version |
The query with argument within optimistic update closure will fail with "missingValue" message.
The query is paginated.
Version of AppSync:
2.6.18
Message I'm getting:
Error at path "listJobsByCustomer.nextToken": missingValue
Mutation:
updateJob(input: UpdateJobInput!): Job
Query called in optimistic update closure:
listJobsByCustomer(customerId: String, first: Int, after: String): JobConnection
JobConnection:
Code:
The text was updated successfully, but these errors were encountered: