Can't import this SDK and new PayPal SDK simultaneously

[MatyasKriz]

Braintree SDK Version

6.39.0

Environment

Both

Xcode Version

Xcode 16.4

OS Version & Device

irrelevant

Integration type

Swfit Package Manager

Development Processor

Apple Silicon (M-series chips)

Describe the bug

Hello, we've already got PayPal integrated through https://github.com/paypal/paypal-ios and want to add Braintree to the mix for card payments.

However, I can't add Braintree into the project because it uses a conflicting target name "PPRiskMagnes". Could it perhaps be renamed to something unique instead?

To reproduce

1. Add https://github.com/paypal/paypal-ios and https://github.com/braintree/braintree_ios through SPM to any project.
2. Get "multiple packages ('braintree_ios', 'paypal-ios') declare targets with a conflicting name: 'PPRiskMagnes’; target names need to be unique across the package graph" error.

Expected behavior

SDKs can be used alongside each other.

Screenshots

[MatyasKriz]

I found a bug/feature request in SPM repository, so unfortunately it's a SPM limitation, but nevertheless these two packages should be usable side by side.

swiftlang/swift-package-manager#8482

[jaxdesmarais]

Hello @MatyasKriz -

You are correct that this is a SPM limitation and not a limitation of our SDKs. I agree they should resolve the dependencies automagically as all other package managers do, but unfortunately this is outside of the SDKs control.

[MatyasKriz]

Making the Magnes library available through SPM would work as well while preserving backwards compatibility, I think. Could you please look into working around this limitation? I understand that it's more of a decision issue rather than implementation issue, since making it available through SPM is straightforward for closed-source XCFrameworks.

[jaxdesmarais]

Hey @MatyasKriz -

The Magnes library is not owned by our team, unfortunately, else we would make this fix as it is currently an issue with both Magnes and Cardinal Commerce not distributing their packages publicly via any of the officially supported package managers. Since we do not own that product we cannot make it available as that decision would have to come from the team that owns the product. I've passed this feedback on to that team as we have had several merchants bring this up over the years. We will keep this thread updated should they decide to move forward with a solution to distribute their packages via package managers.