-
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
Support Realm Java 3.7.2 #62
Comments
3.7.1+ |
Workaround for now? To which version must I downgrade? |
@LaurieScheepers Stetho-Realm would need to replace |
@LaurieScheepers with Realm 3.5.0 works fine. |
I've created #58, which cover this one. Could you check it? |
Thanks for the info. I'll keep an eye out for the next release. |
This PR seems to contain all the necessary changes for this to work: #58 |
Any updates? |
@abou7mied you can use the source code in #58 directly for 3.7.1/3.7.2 (maybe even 4.0.0-RC1) |
When opened in Chrome, display a blank。 Device : Lib : Application code : Realm.init(this);
Stetho.initialize(
Stetho.newInitializerBuilder(this)
.enableDumpapp(Stetho.defaultDumperPluginsProvider(this))
.enableWebKitInspector(RealmInspectorModulesProvider.builder(this).build())
.build()); |
Any updates on this? |
Yeah any ETA's? I would like to upgrade all my dependencies to the latest versions and not keep old versions just for compatibility's sake. Please guys let me know when the next release will be available where this is fixed? |
Yeah, it will be really nice if we can update to latest version (>4.0.0) |
I published temporary maven repo on my github repository until maintainer coming back. It tested on realm 4.0.0. Please let me know if there is a problem Edit: |
@wickedev and @AleksanderMielczarek (I believe you two are responsible for this release) I have test your solution with Realm Java 4.1.1 and so far so good, thanks for your work. Let's hope the maintainer release your version sooner on the official repository. Thanks again. |
I'm getting this exception when trying to open a 4.1.1 db :
|
@mrp14 Can I get more detail like realm configuration, stetho_realm version for that issue? |
I used the 2.2.0 version you published, with Realm 4.1.1 and Stetho Realm 1.5.0. Here is the Realm configuration :
MyRealmMigration.migrate method does nothing. I do have various active change listeners while trying to open the database using Stetho. Could it be related ? |
+1 |
I also had a problem: So, i found solution: instead : need to use: @wickedev or @AleksanderMielczarek please make this change to your repo, i'll use it for my proj, thx you for your work. |
@AScri |
Works fine for me with 2.2.1 version ! Thanks @AScri @wickedev and @AleksanderMielczarek |
I also had a problem: The whole exception:
When i'm on a table with no link to another Entity working find (and on table with link and no data). Thanks you again for your previous work! |
@fkizewski 2.2.1 supports Realm 4.0.0+ |
@Zhuinden My bad! Thanks. So, do you know if there is a stetho version for Realm 3.7.2? Or i need to update my Realm database to 4.0.0+? |
There are so many core fixes in 4.x compared to 3.7.2 that it's probably worth it either way. I recommend 4.1.1 (current latest) |
@Zhuinden Thanks i'll do it! |
Working like a charm, thanks a lot both of you |
@wickedev can I count on it to work? realm 3.7.2
|
@hram Unfortunately, The problem is that some class has changed internally since Realm 4.2.0. Therefore, to use 4.1.x or less, you must use version stetho-realm 2.2.1. |
@hram realm/realm-java#5482 If you need to support 3.7.2, then you should fork the project and rename |
@xamantra I suppose that is not about realm-stetho. did you try to use stetho without realm and stetho? |
@xamantra Can you please help me with this issue? https://stackoverflow.com/questions/50700497/how-to-displays-realm-database-content-on-android-device/50701211#50701211 |
@yozhik It think it is not about realm and stetho .it is your gradle project having an issue..try to 'Clean' or 'Rebuild' your project. |
Hello @wickedev , sorry for late reply. I think it is also an emulator issue, because my friend uses genymotion for debugging and it is working for him, and I use Nox emulator and it doesn't work, that is my conclusion right now.. |
Okay, I tested it with Genymotion and android studio emulator and it both works!!.. |
Now the only thing I'm honestly wondering about is why we're f***ing around with LinkView and SharedRealm if we could just be using the same RealmConfiguration as we use for getting a Realm instance, then get all this schema data via the DynamicRealm API. |
@wickedev works fine with Realm 5.7.0 Thank you! |
@wickedev I have another problem. |
@kylin17 well if you are using If you are NOT using |
@Zhuinden Thank you very much for your help. 👍 |
wickedev Excelent!!
|
Thank you so much, tested on Realm 5.1
// Log.i(TAG, realmConfig.getSchemaVersion() + "scheme ver");
|
I am working on a react native project with realm 6.0.3. I am getting crash on clicking default.realm in sources tab of developer tools. Below is my code for the integration:
|
So what's the crash |
Ah. It's unfortunate I never took the time to rewrite this thing. Everything that Realm-Stetho does could be done with the DynamicRealm API and I think it wouldn't have this shady "connection lost" issue randomly. |
@Zhuinden So, how should I proceed? Would I be able to use stetho-realm or not? And issue is not random. It is occuring everytime I try to open |
Well, try to check if you have |
Planning to support Realm 10? I have
debugImplementation 'com.uphyca:stetho_realm:2.3.0';
and getting the following when I expand the DB dropdown in Chrome.
Used to work just fine with Realm 6 but I have recently upgraded quite a lot of app dependencies. |
It mostly depends on whether @wickedev is up for it or no longer maintaining his fork. Tbh even when I made the 2.3.0 edit, my lingering thought was "this should have been using the DynamicRealm API since 2.0", then this wouldn't be an issue |
I'm sorry, but I'm not using realm anymore, and I don't have time to maintain it recently. @Zhuinden I think it's a good idea to create a new fork repository. |
Fair enough, it's not a huge issue to be honest since Android Studio provides an easy way to access the realm file and open it in Realm Studio. |
@wickedev Did you delete your repository recently? Do you know of any forks of your repository that might still exist? Thanks! EDIT: Found one: https://github.com/dexcom-inc/stetho-realm |
Someone should update it to use DynamicRealm |
@TadeasKriz @Zhuinden |
Moved from realm/realm-java#5260
The text was updated successfully, but these errors were encountered: