You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had the same issue with you when install SwiftyStoreKit with CocoaPods, I cannot install 0.16.2 and later versions, only 0.16.1
But I found a solution, if you uninstall SwiftyStoreKit from CocoaPods and then install it again using Swift Package Manager you can install the last version 0.16.4
I had the same issue with you when install SwiftyStoreKit with CocoaPods, I cannot install 0.16.2 and later versions, only 0.16.1 But I found a solution, if you uninstall SwiftyStoreKit from CocoaPods and then install it again using Swift Package Manager you can install the last version 0.16.4
CocoaPods is mainly used in the project. Can Swift Package Manager and CocoaPods be used at the same time,And I encountered a problem, when evoking the Apple Pay page, the evoking failed, the configuration of things are no problem, have you ever encountered
Yes you can use Swift Package Manager and CocoaPods for dependencies at the same time.
I have some dependencies with CocoaPods because these pods have not yet a Swift Package Manager version so I got to keep them in CocoaPods and I have my other dependencies added in Swift Package Manager so I use both and I have no problem. Just to be sure I haven't the same dependency in both, you should remove it from CocoaPods before add it in Swift Package Manager.
For your Apple Pay issue, I don't know about it, we don't use it in our app. I didn't know SwiftyStoreKit handle Apple Pay too
Bug Report
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Platform Information
Additional context
Add any other context about the problem here.
Potentially Related Issues
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: