-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
FutureTypeAdapter.read() throws unhelpful exception #625
Comments
|
Original comment by |
Same issue here, not able to reproduce locally but find it very common in our crash reports. |
Ran into this today. One quick workaround is to have separate instances of I use Not the most memory-efficient solution but a solution nonetheless. Seems like something is getting lost when an instance is being asked to process multiple objects concurrently. |
Has this issue been resolved, ie. is there still a crash? I'm upgrading from 2.4 to 2.7 to see whether the issue remains. The sources show that the topic of this issue is still relevant; no exception messages have been added. Edit: even with version 2.7, I observed this exception. So instead I stopped using a Singleton as suggested. |
I'm gonna leave this here for posterity. We're still on 2.6.2 and are hitting this, dunno if it's fixed in newer versions. This is what I think is happening:
If I'm right, then I think calling gsonInstance.getAdapter(YourRootClass.class) after constructing your shared gson instance would work around the issue. (I'm working around it by rewriting the rats-nest of classes that we're deserializing into.) |
We are on |
Original issue reported on code.google.com by
MhaleK...@gmail.com
on 29 Jan 2015 at 5:26The text was updated successfully, but these errors were encountered: