-
Notifications
You must be signed in to change notification settings - Fork 54
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
[Regression] Compressed reports are not received correctly in v2 #458
Comments
According to the stacktrace your report is not JSON at all, are you sending key-value pairs? Or trying to send with attachments maybe? |
Do you have compression on? |
Compression is on
|
If it is an regression, is there any known workaround other than downgrading? |
Turn off compression, or put a proxy in front which decompresses requests. |
Compressed Rqeuestst still won't be received correctly
|
hmm, worked for me. Could be a chunking issue which I didn't hit because my test report was too small? Needs further investigation |
Did you test it with the ACRA.init, that i provided? |
I can't reproduce this. Compressed reports are received fine no matter their size, and also with your configuration. |
Can i set a property on the acra Server to print the payload to console ? In Android Studio throught the App Inspector:
when the same Error is send with compression, it failes ans i only see gibberish in the payload due to the compression PS: To see the "correct" version in ACRA, we use a fake BuildConfig, which is an exact copy of the normal BuildConfig with an altered VERSION_CODE |
I published another release which will print the invalid json |
Thank you for the new Version,
The reason for failing is the closing ']' at the end of the stacktrace. |
from what I can see the [] are not an issue, your message says the string isn't terminated, and indeed the stacktrace should end with |
I tried to reformat the Json for better readability, i forgot to include the '{' at the start.
I only replaced sesitive data and shortened the first part of the tacktrace. |
Okay I just confirmed the inclusion of ] in a report does not cause this. I have no idea why your report is cut off. Is it always the same number of symbols before the cutoff? |
The number of symbols before the cutoff is different. A closing |
After updating to the current(04.10.2023) "next"-version, the server can no longer receive reports from the clients.
On the stable release it worked fine.
A reason for that could be, that we dont send all the ReportFields in our reports.
We send only the following:
The text was updated successfully, but these errors were encountered: