Crash - didn't find class "io.realm.internal.network.NetworkStateReceiver"

[lukcz]

Hi, with the new Realm 2.0 I am getting crash as below:

java.lang.RuntimeException: Unable to instantiate receiver io.realm.internal.network.NetworkStateReceiver: java.lang.ClassNotFoundException: Didn't find class "io.realm.internal.network.NetworkStateReceiver"

[Zhuinden]

Did you do a Clean + Rebuild? (you should)

Do you have Instant Run disabled? (you should)

[zaki50]

I reproduced this.

conditions:
syncEnabled is false.
android.net.conn.CONNECTIVITY_CHANGE broadcast is fired.

The easiest way to reproduce this is to execute adb shell am broadcast -a android.net.conn.CONNECTIVITY_CHANGE

[peterbetos]

This is reproducible.

[mikelis-kaneps]

Yes, I have the same problem. Is there a way how to fix this?

[Zhuinden]

2.0.1 will fix it

[r-cohen]

++;

[mishindmitriy]

I have the same problem

[usernotnull]

+1

[smoonsf]

+1

[EspoirX]

I have also encountered this problem

[zaki50]

already fixed in releases branch.
please wait a bit

[lyfebackup]

Same here, when can we expect 2.0.1?

[cmelchior]

@Dimous Only our Mobile Platform Extension does that. Mostly because it allows us to do more intelligent error handling.

We hope to be able to ship 2.0.1 today with a fix for this, and sorry for letting such a server error slipping through 😢

[Domacoski]

+1

[samvanderhyden]

+1

[GulajavaMinistudio]

Same here, when can we a bug fix release ?

[ghost]

+1

[hateum]

is there any way to prevent the crash ?

[Zhuinden]

Well until 2.0.1 is released, you can add a broadcast receiver by the same name in the same package and all that.

[hateum]

I added this class to my project with the same package Realm and now there is no crash.
https://github.com/realm/realm-java/blob/1062d2462eaf841c215d7962dea979f65032fb5a/realm/realm-library/src/objectServer/java/io/realm/internal/network/NetworkStateReceiver.java
Thanks

[pauloleitemoreira]

+1

[takke]

+1

[avalenzuelac]

+1

[shahrukhamd]

I shipped my app to production with Realm 2.0.0 and because of this issue my crash free users are at 17.5% only (down from 99.8%). Please fix that issue ASAP.

I am thinking about removing Realm altogether as my database model is pretty simple.

[pratamawijaya]

+1

[cchcc]

+1

[ezanetta]

+1

[jsadovskaya]

+1

[fuwaneko]

I also shipped an app like @shahrukhamd, and it's horrible now. We depend on third-party libraries and expect releases to be stable and well-tested. This is critical issue and it can potentially destroy your reputation since it's been 7 days already. Also my app now is never closed by the system since Realm listens to network changes. This is totally unacceptable. I understand you want to make money, but it should not interfere with my application in a way that changes it's behaviour. That was the reason I dropped Firebase Crashes in favour of Fabric, since Firebase launched separate process to track crashes which is what I totally don't want.

[cmelchior]

Hi @fuwaneko
We are sorry that this error got shipped in 2.0, and we actually wanted to ship a fix last week, but ran into some problems with our build systems unfortunately. Those should be fixed now and we plan to ship 2.0.1 today.

[fuwaneko]

@cmelchior thank you. I also hope with syncEnabled = false Realm will not listen to network changes.

[cmelchior]

It will not, it was a mistake it was in the base library. It will only be included in the sync part.

[Zhuinden]

The snapshot I tried out didn't have this issue, I think this got merged in from realm-java-private ¬¬

[estebanlagord]

+1 waiting for 2.0.1

[sankar4n]

Same here, waiting for 2.0.1 :(

[ahmadalibaloch]

Waitinggggggggggggggggg 🗡

[pishguy]

+1 and i get the same error

[JSONValidator]

+1

[Zhuinden]

It's going to happen eventually.

[kristakrebs]

+1 2.0.1

[readytopark]

+1

[allentcm]

+1

[ahmadalibaloch]

Where is the Realm team sleeping. Recently the have been boasting to release new features and this fatal bug is not resolved after weeks 👎

[Zhuinden]

@ahmadalibaloch ...man, they do know about it. Realm 2.0 has been barely out for a week, saying it hasn't been fixed for weeks is a major exaggeration and wrong, too.

If you really actually wanted to create a quick fix for this problem in the meantime, you would have just added the missing class and released a new version of your app.

https://github.com/realm/realm-java/blob/1062d2462eaf841c215d7962dea979f65032fb5a/realm/realm-library/src/objectServer/java/io/realm/internal/network/NetworkStateReceiver.java

(I am still not an official Realm person).

[pc-bszabo]

Quick and dirty solution : put this into your launcher activity OR Application=>

try {
getApplicationContext().getPackageManager().setComponentEnabledSetting(new ComponentName("your.package.name","io.realm.internal.network.NetworkStateReceiver"), PackageManager.COMPONENT_ENABLED_STATE_DISABLED, PackageManager.DONT_KILL_APP);
} catch (Exception e) {}

[Zhuinden]

I actually didn't know you could do that. Cool.

[sankar4n]

awesome @pc-bszabo! I have added the following code to Application onCreate

try {
            ComponentName componentName = new ComponentName(
                    getApplicationContext(),
                    "io.realm.internal.network.NetworkStateReceiver"
            );
            getPackageManager()
                    .setComponentEnabledSetting(
                            componentName,
                            PackageManager.COMPONENT_ENABLED_STATE_DISABLED,
                            PackageManager.DONT_KILL_APP);
} catch (Exception ignored) {}

and it works!

Someone has written a blog on disabling BroadcastReceivers

[ahmadalibaloch]

@pc-bszabo Thanks a lot.

[cmelchior]

2.0.1 has just been released fixing this bug. The network receiver is now only added if you enable Sync as well.

I could list all the technical and process difficulties involved in getting this release out the door, but in reality we just dropped the ball on this, and I'm very sorry for those of you that got affected by this. We can only strive to do better in the future.

Closing.

[ahmadalibaloch]

We appreciate your hard work. 👍

[XabierGoros]

Indeed we appreciate the work of the Realm team. On the other side, IMHO we should be more cautious when criticising and hurrying up a team like this whose software is open sourced for us.

Once again, thanks!