Fixed
Status Update
No update yet.
Comments
yu...@google.com
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.
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.
il...@google.com
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
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
ma...@gmail.com
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
You can technically implement this outside room by providing your logging support sqlite open helper.
you can also consider sending a CL ? :)
Description
It would be great if we can work around this bug somewhere in the support library so that app developers can easily avoid this issue just by updating the SDK and rebuild their apps.
Typical steps to reproduce this issue (if the app is suffering from
1. Launch the app.
2. Hit the back button on the NavBar.
3. Wait for a while.
Expected behavior:
InputMethodManager#mServedView and InputMethodManager#mNextServedView should be null.
Actual behavior:
InputMethodManager#mServedView and/or InputMethodManager#mNextServedView still holds a strong reference to View object.