The 'Pods-PromoSuite' target has frameworks with conflicting names: ppriskmagnes.xcframework".

[govind-ksolves]

Is your feature request related to a problem? Please describe.

While integrating the Braintree SDK into our project, we encountered the following error:" The 'Pods-PromoSuite' target has frameworks with conflicting names: ppriskmagnes.xcframework".
Our project already includes the iZettleSDK pod, which also depends on ppriskmagnes.xcframework. Since both Braintree and iZettleSDK include this framework, it’s causing a conflict during installation.
Could you please guide us on how to resolve this conflict or suggest an alternative way to include both Braintree and iZettleSDK in the same project?

Describe the solution you'd like.

Need to integrate both the SDK

[jaxdesmarais]

Hello @govind-ksolves -

Thanks for reaching out regarding this issue. This is ultimately due to the Magnes library being a closed source binary and shipped with specific module of the Braintree SDK that requires the Data Collector. Since the binary is packaged with the SDK the package managers are not able to automatically resolve the conflict between the Braintree SDK and the iZettle SDK.

Currently the modules that require Magnes are PayPal and Local Payments. Are you currently attempting to implement one or both of those payment methods? If not, you can simply import the individual modules you require such as pod 'Braintree/Card' vs pod 'Braintree' which by default includes PayPal/Magnes.

We will reach out internally to our partners at Magnes to see if there has been any movement on distributing their SDK as a publicly available closed-source binary, which would resolve this issue.

[govind-ksolves]

Hello @jaxdesmarais

I’m following up regarding the previous discussion on the Magnes SDK being a closed-source binary and its conflict resolution with the Braintree and iZettle SDKs. In your last response, you mentioned reaching out internally to your partners at Magnes to explore the possibility of distributing their SDK as a publicly available closed-source binary.

Could you please confirm if there have been any updates or progress on this front? This information will help us plan our integration strategy accordingly.
Thanks In Advance

[jaxdesmarais]

Hey @govind-ksolves -

We had an initial kickoff meeting with the Magnes SDK team and they are exploring the feasibility. It will require several approvals as well as investigation on their end to ensure that things are exposed properly without leaking internal details of our fraud protection tools. That to say that this would likely be a more long term solution if it's feasible from their side. We do not currently have a timeline from their team yet but I can provide one if they determine they can move forward with a solution to distribute their closed source binary publicly.