Error on pod install after the release of Braintree version 6.8.0 about braintree_ios HOT 5 CLOSED

Hello @mlazari -

Thanks for reaching back out with those details. This does seem specific to the Cocoapods CDN as the following Podfile downloads the dependencies as expected for multiple versions of our SDK. I was just able to test this with multiple versions successfully in a local Cocoapods project:

platform :ios, '15.0'

target 'bt-ios-cocoapods-testing-demo' do
  pod 'Braintree', '6.8.0' // can replace with any version
end

from braintree_ios.

I just found the same issue being reported here: CocoaPods/CocoaPods#12115 for a different dependency, so indeed doesn't seem related to Braintree. Thanks for looking into it.

from braintree_ios.

Hello @mlazari -

The SDK react-native-braintree-dropin-ui was not developed by Braintree. I would recommend reaching out to the developers of that SDK directly for further assistance on this error. That said there are also several issues related to this opened on the Cocoapods repository - I expect this issue ultimately lies with the Cocoapods CDN which our SDK does not own.

from braintree_ios.

@jaxdesmarais The same thing is happening in a non React Native project that uses this pod directly:

# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

source 'https://cdn.cocoapods.org/'

target 'BraintreeTest' do
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!

  # Pods for BraintreeTest

  pod 'Braintree', '6.8.0'

end

Even if an older version is requested, like pod 'Braintree', '5.20.1', the error is still triggered.

I opened this because I thought it might be related to the release of Braintree 6.8.0, like an error during its publication, making it be in a bad state or something. But I understand it might be related just to a issue with Cocoapods CDN and not with the publication process of this version.

In any case it doesn't seem to be related to react-native-braintree-dropin-ui, that was just a way to reproduce the error, since the project in which I encountered this error is a React Native one.

from braintree_ios.

@jaxdesmarais Got it, thank you!

from braintree_ios.