-
Notifications
You must be signed in to change notification settings - Fork 58
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
AppSyncCustomNetworkInvoker JSON parse error when data is null due to mutation validation errors on server #292
Comments
This bug prevents us from learning that an offline mutation eventually fails, unlike iOS. It's only a one-line fix. I hope you can prioritize it. Thanks! |
Is there a chance you can address this issue? We believe it's a one-line fix, and it will un-block us. Thanks, we appreciate your help in advance. |
To be clear, the fix is to replace this line:
with this:
|
@doc-rj-celltrak thanks, looks reasonable. Our on-call engineer is having a look. |
@doc-rj-celltrak Thanks for your suggestion. We've merged the fixing PR. Will do a release this week. |
Great, thanks @changxu0306 and @jamesonwilliams |
A PR with the fix for this issue was released as part of version 3.1.3. |
Referenced line assumes that there will always be a data object returned for a mutation. This is not true when validation fails - only the errors field is set. This should probably use optJSONObject.
aws-mobile-appsync-sdk-android/aws-android-sdk-appsync/src/main/java/com/amazonaws/mobileconnectors/appsync/AppSyncCustomNetworkInvoker.java
Line 243 in 8cf6844
The text was updated successfully, but these errors were encountered: