Tuesday 14 February 2012

iPhone SDK: Connect to Twitter with OAuth


This tutorial will show you how to quickly integrate the Twitter API with the iPhone SDK using Twitter-OAuth-iPhone, a plug-and-play Twitter library for the iPhone composed of multiple open-source projects combined and synthesized for ease of implementation by Ben Gottlieb.
NOTE: With the release of iOS 5, this article is now outdated. Moving forward, you should seriously consider using the Twitter Framework that ships with the iOS 5 SDK. Only consider implementing the solution demonstrated here if you must support users on older versions of iOS. A tutorial demonstrating the use of the Twitter Framework will be released on Mobiletuts+ in the coming weeks.

Project Setup

This tutorial will use a simple application called “TwitterRush” to demonstrate Twitter OAuth integration for the iPhone. By downloading the TwitterRush application, you will be able to precisely follow all steps in this tutorial. However, if you already have an iPhone project that you would like to connect with the Twitter API, you should still be able to follow along in your own code with only slight modifications.
In addition to TwitterRush or your own project, you will also need to download Ben Gottlieb’s Twitter-OAuth-iPhone project available on GitHub.

Step 1: Copy the Twitter+OAuth Folder

After downloading and unarchiving the Twitter-OAuth-iPhone library, drag the folder entitled “Twitter+OAuth” into the “Other Sources” folder in the Xcode 4 navigator area. Be sure to check the “Copy items into destination group’s folder (if needed)” option and click “Finish.”
Twitter API Guide 1
Trying to compile and run your application now will result in A LOT of errors (90 at the time of this writing with iOS SDK 4). Not to worry: we will easily fix all of them in Step 2.

Step 2: Add the libxml2 Library

In the navigator area of Xcode 4, select the project name (in this case “TwitterRush”). Next, select the current target (“TwitterRush” here again), and then select the “Build Phases” tab. Expand the “Link Binary With Libraries” option, and then click the “+” button to add a new framework. Type “libxml2″ into the search box, and select the libxml2.dylib library that appears in the list. Click “Add” to include this library in the linking phase of your project.
After completing these steps, your screen should look something like this:
Adding the libxml2 library to an Xcode 4 project
After adding the library to your project, you will need to modify the “header search paths” setting in your project’s build settings. To do this, deselect the target and select the actual TwitterRush Project. Open the “Build Settings” tab and search for the “Header Search Paths” entry. Double click this setting and then click the “+” button in the bottom left of the pop-up dialogue to add a new search path. Click the “recursive” check box, double click the “Path” field, and enter the following dynamic path:
  1. $(SDKROOT)/usr/include/libxml2  
After clicking “Done”, your screen should look similar to this:
Twitter API Guide 4
If you run the application from the Xcode menubar, you should now be able to build the application without any compile errors!

Step 3: Declare the NSXMLParserDelegate Protocol

While you are now able to compile and run the application without any errors, there are a number of warnings related to changes in the iOS4 SDK and the NSXMLParserDelegate protocol. You will need to explicitly declare that MGTwitterStatusesParser.h and MGTwitterXMLParser.h conform to this protocol in order to prevent these warnings from occurring.
To do so, open the MGTwitterStatusesParser.h file and modify the @interface declaration by declaring the NSXMLParserDelegate protocol like so:
  1. @interface MGTwitterStatusesParser : MGTwitterXMLParser <NSXMLParserDelegate> {  
Now do the same for MGTwitterXMLParser.h, modifying the @interface declaration to read:
  1. @interface MGTwitterXMLParser : NSObject <NSXMLParserDelegate> {  
You should now be able to smoothly compile the application without generating any errors or warnings! We’re now ready to begin integrating the Twitter-OAuth-iPhone library with our code.

Step 4: Import SA_OAuthTwitterController.h & Declare SA_OAuthTwitterEngine

We now need to begin importing the library classes that we will use to connect with the Twitter API. OpenTwitterRushViewController.h and modify the code to read as follows:
  1. #import <UIKit/UIKit.h>  
  2. #import "SA_OAuthTwitterController.h"  
  3.   
  4. @class SA_OAuthTwitterEngine;  
  5.   
  6. @interface TwitterRushViewController : UIViewController <UITextFieldDelegate, SA_OAuthTwitterControllerDelegate>  
  7. {  
  8.     IBOutlet UITextField     *tweetTextField;  
  9.   
  10.     SA_OAuthTwitterEngine    *_engine;  
  11. }  
  12.   
  13. @property(nonatomic, retain) IBOutlet UITextField *tweetTextField;  
  14.   
  15. -(IBAction)updateTwitter:(id)sender;   
  16.   
  17. @end  
On line 2, we import the SA_OAuthTwitterController class for use within our view controller. On line 4, we forward declare the SA_OAuthTwitterEngine class so we can declare an instance of that class in the@interface without actually importing the header file. On line 6 we declare theSA_OAuthTwitterControllerDelegate protocol -this will allow us to easily respond to Twitter API events later. Finally, on line 10 we declare the _engine object as an instance of the SA_OAuthTwitterEngineclass.
Now switch to the TwitterRushViewController.m file. Import the SA_OAuthTwitterEngine class that we just forward declared in the class interface:
  1. #import "SA_OAuthTwitterEngine.h"  
Because the SA_OAuthTwitterControllerDelegate only contains optional method declarations, at this point you should again be able to compile and run your application without any errors or warnings.

Step 5: Define Your Twitter API OAuth Credentials

In order to gain OAuth access to the Twitter API, you will need to first create a Consumer Key and a Secret Key for Twitter to be able to identify and authenticate your application. You can do this from the Twitter web site by logging into your account and navigating to the app registration form. When going through the registration process, be sure to specify “client” as the application type, check the “Yes, use Twitter for login” box, and select “Read & Write” as the default access type to enable your iPhone app to post tweets on behalf of your users.
After you have registered your application and Twitter has generated your application credentials, add the following to TwitterRushViewController.m above the class @implementation:
  1. #define kOAuthConsumerKey        @"Your consumer key here"         //REPLACE With Twitter App OAuth Key  
  2. #define kOAuthConsumerSecret    @"Your consumer secret here"     //REPLACE With Twitter App OAuth Secret  
We will use these constants momentarily when we instantiate our _engine object.

Step 6: Launch the Twitter Login Screen

For our use-case, we want to initialize the _engine object when our ViewController is created and then display the Twitter OAuth login screen as soon as the view controller finishes loading. To initialize the_engine object, modify the viewDidAppear method to read as follows:
  1. - (void)viewDidAppear: (BOOL)animated {  
  2.   
  3.     if(!_engine){  
  4.         _engine = [[SA_OAuthTwitterEngine alloc] initOAuthWithDelegate:self];  
  5.         _engine.consumerKey    = kOAuthConsumerKey;  
  6.         _engine.consumerSecret = kOAuthConsumerSecret;  
  7.     }  
  8.   
  9. }  
Now go ahead and release the _engine object in our view controller’s dealloc method:
  1. - (void)dealloc {  
  2.     [_engine release];  
  3.     [tweetTextField release];  
  4.     [super dealloc];  
  5. }  
After our view finishes loading, we want to immediately launch the Twitter login screen. To do so, you will need to again modify the viewDidAppear method like so:
  1. - (void)viewDidAppear: (BOOL)animated {  
  2.   
  3.     if(!_engine){  
  4.         _engine = [[SA_OAuthTwitterEngine alloc] initOAuthWithDelegate:self];  
  5.         _engine.consumerKey    = kOAuthConsumerKey;  
  6.         _engine.consumerSecret = kOAuthConsumerSecret;  
  7.     }  
  8.   
  9.     UIViewController *controller = [SA_OAuthTwitterController controllerToEnterCredentialsWithTwitterEngine:_engine delegate:self];  
  10.   
  11.     if (controller){  
  12.         [self presentModalViewController: controller animated: YES];  
  13.     }  
  14.   
  15. }  
If you run the application now, you’ll see that we are successfully presenting the Twitter login screen whenever our custom view is displayed. However, there is one major problem with this setup: the login screen will always be displayed when the view appears, even if the user has already logged in. We need to add a conditional that will only display this control if the user has not yet been connected via OAuth.
To do this, add the following conditional before displaying the view:
  1. if(![_engine isAuthorized]){  
  2.     UIViewController *controller = [SA_OAuthTwitterController controllerToEnterCredentialsWithTwitterEngine:_engine delegate:self];  
  3.   
  4.     if (controller){  
  5.         [self presentModalViewController: controller animated: YES];  
  6.     }  
  7. }  
The isAuthorized method will return a boolean value of TRUE if we have an OAuth authentication token. So, this conditional simply tests whether we do not have authorization, and then displays the Twitter login when needed.
For the isAuthorized method to work, we also need to add the followingSA_OAuthTwitterEngineDelegate protocol methods responsible for storing our OAuth authentication token after the first login:
  1. //=============================================================================================================================  
  2. #pragma mark SA_OAuthTwitterEngineDelegate  
  3. - (void) storeCachedTwitterOAuthData: (NSString *) data forUsername: (NSString *) username {  
  4.     NSUserDefaults          *defaults = [NSUserDefaults standardUserDefaults];  
  5.   
  6.     [defaults setObject: data forKey: @"authData"];  
  7.     [defaults synchronize];  
  8. }  
  9.   
  10. - (NSString *) cachedTwitterOAuthDataForUsername: (NSString *) username {  
  11.     return [[NSUserDefaults standardUserDefaults] objectForKey: @"authData"];  
  12. }  

Step 7: Post Updates to Twitter

In what is perhaps the simplest step of the entire process, add the following single line of code toupdateTwitter, our custom IBAction method, to actually post an update to Twitter:
  1. [_engine sendUpdate:tweetTextField.text];  
Voila! You should now be posting updates to your Twitter feed. However, we aren’t quite finished yet. What happens if our application fails to post the update? What if we wanted to present a confirmation view if the tweet is posted successfully? Thankfully, the TwitterEngineDelegate protocol has two methods defined for just this purpose.
Add the following code to TwitterRushViewController.m:
  1. //=============================================================================================================================  
  2. #pragma mark TwitterEngineDelegate  
  3. - (void) requestSucceeded: (NSString *) requestIdentifier {  
  4.     NSLog(@"Request %@ succeeded", requestIdentifier);  
  5. }  
  6.   
  7. - (void) requestFailed: (NSString *) requestIdentifier withError: (NSError *) error {  
  8.     NSLog(@"Request %@ failed with error: %@", requestIdentifier, error);  
  9. }  
You can see that the application will now log success and failure messages to the console depending on what happens after we click the “Tweet” button. This behavior can be easily modified to match the needs of your own apps.

Conclusion

If you have followed the step-by-step instructions above, you should now be able to post status updates to Twitter on behalf of your users!
The full TwitterRushViewController.h file should now look like this:
  1. #import <UIKit/UIKit.h>  
  2. #import "SA_OAuthTwitterController.h"  
  3.   
  4. @class SA_OAuthTwitterEngine;  
  5.   
  6. @interface TwitterRushViewController : UIViewController <UITextFieldDelegate, SA_OAuthTwitterControllerDelegate>  
  7. {   
  8.   
  9.     IBOutlet UITextField *tweetTextField;  
  10.   
  11.     SA_OAuthTwitterEngine *_engine;   
  12.   
  13. }  
  14.   
  15. @property(nonatomic, retain) IBOutlet UITextField *tweetTextField;  
  16.   
  17. -(IBAction)updateTwitter:(id)sender;   
  18.   
  19. @end  
The full TwitterRushViewController.m file should read:
  1. #import "TwitterRushViewController.h"  
  2. #import "SA_OAuthTwitterEngine.h"  
  3.   
  4. /* Define the constants below with the Twitter 
  5.    Key and Secret for your application. Create 
  6.    Twitter OAuth credentials by registering your 
  7.    application as an OAuth Client here: http://twitter.com/apps/new 
  8.  */  
  9.   
  10. #define kOAuthConsumerKey               @"Your Key Here"        //REPLACE With Twitter App OAuth Key  
  11. #define kOAuthConsumerSecret            @"Your Secret Here"    //REPLACE With Twitter App OAuth Secret  
  12.   
  13. @implementation TwitterRushViewController  
  14.   
  15. @synthesize tweetTextField;   
  16.   
  17. #pragma mark Custom Methods  
  18.   
  19. -(IBAction)updateTwitter:(id)sender  
  20. {  
  21.     //Dismiss Keyboard  
  22.     [tweetTextField resignFirstResponder];  
  23.   
  24.     //Twitter Integration Code Goes Here  
  25.     [_engine sendUpdate:tweetTextField.text];  
  26. }  
  27.   
  28. #pragma mark ViewController Lifecycle  
  29.   
  30. - (void)viewDidAppear: (BOOL)animated {  
  31.   
  32.     // Twitter Initialization / Login Code Goes Here  
  33.     if(!_engine){  
  34.         _engine = [[SA_OAuthTwitterEngine alloc] initOAuthWithDelegate:self];  
  35.         _engine.consumerKey    = kOAuthConsumerKey;  
  36.         _engine.consumerSecret = kOAuthConsumerSecret;  
  37.     }  
  38.   
  39.     if(![_engine isAuthorized]){  
  40.         UIViewController *controller = [SA_OAuthTwitterController controllerToEnterCredentialsWithTwitterEngine:_engine delegate:self];  
  41.   
  42.         if (controller){  
  43.             [self presentModalViewController: controller animated: YES];  
  44.         }  
  45.     }     
  46.   
  47. }  
  48.   
  49. - (void)viewDidUnload {  
  50.     [tweetTextField release];  
  51.     tweetTextField = nil;  
  52. }  
  53.   
  54. - (void)didReceiveMemoryWarning {  
  55.     [super didReceiveMemoryWarning];  
  56. }  
  57.   
  58. - (void)dealloc {  
  59.     [_engine release];  
  60.     [tweetTextField release];  
  61.     [super dealloc];  
  62. }  
  63.   
  64. //=============================================================================================================================  
  65. #pragma mark SA_OAuthTwitterEngineDelegate  
  66. - (void) storeCachedTwitterOAuthData: (NSString *) data forUsername: (NSString *) username {  
  67.     NSUserDefaults          *defaults = [NSUserDefaults standardUserDefaults];  
  68.   
  69.     [defaults setObject: data forKey: @"authData"];  
  70.     [defaults synchronize];  
  71. }  
  72.   
  73. - (NSString *) cachedTwitterOAuthDataForUsername: (NSString *) username {  
  74.     return [[NSUserDefaults standardUserDefaults] objectForKey: @"authData"];  
  75. }  
  76.   
  77. //=============================================================================================================================  
  78. #pragma mark TwitterEngineDelegate  
  79. - (void) requestSucceeded: (NSString *) requestIdentifier {  
  80.     NSLog(@"Request %@ succeeded", requestIdentifier);  
  81. }  
  82.   
  83. - (void) requestFailed: (NSString *) requestIdentifier withError: (NSError *) error {  
  84.     NSLog(@"Request %@ failed with error: %@", requestIdentifier, error);  
  85. }  
  86. @end  
Thanks for reading this tutorial on the Twitter-OAuth-iPhone library, and a very special thanks to Ben Gottlieb, Matt Gemmell, Jon Crosby, Chris Kimpton, and Isaiah Carew. Without their hard work, implementing the Twitter API with the iPhone SDK would take many, many more steps to achieve.
Have questions or comments on this tutorial? Leave them in the comments section below or message@markhammonds directly on twitter. Bonus points for completing this tutorial and using the TwitterRush application to send me a shout out!

1 comments:

 

Copyright @ 2013 PakTechClub.