RFIDAPI3 2.0.2.82+ dependency breaking changes


Audience
Tags

I am updating our applications to use version 2.0.2.94 coming from version 2.0.1.29.
We are currently using a logging library called logback-android. Which works 100% out of the box with version 2.0.1.29 of RFIDAPI3

I have ran into a problem with building the application, involving duplicate classes between logback-android and API3 2.0.2.82 - 2.0.2.94
Duplicate class org.slf4j.impl.StaticLoggerBinder
Duplicate class org.slf4j.impl.StaticMDCBinder
Duplicate class org.slf4j.impl.StaticMarkerBinder

Excluding dependency from your aar doesn't seem to be possible, and I can't exclude them app wide because the actual logging library needs them.

I have tried to incrementally update from 2.0.1.29 to 2.0.2.94 and the problem starts to occur at 2.0.2.82, and version 2.0.1.44 below it seems fine.

This is just one example of the problem.
Further testing versions 2.0.2.82+ they have a lot if not all their dependencies baked into the aar. Including ubiquitous dependencies like apache commons and slf4j, which cannot be used in the users application because it already exists within API3.

Submitted by James Swinton … on August 15, 2022 Permalink

Hi,

We'd recommend raising a support ticket in this instance. I spoke to some team members internally & its likely due to the additional reader support we added in the latest versions of our SDK. In order to make the changes required here we'd need to follow the support process & escalate things that way.

Thanks for your feedback.