-
Notifications
You must be signed in to change notification settings - Fork 343
AFNetworking 2.2.x compatibility #79
Comments
+1 here Chris -- cheers on kickflip. |
Thanks! :) |
👍 |
@mattt is this something you are open to someone else updating, or is this an abandoned project? |
Would love an update on this issue. @mattt, any thoughts on this? |
@mattt Is this abandoned? |
+1 @mattt I use [email protected]:mlwelles/AFOAuth2Client.git as a workaround, but would love to be able to use the official and not have warnings and outdated versions in my podfile etc. |
Perhaps someone else is up for the job of becoming the new owner of this project? I've only used it in one project so far so don't think I would be a great help... @conradev ? |
@samskiter We still don't know if this is abandoned. @mattt is very active on github, nshipster, etc. Let's hope he responds to this thread. |
@nunofgs I think it might be safe to say this project is dead enough for someone to take some control and try and make some progress (presuming there is such a person who's prepared to take the task on - any volunteers? I'm probably not versed enough on AFNetworking 2.x to really contribute). I've experienced almost complete radio silence on issues/PR here since Dec 2013. |
@matt 👍 |
Hi everyone! I'm the creator/maintainer of the AFNetworking 2.0-compatible replacement for AFOAuth1Client, BDBOAuth1Manager. A new project I've started working on requires the use of OAuth 2.0, so I just wanted to gauge the community's interest in me creating an OAuth 2.0 version of BDBOAuth1Manager. Since I'm not familiar with the spec the way I am with OAuth 1.0a, it will take me a bit of time to get something working. If there's enough interest, I'm more than happy to throw it up here! |
The solution to updating I have a fork of I have neglected to help maintain this project, but I am still one of the maintainers. I would love pull requests to my fork, and if it reaches a certain threshold, I can eventually move it to a branch here. Thoughts? |
AFOAuth2Client has been deprecated in favor or AFOAuth2Manager, which is AFNetworking 2-compatible, integrating work from @conradev's branch. pod 'AFNetworking', '~>2.5'
pod 'AFOAuth2Manager', '~>2.0' For anyone still on AFNetworking 1.x, a new release of AFOAuth2Client, 1.0.0, has been pushed to CocoaPods. pod 'AFNetworking', '~>1.3'
pod 'AFOAuth2Client', '~>1.0' # Deprecated |
@mattt Awesome! Thank you!! |
thanks @mattt |
I realize there are multiple issues open for AFNetworking 2.0 compatibility but it seems that there isn't much activity or interest in merging those patches. Is there any specific reason that these patches aren't acceptable?
I am developing a library/podspec that depends on both AFNetworking and AFOAuth2Client and I am worried that end users of the library may experience AFNetworking version conflicts. As far as I know, it isn't possible for me to point to an "unofficial" version of AFOAuth2Client in my podspec, so for now I guess I am limited to AFNetworking 1.3.x until the official podspec is updated as well.
The text was updated successfully, but these errors were encountered: