-
Notifications
You must be signed in to change notification settings - Fork 589
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
Can instantiate RxBleClient with last Dagger release #342
Comments
Hey. Thanks for updating us. This is related to google/dagger#950 We'll let you know when the snapshot will have a workaround. |
The PR has been merged hence you can expect that the snapshot ( |
Sure, where can i find this snapshot ? |
Offcourse i passed on it and missed it...
The BLEConnectionService.java:69 line => |
Pretty strange, could you show your build.gradle regarding dependency configuration? Do you use multi dex? |
I am using multi dex yes, i have a lot of dependencies... |
This part related to rxandroidble. I'd like to be sure that you didn't exclude transitive dependencies. (or just confirm it) |
And other extra dependencies as google, support, firebase etc... |
it's was |
Yup, indeed there is a problem. We will look on it Tomorrow. |
The problem should be fixed now. You can check it by using the newest |
It's working with the last Snapshot :) |
@uKL You probably already know but the sonatype snapshot repository (https://oss.sonatype.org/content/repositories/snapshots/com/polidea/rxandroidble/rxandroidble/) has a 1.6.0-SNAPSHOT version already, yet that is the incorrect one. |
|
My project was using Even my dagger version is |
With more investigation, I found that I was getting this error because I recently migrated Fabric to Firebase Crashlytics. And the latest version of Firebase actually uses So upgrading rxandroidble to |
Happy to hear that. :) |
Summary
I faced an issue yesterday with the new Dagger release (2.14.1). At the RxBleClient creation (
RxBleClient.create(context);
) the app crash (with 2.13 and less it's ok)Library version
1.4.3
Logs from the application running with setting
The text was updated successfully, but these errors were encountered: