To make it easier to diagnose your issue, please fill out the following:
Summary
The examples don't work with iOS 11
Code to reproduce
pod update in terminal.
Also using PKAddressField anywhere in Swift code
iOS version
What version of iOS are you observing the problem on?
11
Installation method
How did you install our SDK?
pod install
SDK version
What version of our SDK are you using? You can find this by either looking at your Podfile.lock (if you're using Cocoapods), your Cartfile.resolved (if you're using Carthage), or by looking at the value of STPSDKVersion in STPAPIClient.h.
11.3
Other information
Anything else you can include that'll make it easier for us to help you!
massoud12345
All 17 comments
Sorry you're having trouble. Can you give us the specific error message you are seeing so we can try to help you fix the problem?
bdorfman-stripe
on 19 Oct 2017
massoud12345
on 19 Oct 2017
Hi, thank you for your help. Please see the screenshots above.
massoud12345
on 19 Oct 2017
Are you using cocoapods with or without frameworks enabled?
bdorfman-stripe
on 20 Oct 2017
I have not been able to replicate your exact errors locally when running cocoapods. Can you provide me your podfile and your minimum iOS version you are targetting with your app? A sample xcode project that replicates the issue would be even better. Thank you for your help and patience as we try to work out what is happening.
bdorfman-stripe
on 20 Oct 2017
Thank you for your quick reply.
I am using the following set up.
The deployment target is iOS 11.
platform :ios, '11.0'
use_frameworks!
target 'AppName' do
pod 'Alamofire', '~> 4.4'
pod 'Stripe'
end
massoud12345
on 20 Oct 2017
I have just created a brand new Xcode project targeting iOS 11.0 and used your Podfile as you pasted here, and I do not see the warnings or errors you have shown in your screenshot. Can you create an example project which replicates the issue and send it to me so I can investigate further? You can send it to [email protected]
Thank you!
bdorfman-stripe
on 20 Oct 2017
Will do.
Thank you for your help Brian.
massoud12345
on 20 Oct 2017
I'm having the exact same issues described by @massoud12345
cyrilzakka
on 24 Oct 2017
These errors/warnings are due to Apple having updated PassKit for iOS 11. http://codeworkshop.net/objc-diff/sdkdiffs/ios/11.0/PassKit.html
cyrilzakka
on 24 Oct 2017
The Stripe SDK supports iOS versions back to iOS8 so we cannot simply move over to the new iOS 11 only methods. Locally the projects appear to build without deprecation warnings since the StripeSDK.framework has a minimum version of 8? I also do not see any ARC implicit conversion error at all like is shown in the screenshot. Same as I said before, if you have a project which replicates the error please email to me so that we can investigate.
Thanks,
Brian
bdorfman-stripe
on 24 Oct 2017
Just going to ignore them for now as they鈥檙e not really stopping development - I just hate having warnings.
I think just inserting
if #available(iOS 11.0, *) {
// use the feature only available in iOS 11
} else {
// or use some work around
}
should take care of the warnings
cyrilzakka
on 24 Oct 2017
We'll investigate adding some availability guards or superfluous warning suppression for our next release, sorry about that!
bdorfman-stripe
on 24 Oct 2017
I鈥檓 sorry if that came off as mean, I was just trying to help. Really grateful for this library and everything you guys have done!
cyrilzakka
on 24 Oct 2017
It's cool, I didn't take it as mean :) I know how annoying it is to have warnings pulled into your project by a third party that you can't do anything about. I'll try to get this all sorted out ASAP!
bdorfman-stripe
on 24 Oct 2017
Update on this issue: The warnings are silenced in https://github.com/stripe/stripe-ios/pull/823 which will be included in our next release (all cases are actually properly guarded against, just not with the new @available language feature that Xcode 9 looks for).
Additionally, the compilation errors in the original post appear to be from user alterations made to the example project and not a bug in this repo or the sdk code itself.
If anyone else runs into issues on Xcode 9 or iOS 11 please open a new Github issue and we'll try to get it sorted out as soon as possible.
Thanks,
Brian
bdorfman-stripe
on 2 Nov 2017
@bdorfman-stripe The warning still persists when using Carthage. I have the latest version of Stripe SDK: 11.5.0.
flexaddicted
on 21 Nov 2017
Related issues
billinghamj
路
6Comments
provTheodoreNewell
路
5Comments
mansoorshahsaid
路
4Comments
paynd
路
3Comments
aurelhubert
路
6Comments
Most helpful comment
It's cool, I didn't take it as mean :) I know how annoying it is to have warnings pulled into your project by a third party that you can't do anything about. I'll try to get this all sorted out ASAP!