Firebase messaging 20.1.0 Causes crash in RxBLE library
See original GitHub issueI’ve explained the problem in detail here.
And here is a repo where the issue can easily be reproduced: https://github.com/Doophie/TestAppCrash
Note that in the first commit on that repo the crash occurs (it uses firebase messaging 20.1.0) and in the second commit, where all i did was rollback to firebase messaging 20.0.0 the crash does not occur.
Here is what the crash log looks like:
2020-02-13 09:44:57.530 20760-20760/my.package.name E/AndroidRuntime: FATAL EXCEPTION: main
Process: my.package.name, PID: 20760
java.lang.NoSuchMethodError: No static method injectMembers(Ldagger/MembersInjector;Ljava/lang/Object;)Ljava/lang/Object; in class Ldagger/internal/MembersInjectors; or its super classes (declaration of 'dagger.internal.MembersInjectors' appears in /data/app/my.package.name-Nbmle9woVCiX-2v0teYwZw==/base.apk!classes3.dex)
at com.polidea.rxandroidble.RxBleAdapterStateObservable_Factory.get(RxBleAdapterStateObservable_Factory.java:28)
at com.polidea.rxandroidble.RxBleAdapterStateObservable_Factory.get(RxBleAdapterStateObservable_Factory.java:10)
at com.polidea.rxandroidble.RxBleClientImpl_Factory.get(RxBleClientImpl_Factory.java:104)
at com.polidea.rxandroidble.RxBleClientImpl_Factory.get(RxBleClientImpl_Factory.java:23)
at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
at com.polidea.rxandroidble.DaggerClientComponent.rxBleClient(DaggerClientComponent.java:419)
at com.polidea.rxandroidble.RxBleClient.create(RxBleClient.java:54)
at my.package.name.Comm.RxBLEComm.<init>(RxBLEComm.java:109) // These are the only
at my.package.name.Comm.RxBLEComm.init(RxBLEComm.java:118) // lines in my code which
at my.package.name.RootApp.onCreate(RootApp.kt:63) // are totally unrealted to firebase
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1155)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5928)
at android.app.ActivityThread.access$1100(ActivityThread.java:200)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1656)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6735)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
2020-02-13 09:44:57.586 2989-3111/? E/NetworkController.MobileSignalController(2): showVoteIcon=false
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Updating Firebase causes RxBLE crash - Stack Overflow
So the issue was the version of the rxandroidble library was incompatible with the new firebase messaging. When I updated from.
Read more >[Solved] Android app crash when one signal notification sent
My App Crash every time I send a One Signal Push notification. note: firebase has no issue also one signal inApp message working...
Read more >RxBLE | 使用 RxJava 封装的低功耗蓝牙类库 - kandi
RxBLE is a Java library typically used in Programming Style, ... There are 7 watchers for this library. ... Updating Firebase causes RxBLE...
Read more >Updating Firebase causes RxBLE crash...anycodings
So the issue was the version of the anycodings_firebase rxandroidble library was incompatible anycodings_firebase with the new firebase messaging.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry for the delay. I was able to reproduce the issue. Let me consult this to the team. I’ll get back to you once I got an update.
Thank you and we shall now consider this issue as resolved.
I am closing this issue for now. If you want to continue the discussion just leave a comment here and we are happy to re-open this. 😃