-
Notifications
You must be signed in to change notification settings - Fork 371
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
DatabaseNotClosedException raised when notification arrives #8
Comments
Thanks for reporting the issue, we will be looking into this issue next week. Could you provide step by step instructions to reproduce this issue to help us quickly fix it? Thanks. |
Just fixed the open cursor from your stack trace as well as a few other open resources in commit 4028737 Thanks. |
jkasten2
pushed a commit
that referenced
this issue
Jul 3, 2019
jkasten2
pushed a commit
that referenced
this issue
Jul 8, 2019
1 task
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running the app in StrictMode. I get the following exception when notification comes on the app:
Finalizing a Cursor that has not been deactivated or closed. database = /data/data/com.patientapp/databases/OneSignal.db, table = notification, query = SELECT notification_id FROM notification WHERE notification_id = ?
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at android.database.sqlite.SQLiteCursor.(SQLiteCursor.java:98)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:50)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1314)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at android.database.sqlite.SQLiteDatabase.queryWithFactory(SQLiteDatabase.java:1161)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at android.database.sqlite.SQLiteDatabase.query(SQLiteDatabase.java:1032)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at android.database.sqlite.SQLiteDatabase.query(SQLiteDatabase.java:1200)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at com.onesignal.OneSignal.isDuplicateNotification(OneSignal.java:1263)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at com.onesignal.OneSignal.isValidAndNotDuplicated(OneSignal.java:1290)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at com.onesignal.NotificationBundleProcessor.Process(NotificationBundleProcessor.java:48)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at com.onesignal.GcmIntentService.onHandleIntent(GcmIntentService.java:66)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at android.os.Handler.dispatchMessage(Handler.java:102)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at android.os.Looper.loop(Looper.java:136)
12-02 17:20:45.025 4035-4044/com.patientapp E/StrictMode: at android.os.HandlerThread.run(HandlerThread.java:61)
The text was updated successfully, but these errors were encountered: