-
Notifications
You must be signed in to change notification settings - Fork 83
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
Question: Problems with custom deserializer, UnknownFieldSet #111
Comments
Or does the data type returned by the deserializer need to be a string? |
So I believe a short term solution would be to return a string. I feel like it should work with the changes in #76 I have a custom deserializer for protobufs that I use, I'll review how I'm using it. I'll post back with what I find. |
So I'm updating the linked PR to register a protocol buffer module for jackson, which should allow it to serialize properly without issues. |
I've published a new release. I believe this should resolve your issue. Please re-open if you continue to have problems. Thanks! |
In my case, server uses not |
After creating a custom deserializer, and uploading into the app, I get the following when trying to view a View which uses that message format.
Is there anyway to avoid this? #75 looks like it tried to mitigate this, but im still seeing it on master HEAD
The text was updated successfully, but these errors were encountered: