-
Notifications
You must be signed in to change notification settings - Fork 33
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
java.net.ProtocolException: Unexpected tag 0 #457
Comments
Thank you for all the details. It seems like the file had a wrong data format somehow. Do you remember if your app was suddenly killed by the OS at some point before this issue happened? I'm asking because the only thing that comes to my mind would be that the writing process got abruptly interrupted.
I think you've properly configured everything so this seems to be something we have to take care of in the diskbuffering lib, I'm currently working on a refactor so for the time being I'll leave this issue open to take a detailed look afterward. If you happen to see this issue again it'd help a lot if you could let us know just to get an idea of how often something like this can happen. |
Hi, thanks for feedback! I faced the issue only in emulator just only once, and the problem could be related to a really fast "Re-Run" of the application in Android Studio |
Thanks for letting us know @esdrasdl
Disk buffering is disabled by default so I'd recommend taking a look at the |
Is anyone able to provide a repo that reproduces this? Was it a one-time occurrence? |
Hi,
We are using version 0.6.0.
And we got an exception:
The related Opentelemtry intializations:
I located three files in cache folder so I attached them (I added manually the .txt extension, since the Github doesn't support the original format):
1719496845682.txt
1719496186206_b18ab147-65a4-4c1a-ab39-30ae9ed36001.tmp.txt
1719496186206.txt
The otel integration was worked without problem before, and the error occured in an android emulator.
What can I do? The App completly stopped.
(After cold boot of emulator device, the error has gone)
The text was updated successfully, but these errors were encountered: