IssueTracker

Is there any hope that this will be looked at any time soon?
I find it pretty disappointing that there is no way to debug queries. I am using Room in an application with foreign key relationships, and these are failing silently and for some mysterious reason, and I have no way to debug my queries other than manually adding a bunch of LogCat logs.
Thank you for considering this.

Hello

Room database looks very promising and interesting, But I am still on initial stage of learning it and I am facing the problem of not being able to see log outputs of the database.
While implementing / learning debugging should be enabled.

It would be extremely helpful if we can have debugging logs for Room database implementation.

Thanks and regards
Abhiroop Nandi Ray

sorry, we are not agianst this feature but it is just not a high priority right now.
You can technically implement this outside room by providing your logging support sqlite open helper.

you can also consider sending a CL ? :)
https://android.googlesource.com/platform/frameworks/support/+/androidx-master-dev

I have been able to achieve it via a very hackie way
Please refer to
https://stackoverflow.com/questions/46172417/android-room-database-dao-debug-log/53693849#53693849 
or
https://gist.github.com/aasaandinesh/6e4cf206bd1bb56966954cabc42128dd

Will try to do it in a proper way

You can log Room's Sqlite queries on emulator, see: https://stackoverflow.com/a/54963655/1233652

This is needed for asserting query execution and increasing the speed of adoption of the framework. Please prioritize higher as simple as it is.

Please, it would be very helpful for developers to be able to debug room operations in an easy way.

Please, it would be very helpful for a more complicated erd, prioritize higher as soon as possible.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit ab6d205c0217a0ed5c170bf6ceadb20422947699
Author: Elif Bilgin <elifbilgin@google.com>
Date:   Tue Nov 17 13:50:26 2020

    Implementing functionality for a general callback function for SQLite queries. If possible, bind arguments are provided to the callback in addition to the SQLite query statement. This callback may be used for logging executed queries, in which case it is recommended to use an immediate executor.
   
    This CL will be followed up by a CL resolving b/174478034.
   
    Test: Tests have been added QueryInterceptorTest.kt
   
    Relnote: Add query callback feature to Room.
   
    Bug: 74877608
    Change-Id: Iaa513e39115f0c9c68359774fa70e1d3dd022c39

A       room/integration-tests/kotlintestapp/src/androidTest/java/androidx/room/integration/kotlintestapp/test/QueryInterceptorTest.kt
M       room/runtime/api/current.txt
M       room/runtime/api/public_plus_experimental_current.txt
M       room/runtime/api/restricted_current.txt
A       room/runtime/src/main/java/androidx/room/QueryInterceptorDatabase.java
A       room/runtime/src/main/java/androidx/room/QueryInterceptorOpenHelper.java
A       room/runtime/src/main/java/androidx/room/QueryInterceptorOpenHelperFactory.java
A       room/runtime/src/main/java/androidx/room/QueryInterceptorStatement.java
M       room/runtime/src/main/java/androidx/room/RoomDatabase.java

https://android-review.googlesource.com/1502194

we normally do (bake RCs 2 weeks). this was the push to ship things at IO :/ (conference deadlines).
and this bug was in beta but unfortunately didn't get caught until now :/

sorry about the issue, we'll ship a 1.1.1 RC soon.

No it's not just a log problem. I added the migration of adding new column of string, in the first launch the first insert fails. So the data is lost.

In my case, the error looks like:
 Cannot run invalidation tracker. Is the db closed?

    java.lang.IllegalStateException: The database '/data/data/com.pushcoin.app.reggie.debug/databases/reggie_transaction.db' is not open.

shipped in 1.1.1-rc1.
that CL only includes this fix so hopefully safe to migrate to .

I had same issue like Cannot run invalidation tracker. Is the db closed? on room version 1.0.0, but just log issue. (it didn't occur crash)
And I checked it was fixed on room version 1.1.1-rc1. I wonder when the official 1.1.1 version will be released?

we are just letting rc-1 bake to see if any error shows up. going clean so far so might release it in a week or two.
feel free to use it, it does not have any additional features etc.

I see this bug as really critical and would like to see a warning right here:
https://developer.android.com/topic/libraries/architecture/adding-components#room

That it crashes on migrations and strongly recommend users to use a previous version or the RC.

I'm getting this as well (when inserting a row after migrations), but I'm using the new Jetpack dependencies (androidx.room:room-runtime:2.0.0-alpha1). It sure seems as if the fix isn't included in that, but I wanted to double check in case the issue just hadn't been truly resolved yet.

Yup how about androidx 2.0.0-alpha1?

we'll ship a new version of androidX room to fix that. and hoping to ship 1.1.1 this week, we've not received any bugs and we see many people using it so should be fine by now.

Is this fix now ? I'm having this issue!

I could see 1.1.1 is shipped at 6/19 but androidX room hasn't released yet. :(

I am also facing the same issue

it is already shipped so please try with the latest version

it is still happened with version 2.2.0-rc01

Hitting the same issue in Room 2.2.3. Looks like it was fixed in 1.1.1-rc1 according to some old comments, but it's broken again in Room 2.X.X.

Crashing on Oneplus 6t Android 10. We're closing the database in onDestroy and seems like the only solution is to not close the database?
Room version 2.2.5

Crashing on Room 2.2.0:

Device:
Pixel XL
Android 10
Security patch: October 6, 2019
Kernel: 3.18.137-g72a7a64494e
1 Fri Sep 27 18:40:34 UTC 2019
Build number: QP1A.191005.007.A3

After few days i found solution!

I got same issue like #4. And it comes on some devices like OnePlus 6t because application relaunch MainActivity at start, so when we call database.close() in activity OnDestroy() we also need set 'null' to database instance (if you use singleton class for working with your database). So i created my own function on my singleton database class and call it on in activity OnDestroy() function. Hope its helpful!

My database class:
abstract class AppDatabase: RoomDatabase() {
    abstract fun TestDao(): TestDao

    companion object {

        @Volatile
        private var INSTANCE: AppDatabase? = null

        fun getDatabase(context: Context): AppDatabase{
            val tempInstance = INSTANCE

            if(tempInstance != null){
                return tempInstance
            }

            synchronized(this){
                val instance = Room.databaseBuilder(
                    context.applicationContext,
                    AppDatabase::class.java,
                    "database_name"
                    )
                        .build()
                INSTANCE = instance
                return instance
            }
        }

        fun closeConnection() {
            if(INSTANCE != null){
                Log.i("room", "reset instance")
                INSTANCE!!.close()
                INSTANCE = null
            }

        }
    }
}