StackOverflowError on App start about appcenter-sdk-android

[codeknox]

@guperrot hey there, installed over the weekend on 3 QA machines, and so far no zero files or leftovers to be seen.
Again, thank you for the promptly turn-around.

[codeknox]

I guess I found what causes the issue:

Lots of zero bytes length files.

And also lots of this on log:

10-30 10:55:02.998 2145-2164/? D/AppCenterCrashes: Process pending error file: /data/data/com.XXXXXX.YYYYYY/files/error/b2283cf7-4275-48fb-ba94-c8546385734a.json
10-30 10:55:03.008 2145-2164/? E/AppCenterCrashes: Error parsing error log
    org.json.JSONException: End of input at character 0 of 
        at org.json.JSONTokener.syntaxError(JSONTokener.java:450)
        at org.json.JSONTokener.nextValue(JSONTokener.java:97)
        at org.json.JSONObject.<init>(JSONObject.java:154)
        at org.json.JSONObject.<init>(JSONObject.java:171)
        at com.microsoft.appcenter.ingestion.models.json.DefaultLogSerializer.deserializeLog(DefaultLogSerializer.java:59)
        at com.microsoft.appcenter.crashes.Crashes.processPendingErrors(Crashes.java:644)
        at com.microsoft.appcenter.crashes.Crashes.onStarted(Crashes.java:367)
        at com.microsoft.appcenter.AppCenter.finishStartServices(AppCenter.java:871)
        at com.microsoft.appcenter.AppCenter.access$600(AppCenter.java:49)
        at com.microsoft.appcenter.AppCenter$8.run(AppCenter.java:793)
        at android.os.Handler.handleCallback(Handler.java:615)
        at android.os.Handler.dispatchMessage(Handler.java:92)
        at android.os.Looper.loop(Looper.java:137)
        at android.os.HandlerThread.run(HandlerThread.java:60)

[guperrot]

This stack overflow error is when processing a .throwable file with many nesting of exceptions to reconstruct the Throwable that caused crash after restart so it can be accessed via SDK API for inspection.

zero length .json files is a separate issue but can be caused by the crash loop and just be a consequence of the first issue. Though we should delete files that we cannot read, looks like they accumulate in your case so need to check cleanup code to make sure they are deleted.

Any chance you can extract and attach the largest .throwable file that you have? With the .json file having the same uuid. Thanks in advance.

[codeknox]

All .throwable files are same size:

and I also have a lot of Zero bytes .json without the .throwable related file:

Anyway, I saved all files here:
https://www.dropbox.com/s/tu3lgk1v3xru9s1/error.zip?dl=0

PS is there a way for me to "work around" these crash when sending a crash situations?

[guperrot]

Thanks for sharing the files, we are working on a SDK work around. I am not sure how you can work around without us fixing the SDK so we will share a pre-release of it when the fix is ready.

[guperrot]

To test a pre-release of the SDK you can point your app/build.gradle file at

repositories {
    maven {
        url "https://dl.bintray.com/vsappcenter/appcenter-snapshot"
    }
}

And use version 1.9.1-2+bc7c1c6f (only this very specific version has the pending fix).

At end of November you will be able to remove this pre-release repository and switch to 1.10.0 instead.

This quick fix prevents the crash loop but we are still working on the pull request to improve the behavior.

If your application is published and other users of your application might see the same issue, we thus recommend using the pre-release for the time being. If you believe only your test device is impacted then clearing storage of the application or uninstalling/reinstalling might be an option.

[codeknox]

@guperrot 24h and no crash! thank you very much for the quick turn-around.

[guperrot]

You're welcome, we keep the bug opened until we release the SDK end of month.
We have another prerelease version that also cleans the empty/invalid files now: 1.9.1-3+2430ff4b, it also fixes errors at write time on top of the read ones.

[guperrot]

Version 1.10.0 has been officially released.