-
Notifications
You must be signed in to change notification settings - Fork 114
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
Fails to return database tables with Realm 2.0 #37
Comments
+1 |
@Dragas Are you still running into this? Have you seen what might be causing it? I'm running into it too, and I'll start trying to debug it this weekend - but in the meantime if there is something you're running into that's obvious, it could be helpful. |
@sureshjoshi I still am running into it, but I didn't see anything else that looked obvious. Looking into other issues, #35 seems to be related as I'm getting the same downward arrow, signaling that database was expanded, without actual tables in it. Adding name parameter hides the Then again, I didn't look much into it since debugging contents of the database wasn't my project's priority. Others who upvoted this issue seem to be running into it as well. |
So, I found one problem. It's how the Realm instance is being opened (a little bit roundabout right now). However, essentially, if you have a named Realm instance, it will fail to open. If you remove the name of your database (keeping with the default.realm file) it will work. This also poses a problem when you have multiple databases - as only one will get opened, but the data will display as the same for both. |
@Dragas You can check out my PR to see how I got around this:
|
+1 |
I've released 2.1.0 that contains the fix. |
As of the latest realm update, stetho fails to return database tables and dumps the following into the console.
If stetho initialization for Realm 2.0 differs in any way from Realm 1.2, shouldn't it be mentioned in the readme.md?
The text was updated successfully, but these errors were encountered: