-
Notifications
You must be signed in to change notification settings - Fork 475
"Attempt to re-open an already-closed object: SQLiteDatabase" error on a Play Store pre-launch tests #498
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
Comments
Do you have a repro or just logs? I think @krizzu worked in this area not too long ago. Any ideas? |
Yup, this is something I addressed in the v1.12.1 release. The problem was that the db connection was not closed properly, causing more issue. In your example, it looks like there was some long-running task, which accessed AsyncStorage after the app was already closed? |
Hi there @keeprock, @krizzu and @tido64 , If it's not too much trouble, I'd like to share some more info on this issue. I've recently bumped This is the log info that I can share:
I'll be going through this dependency's code and @krizzu's PR to see if I can figure it out, either way leaving this here for your eyes : ) PS: If I find more relevant info, I'll be updating this comment. Thank you again, |
Thanks @limaAniceto. Could you be so kindly to show me, which version you've got prior to bumping? I'm looking for a stable version. Got some other error reports, which may be linked to this. |
Thank you so much for getting back to me so quickly @keeprock We were previously at If there's anything else that I can find that helps you, please let me know 🙏 |
Same here, we got this crash too, alas the tracebacks are not that helpful:
Got these from Crashlytics, I don't know how to reproduce the issue. |
what is the solution |
Why is this closed? |
Still happening: ` "@react-native-async-storage/async-storage": "1.19.3", |
Still happening, when the App undergoes a hot update
crash reason
|
Uh oh!
There was an error while loading. Please reload this page.
Current behavior
In a process of releasing a bundle to the Play Store, I received an errors on a pre-launch tests. It shows up as :
«attempt to re-open an already-closed object: SQLiteDatabase /data/user/0/com.app/databases/RKStorage»
Expected behavior
App should not get any errors.
Repro steps
I've got two separate angles at which we can look at this problem.
My Sentry error system caught an exception, which may happen then an app has been closed after being put into a background (by pressing Home, I guess)
At first glance, the app is already to be closed, so why even bother? I don't know what the user actually saw, which makes me worry a bit. It doesn't happen before.
Also, there are pre-launch tests, which are mandatory before uploading an app to the Play Store. And they are showing the same errors.
Related issue - firebase/quickstart-unity#861.
Looks like a problem with pre-release test code on a Google side. But worth looking at any way, cause
async-library
being caught in an error log.Thanks!
Environment
react-native: =0.63.3 => 0.63.3
The text was updated successfully, but these errors were encountered: