Production error using Rx2Firebase

Hi @FrangSierra, I have plenty of users hitting non-fatal exceptions pointing to:

Non-fatal Exception: durdinapps.rxfirebase2.exceptions.RxFirebaseDataException
       at durdinapps.rxfirebase2.RxFirebaseDatabase$3$1.onComplete(RxFirebaseDatabase.java:130)
       at com.google.android.gms.internal.zzeck.run(Unknown Source)
       at android.os.Handler.handleCallback(Handler.java:739)
       at android.os.Handler.dispatchMessage(Handler.java:95)
       at android.os.Looper.loop(Looper.java:145)
       at android.app.ActivityThread.main(ActivityThread.java:7007)
       at java.lang.reflect.Method.invoke(Method.java)
       at java.lang.reflect.Method.invoke(Method.java:372)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1404)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1199)

As per the decompiled class, the error happens on public static Completable setValue(@NonNull final DatabaseReference ref, final Object value), but that method doesn’t seems to be using any RxFirebaseDataException instance. I can’t seem to find any logic nor explanation to why this might be happening 😕 . I’m a little bit puzzled with this, so any help you might be able to provide will be awesome!

Thanks man!

[mradzinski]

Hey @FrangSierra We just released yesterday, so I took some time and waited before calling it a victory. It seems my original assumption that the issue was related to a bug in our app which was manifesting wrongly through your library was right. As soon as we fixed the bug the non-fatal errors stopped showing up. So yeah, lets keep this issue closed and locked.

Thanks for your assistance and time!!! I owe you a couple beers!

[FrangSierra]

I added a few checks on the onFailure of the library that maybe was causing this error on your calls, anyway I have done a lot of tests using the methods and I don’t understand why this can be happening. At the moment it doesnt look to be a problem of the library, so please, keep me updated about this topic.

I will close the issue, feel free to re-open it.