Fix for JsonIOException #119
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andy317fe301f8c7
previously approved these changes
Nov 27, 2024
andy317fe301f8c7
approved these changes
Dec 2, 2024
…se GsonConverter cannot work with Void type directly and throws JsonIOException
ionutmanolache-okta
force-pushed
the
JsonIOException-fix
branch
from
bff18dd to
28d8588
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was an issue where method payloadFromResponse() threw a JsonIOException when the callback type was specified as void. This happened because the GsonConverter cannot directly handle Void type. To resolve this, I added line of code that checks the callback type and returns null if callback type is Void