-
Notifications
You must be signed in to change notification settings - Fork 118
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
Crash in DBDelegate #334
Comments
Thanks for reporting these! Do you happen to know the steps to reproduce this? Likewise, if you can share the relevant code/parameters that the app was running at the time of the crash, that may be helpful. Also, the latest version of the SDK is v6.2.0, which contains a few bug fixes since v6.0.0, so please update to v6.2.0 and let us know if that seems to resolve any of these. Thanks! |
Yes, I anticipated this question, but unfortunately, I don't know the exact steps either, and I can only guess. Also, I can't reproduce the crash. I suspect the app's module is waiting for changes to the DropBox’s folders using specific cursors. Just in case I attached fragments of the code. The suspect module is: |
Thanks! |
This issue also happens on my end. I see quite a lot of crashes, mostly on DBDelegate line 35 or 32, but sometimes on different lines. Seems like a memory related issue which can't be reproduced easily. |
Hello there. Any news? |
@NSStalker This is still open with the team, but I don't have any update on it right now. |
@greg-db Thanks! I can't help but say that I am very keen to see some movement towards eliminating these crashes. The latest version of v6.2.0, unfortunately, did not help. |
@greg-db I know that this issue is tricky to reproduce, as I also can't reproduce it in dev environment. However, since I am using Google Crashlytics, I wonder if your team would like to get some logs to better understand the cause of this crash. You can send me detailed log requirements or even Dropbox sources files, and I can integrate them into my code. Then, once a crash is reproduced in my app, I can send you these logs for your team to analyze. We can re-iterate this process as much as needed until issue is resolved. This crash occurs almost daily on my customer devices, so there is no issue to reproduce it. |
@NSStalker Thanks for the note. @yoasha Thanks for the offer! I'll bring this up with the team to see if this is something we could do. |
Hi, |
Hi @yoasha , |
Thanks for the notes. This is still open with the team, but I don't have anything new to share unfortunately. |
Thanks for your quick response. Is there any chance you can discuss this with the team and check for a more precise status? For example, is anyone actively working on it? |
@yoasha I can't make any promises myself, but yes, I'm bringing this up with the team. |
Thank you. We look forward to receive any updates. |
Hello there.
I use Your SDK 6.0.0 in my iOS app.
Here is the crash I found in FirebaseCrashlytics:
The text was updated successfully, but these errors were encountered: