-
Notifications
You must be signed in to change notification settings - Fork 993
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undeclared 'STPSourceTypeBitcoin:' #1006
Comments
Hi @jzhw0130 , We removed bitcoin support in v13.0.0. There are some more details in the Migrating guide: https://github.com/stripe/stripe-ios/blob/master/MIGRATING.md Thanks, |
No No . @danj-stripe It is not a migrate issue. The error exists inside the library, not my application code. |
@jzhw0130, thanks for getting back in touch. We don't have a file called I think you might be looking at code from a different repository: tipsi/tipsi-stripe. I was able to find some code there that matches what I think you're looking at: https://github.com/tipsi/tipsi-stripe/blob/master/ios/TPSStripe/TPSStripeManager.m#L258-L260. If that's the case, then unfortunately we won't be able to help out much, since we don't have any control over that repository (it's written by someone outside of Stripe). I would suggest opening an issue there and seeing if a developer who works on that project will take a look. -James |
oh oh, sorry for my mistake. @jil-stripe I found the ReactNative library (tipsi/tipsi-stripe) on https://stripe.com/docs/libraries#mobile. The RN library links you guys native library, the error exists on on the RN layer, not your library, I will open a issue there. Thanks for you guys help. Zhiwei |
* Add signup flow UI tests * Refactor virtual keyboard text entry * Add signin test * Add comment
Summary
Use of undeclared identifier 'STPSourceTypeBitcoin'; did you mean 'STPSourceTypeUnknown'?
Code to reproduce
Just build
iOS version
9.0+
Installation method
Cocaspod
SDK version
target 'Milo' do
pod 'Stripe', '~> 13.1.0'
inherit! :search_paths
end
The text was updated successfully, but these errors were encountered: