Stripe-ios: Stripe pod does not compile on Xcode 11.4

[stephengilroy-grx]

Summary

After just recently updating to the new Xcode 11.4 I am unable to build my project withe Stripe SDK pod. Compiler error given is:
Incompatible block pointer types sending '__strong STPAPIResponseBlock _Nonnull' (aka 'void (^__strong)(ResponseType _Nullable __strong, NSHTTPURLResponse * _Nullable __strong, NSError * _Nullable __strong)') to parameter of type 'void (^ _Nonnull)(STPSource * _Nullable __strong, NSHTTPURLResponse * _Nullable __strong, NSError * _Nullable __strong)'

Code to reproduce

I was able to repro with a newly created empty project. Just run pod init add the latest stripe pod and try to build.

iOS version

13.4

Installation method

Cocoapods

SDK version

19.0.0 (also observed this behavior on 18.x versions)

Other information

I've tried everything imaginable: nuking pods, restarting my computer, deleting derived data, etc. As soon as I downgrade to 11.3.1 I am able to successfully build again.

From the error response above it seems this might be related to ObjC generics?

[bryanbartow]

Looks like this might be fixed in #1524

[stephengilroy-grx]

https://github.com/stripe/stripe-ios/pull/1526 was just merged in so I believe this should be resolved soon 🤞

[yuki-stripe]

Thanks for the report, we're working on releasing a new version that fixes this now.

[csabol-stripe]

We've just published a release with this fix https://github.com/stripe/stripe-ios/releases/tag/v19.0.1
It should also be live on cocoapods

[prgorasiya]

My app still supports iOS 9.
Therefore I have to use V17.0.2 and thats throwing issues with Xcode 11.4
Any way to fix this?

[mhergon]

My app still supports iOS 9.
Therefore I have to use V17.0.2 and thats throwing issues with Xcode 11.4
Any way to fix this?

Same here!

[mikedizon]

Issued a PR for v14.0.0/v14.0.1

https://github.com/stripe/stripe-ios/pull/1534

[davidme-stripe]

We've released v14.0.1, v15.0.2, v17.0.3, and v19.0.1 to Cocoapods with fixes for this issue.

We think this should cover all current versions without additional migration work. Please let us know if you're unable to update to one of these versions.