From 4eb9d2e372e03848cd1f7bff8f6112e30fe4e9d2 Mon Sep 17 00:00:00 2001 From: Mattt Thompson Date: Mon, 21 Jan 2013 12:33:38 -0800 Subject: [PATCH] Updating README --- README.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/README.md b/README.md index 20c7abc..94a5542 100644 --- a/README.md +++ b/README.md @@ -1,12 +1,7 @@ # AFOAuth1Client -> _This is still in early stages of development, so proceed with caution when using this in a production application. -> Any bug reports, feature requests, or general feedback at this point would be greatly appreciated._ - ## Instructions -Add all of the included files into an iOS project with AFNetworking. `AFHTTPClient` should replace the existing copy in your current AFNetworking installation. - Register your application to [launch from a custom URL scheme](http://iphonedevelopertips.com/cocoa/launching-your-own-application-via-a-custom-url-scheme.html), and use that with the path `/success` as your callback URL. Here's how it all looks together: @@ -17,7 +12,6 @@ AFOAuth1Client *twitterClient = [[[AFOAuth1Client alloc] initWithBaseURL:[NSURL // Your application will be sent to the background until the user authenticates, and then the app will be brought back using the callback URL [twitterClient authorizeUsingOAuthWithRequestTokenPath:@"/request_token" userAuthorizationPath:@"/authorize" callbackURL:[NSURL URLWithString:@"x-com-YOUR-APP-SCHEME://success"] accessTokenPath:@"/access_token" success:^(AFOAuth1Token *accessToken) { NSLog(@"Success: %@", accessToken); - NSLog(@"Your OAuth credentials are now set in the `Authorization` HTTP header"); } failure:^(NSError *error) { NSLog(@"Error: %@", error); }];