Hi, so we are trying to remove jCenter dependency from our project but Zendesk messaging library is blocking us to do so as it depends on Flexbox library from jCenter. Google moved that library to their Maven repository but we can't force it as Gradle doesn't look at it as same Flexbox library. So we really need Zendesk library to be updated in order to remove jCenter dependency.
Is there any ETA when we can expect that so that we can plan our work accordingly?
We are facing the same issue here.
The Zendesk support has any solution in mind?
Same thing here. Got flexbox library error when trying to update dependencies.
Same thing here. you just need to change the flexbox version to 3.0.0 to support mavenCentral
We've faced the same issue.
Please migrate to com.google.android:flexbox:3.0.0 from mavenCentral
Thank you!
One workaround is adding the following to your build.gradle:
dependencies {
modules {
module("com.google.android:flexbox") {
replacedBy("com.google.android.flexbox:flexbox")
}
}
implementation ("com.zendesk:messaging:$zendeskMessagingVersion", {
exclude group: "com.google.android", module: "flexbox"
})
implementation "com.google.android.flexbox:flexbox:3.0.0"
Hello,
We've prioritized the fix for this issue on all SDKs will have a resolution in the near future. The work-around to upgrade to Flexbox 3.0.0 should work fine for now. Apologies for any inconvenience caused!
Hi Nataliya,
We are actively working on a resolution to this issue, but if this is blocking you, you can upgrade to Flexbox 3.0.0 as a workaround for now. Apologies for any inconvenience that this has caused you. We'll update our release notes as soon the release is complete.
Hi Mick,
In case it helps this is Intercom's fix from May 2021: https://github.com/intercom/intercom-android/commit/aea1f7f244d706eb0048ee213682448c3c0d356c.
It's literally one line of code:
- com.google.android:flexbox:2.0.1
+ com.google.android.flexbox:flexbox:3.0.0Also, super nice that you can actually see the open source code of the project no? Beautiful for debugging.
This issue has now been corrected in the most recent version for our Classic SDKs. Thanks for raising this issue in Community, and helping us to get it resolved!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Thank you so much for your post. This is something our teams are working on and recognize as a priority to update. There isn't a precise ETA for this deliverable but as soon as we have a released version of the mobile SDKs with a resolution, it will be our top priority to let our community members know. I apologize for any inconvenience this has caused you. We truly appreciate your commitment and taking the time to follow up.
Best,
Erica - Dev Support