-
Notifications
You must be signed in to change notification settings - Fork 281
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
Swift 3.0 - No such module #137
Comments
Ah CocoaPods. I need to update the podfile and define |
Okey thank you :-) Please, keep me in touch in this issues when it's done ! |
I have not yet pushed version 3.0 since CocoaPods seems to want to use Swift 2.3 for whatever reason, but I've updated the podspec on the develop branch. Can you try again? |
Same issue here |
Just pushed an updated podspec, can you try again? |
@p2, thanks you, that error is fixed. Current state: .../Pods/p2.OAuth2/Sources/Base/OAuth2KeychainAccount.swift:58:11: Use of undeclared type 'KeychainGenericPasswordType' |
Same error, look to be an error with SwiftKeychain library ! |
The sources for the keychain classes are in the submodule, the |
That submodule project uses Swift2. Maybe it will be better to fork it or copy to OAuth2. |
It is forked and now on Swift 3. All works well in Xcode, not sure what CocoaPods is doing. I've changed sourcefile order in the podspec, does that help? |
I tried again and same problem :/ |
I've add
Maybe it helps to find solution |
Yes, I have the same problem, even after |
Alright, I also changed the submodule on
Maybe clean the cache first:
|
Thank you. I didn't understand what you did, but it works :D |
It's ok now ! :D Thank you. |
🙂 As you saw, the original Thanks for testing to the both of you! I'll keep this open for others to see. |
Has the v3 pod spec been taken down? I'm sure I had it building through Cocoapods with version 3 of your library but running a
Not too much of an issue as I can point to your repo to pull the code, but I could have sworn I pulled down version 3.0 yesterday through Cocoapods! |
No, I'm unable to post
|
@p2 Maybe you should, at least for now, update the readme with this instructions? Currently when a new user tries installing it, it fails and needs to search to maybe find this issue. |
You can fork https://github.com/CocoaPods/Specs and update manually, I'm doing this for PromiseKit since this has been going on for a while now. |
Thanks, I probably should. What a piece of crap. |
You have to ping a maintainer to get them to merge it. |
May I suggest moving this to an issue with a more clear title? I arrived here via google and didn't know why it was pointing me here :) but this did solve my problem at least!
the Swift 3.0 transition has been...rocky....to say the least it seems for everyone. |
The solution for Swift 3.0 is in the README file :-) |
@liltimtim what have you been searching for, OAuth2 and CocoaPods? Maybe I can adapt the title. Installation via CocoaPods is explained st the bottom of the readme; I don't think CocoaPods is a great system for Swift, since we can use frameworks in iOS it's overkill. |
@p2 Maybe Swift 3.0 - No such Module error? I was receiving similar error as the op. after implementing your solution it was fixed. |
The bug in CocoaPods has been addressed in CocoaPods pod 'p2.OAuth' '~> 3.0' |
Have updated my Podfile and all seems to be working, many thanks! |
Hi, I've tried through cocoa pods and get the same issue. Has this been tested for swift 4? I get the "no such module p2.OAuth2" error though when I go to project settings/build phases/ link binary.../ and press add, p2.OAuth 2 is in the linkable frameworks. Also, via cocoa pods, there are a lot of errors as functions and properties are internal and cannot be reached. Any help greatly appreciated |
This issue is closed, please open a new issue and provide more details if v 4.0.1 doesn't work for you via CocoaPods. |
Hello,
I'm trying to build my project with 3.0, but seems to be not possible at this time ?
I tried with :
pod 'p2.OAuth2', :git => 'https://github.com/p2/OAuth2', :branch => 'develop'
But got this :
Have you any solution ? :-)
The text was updated successfully, but these errors were encountered: