Skip to main content

Using RestAPI calls with MGTwitterEngine+Oauth



I am using MGTwitterEngine+Oauth for twitter integration in iPhone. I need to post status and status with media on twitter.When searching I came to know that it can be possible with REST API. https://dev.twitter.com/docs/api





But I did not find any links which can help how to use this api after I get authenticated with twitter. So what I did I tried using Oauth but it requires manually entering the pin which is not accepted in my case. So what I did it. I fetch information from mgtwitter engine methods:-







- (void) OAuthTwitterController: (SA_OAuthTwitterController *) controller authenticatedWithUsername: (NSString *) username {





NSLog(@"Inside authenticatedWithUsername");

NSLog(@"%@",[[_engine tokenOFAuth] key]);

NSLog(@"%@",[[_engine tokenOFAuth] pin]);

NSLog(@"%@",[[_engine tokenOFAuth] secret]);

[_engine getUserInformationFor:username];



}

tokenOFAuth is the instance of OAToken.



- (void)userInfoReceived:(NSArray *)userInfo forRequest:(NSString *)connectionIdentifier {



NSLog(@"User Info Received: %@", userInfo);

NSDictionary *userDict=[userInfo objectAtIndex:0];



oAuth.user_id=[userDict objectForKey:@"id"];

oAuth.screen_name=[userDict objectForKey:@"screen_name"];

oAuth.oauth_token=[[_engine tokenOFAuth]key];

oAuth.oauth_token_secret=[[_engine tokenOFAuth]secret];

[oAuth synchronousAuthorizeTwitterTokenWithVerifier:[[_engine tokenOFAuth]pin]];

oAuth.oauth_token_authorized=YES;

[oAuth saveOAuthTwitterContextToUserDefaults:oAuth];



[self sendTwitterTweetMethod];





}



-(void)sendTwitterTweetMethod

{

[oAuth loadOAuthTwitterContextFromUserDefaults];

NSString *postUrl = @"https://api.twitter.com/1/statuses/update.json";

ASIFormDataRequest *request = [[ASIFormDataRequest alloc] initWithURL:[NSURL URLWithString:postUrl]];

NSMutableDictionary *postInfo = [NSMutableDictionary dictionaryWithObject:@"I am testing my app" forKey:@"status"];

for (NSString *key in [postInfo allKeys]) {

[request setPostValue:[postInfo objectForKey:key] forKey:key];

}

[request addRequestHeader:@"Authorization" value:[oAuth oAuthHeaderForMethod:@"POST" andUrl:postUrl andParams:postInfo]];

NSLog(@"[oAuth oAuthHeaderForMethod:@"" andUrl:postUrl andParams:postInfo]=%@",[oAuth oAuthHeaderForMethod:@"POST" andUrl:postUrl andParams:postInfo]);

[request startSynchronous];

NSLog(@"Status posted. HTTP result code: %d", request.responseStatusCode);

[request release];





}



But it is giving response:-Status posted. HTTP result code: 401 which means unauthorized.







please suggest me to use this rest api with twitter+oauth and without manually entering pin also. I am stuck here.Please help. Any suggestions would be highly appreciated.


Comments

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex