Skip to content
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

Getting nullpoint exception when calling mutation #51

Closed
Rissmon opened this issue Oct 16, 2018 · 3 comments
Closed

Getting nullpoint exception when calling mutation #51

Rissmon opened this issue Oct 16, 2018 · 3 comments
Assignees
Labels
bug Something isn't working closing-soon pending-response Issue is pending response from the issue requestor

Comments

@Rissmon
Copy link

Rissmon commented Oct 16, 2018

Getting nullpoint exception when calling mutation with invalid id
I am having an issue with AppSync SDL. My application getting crashed when I try to update a value corresponding to an id which is not present in dynamo DB.

Environment:

AppSync SDK Version: 2.6.26

Device Information:

Device: Samsung J8, Redmi Note 5 Pro
Android Version: Marshmallow 6.0, Oreo 8.1

*Since the exception occur inside the SDK i am not able to control this situation
FATAL EXCEPTION: OkHttp Dispatcher Process: PID: 12394 java.lang.NullPointerException: Attempt to invoke interface method 'java.util.Set java.util.Map.entrySet()' on a null object reference at org.json.JSONObject.<init>(JSONObject.java:132) at com.amazonaws.mobileconnectors.appsync.InterceptorCallback.onResponse(AppSyncOfflineMutationInterceptor.java:106) at com.apollographql.apollo.internal.interceptor.ApolloCacheInterceptor$1$1.onResponse(ApolloCacheInterceptor.java:102) at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor$1.onResponse(ApolloParseInterceptor.java:84) at com.apollographql.apollo.internal.interceptor.ApolloServerInterceptor$1$1.onResponse(ApolloServerInterceptor.java:110) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:153) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) at java.lang.Thread.run(Thread.java:764)

@sunchunqiang sunchunqiang added the bug Something isn't working label Oct 22, 2018
@scb01
Copy link
Contributor

scb01 commented Oct 29, 2018

@Rissmon

Sorry to hear that you are running into issues. I will investigate this further on my side. Can you provide some more information to help debug this - specifically, can you share your appsync schema and a code snippet from your client.

@scb01
Copy link
Contributor

scb01 commented Nov 8, 2018

@Rissmon
v2.6.27 contains the fix for this issue. Please try with the updated SDK and let us know how it goes.

@scb01 scb01 added pending-response Issue is pending response from the issue requestor closing-soon labels Nov 8, 2018
@frankmuellr
Copy link
Contributor

This issue has been closed because of inactivity. Please open a new issue if are still encountering problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working closing-soon pending-response Issue is pending response from the issue requestor
Projects
None yet
Development

No branches or pull requests

4 participants