Skip to main content
Salesforce

Return to Answer

Updated answer to note the SDK has been updated to fix this behavior.
Source Link
edit approved Jan 30, 2018 at 19:42
Bill Mote
edit approved Jan 30, 2018 at 19:42
Bill Mote
  • 5.4k
  • 1
  • 11
  • 16

As it currently stands there isn't much, if anything, you can do here. The Marketing Cloud SDK compiles the tozny library into the distributed aar rather than declaring it in the pom file distributed. This is done because there are certain modifications made to the code required by the SDK. Because of this, adding an exclude dependency declaration to your build.gradle file will not have the desired effect.

I'll open a ticket to get this addressed in the SDK.

UPDATE 20180130 -- The latest release, v5.4.2, contains a fix for this issue.

As it currently stands there isn't much, if anything, you can do here. The Marketing Cloud SDK compiles the tozny library into the distributed aar rather than declaring it in the pom file distributed. This is done because there are certain modifications made to the code required by the SDK. Because of this, adding an exclude dependency declaration to your build.gradle file will not have the desired effect.

I'll open a ticket to get this addressed in the SDK.

As it currently stands there isn't much, if anything, you can do here. The Marketing Cloud SDK compiles the tozny library into the distributed aar rather than declaring it in the pom file distributed. This is done because there are certain modifications made to the code required by the SDK. Because of this, adding an exclude dependency declaration to your build.gradle file will not have the desired effect.

I'll open a ticket to get this addressed in the SDK.

UPDATE 20180130 -- The latest release, v5.4.2, contains a fix for this issue.

Source Link
Seth
Seth
  • 951
  • 4
  • 5

As it currently stands there isn't much, if anything, you can do here. The Marketing Cloud SDK compiles the tozny library into the distributed aar rather than declaring it in the pom file distributed. This is done because there are certain modifications made to the code required by the SDK. Because of this, adding an exclude dependency declaration to your build.gradle file will not have the desired effect.

I'll open a ticket to get this addressed in the SDK.