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
StackOverflowError on App start #855
Comments
I guess I found what causes the issue: Lots of zero bytes length files. And also lots of this on log:
|
This stack overflow error is when processing a zero length Any chance you can extract and attach the largest |
All and I also have a lot of Zero bytes Anyway, I saved all files here: PS is there a way for me to "work around" these crash when sending a crash situations? |
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. |
To test a pre-release of the SDK you can point your
And use version At end of November you will be able to remove this pre-release repository and switch to 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. |
@guperrot 24h and no crash! thank you very much for the quick turn-around. |
You're welcome, we keep the bug opened until we release the SDK end of month. |
@guperrot hey there, installed over the weekend on 3 QA machines, and so far no zero files or leftovers to be seen. |
Version 1.10.0 has been officially released. |
Description
StackOverflowError during app start
Repro Steps
Please list the steps used to reproduce your issue.
Details
Which SDK version are you using?
Which OS version did you experience the issue on?
What device version did you see this error on? Were you using an emulator or a physical device?
What third party libraries are you using?
Please enable verbose logging for your app using
AppCenter.setLogLevel(Log.VERBOSE)
before your call toAppCenter.start(...)
and include the logs here:I will work on collecting the logs, as I need a new deploy, but for now, here is the stack trace:
The text was updated successfully, but these errors were encountered: