Closed shumidub closed 3 years ago
pai-vz
commented
4 years ago Hi @shumidub, we are now investigating this issue and hope to get more info about that. May I ask which version did you use before 12.1.0 and what date did you observe the error rate started to increase significantly?
shumidub
commented
4 years ago Before we used 11.4.0@aar version, now using - 12.1.0
We updated version to 12.1.0 and uploaded application to Google Play on February 11
And from February 11, we begin to detect poor success rates
shumidub
commented
4 years ago any update ?
pai-vz
commented
4 years ago This issue is still investigation. Part of the problem is caused by race condition of IO in SDK and it will be fixed in next SDK release. Others are caused by weird network issue. It seemed that our network request will be interrupted so that BE cannot receive the entire body, which caused the 400 issue. And we are still working on understanding the root reason and whether it will cause data lost or not.
BTW, did you also observe data lost after upgrade to new version of Flurry? i.e. active user, number of sessions
shumidub
commented
4 years ago Ok, thanks. Yeas, I guess some of data lost. In comparison with other analysts - with 11.4.0@aar version the difference between other analysts and flurry was about 5 % on active devices / users. But after the update to 12.1.0 version the difference is about 20 % But differnence on other analytics between each other (except flurry) was not changed
shumidub
commented
4 years ago 
pai-vz
commented
4 years ago Hi @shumidub, after investigation, I think I finally figure out what's going wrong. As I mentioned before, some 400 issues are caused by IO race in SDK, which will cause data lost. It will be fixed in next release. But that only covers small part of the issue. Most of 400 issues are caused by junk data generated by SDK and it will not cause your data lost though you will see many 400 response. We will also address the issue in the next release.
You mentioned that Flurry showed less data than other analytics. But I did see an increase of usage compared to previous version when I checked Flurry backend. So may I ask whether there are still data difference? Has it been better or worse?
It will be of great help for us to debug if you could share more data with us. If you are OK with that, could you please let me know? For safety, I will ask our support team to reach out to you via email so that we can communicate in private channel.
shumidub
commented
4 years ago Hello, Could I try 12.3.0 version or should wait next version ?
harman-vz
commented
4 years ago Hi @shumidub,
The latest SDK release (12.3.0) will improve some of the 400 issues that are caused by the IO race condition but will not fix the entire issue, you're welcome to use this version of the SDK for now while we work on the entirety of the issue which will be fixed in the upcoming version.
Thank you for your patience.
On Sat, May 16, 2020 at 7:52 AM Artem notifications@github.com wrote:
Hello, Could I try 12.3.0 version or should wait next version ?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flurry/flurry-android-sdk/issues/14#issuecomment-629658106, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANLUISFBNR7MACD5N7NBQO3RR2SBZANCNFSM4KZB3AMQ .
After update to 12.1.0 version , I found that success rate for request with url data.flurry.com/v1/flr.do (data.flurry.com) is only 85 %. 15 % of all response code is 400 Client error
In comparison with other analysts-before that, the difference between analysts was about 5 % on active devices / users. But after the update the difference is about 20 % !!!