Last 30 days

• Dec 01, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by tom.digr...@gmail.com   -   Not sure if this is an issue or if I'm using an old version. Should 'ticket' be released toward the end of OADataFetcher.m so there isn't a memory leak? Or is that being released somewhere else?

  Not sure if this is an issue or if I'm using an old version. Should 'ticket' be released toward the end of OADataFetcher.m so there isn't a memory leak? Or is that being released somewhere else?
• Dec 01, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by tom.digr...@gmail.com   -   Not sure if this is an issue or if I'm using an old version. Should '[ticket release];' be toward the end of OADataFetcher.m so there isn't a memory leak? Or is that being released somewhere else?

  Not sure if this is an issue or if I'm using an old version. Should '[ticket release];' be toward the end of OADataFetcher.m so there isn't a memory leak? Or is that being released somewhere else?

Earlier this year

• Nov 15, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by hamfilter   -   @zuksh.5 Did your set the destination for the "Copy Files" phase to "Frameworks"? I had a similar problem. Think you are just linking the framework in the wrong way. Remove it and try again step by step.

  @zuksh.5 Did your set the destination for the "Copy Files" phase to "Frameworks"? I had a similar problem. Think you are just linking the framework in the wrong way. Remove it and try again step by step.
• Nov 15, 2009

  issue 6 (Request token not added to the request URL) reported by hamfilter   -   What steps will reproduce the problem? 1. Ask a request token from the OAuth provider as described in the wiki 2. Call the openURL method as described in the wiki 3. The provider (yammer.com in this case) said: "no request token found" What is the expected output? What do you see instead? I expected to see the token in the URL. Not sure if it's passed as a POST request? The URL didn't show the the token in the URL so it's missing if it should be a GET request. What version of the product are you using? On what operating system? Head version from SVN on Mac off course. Please provide any additional information below. I fixed it by adding the request token to the URL (the GET way that is). Not sure if that's correct but it seems to work. This could be a Yammer problem as well, don't know. Here is the code NSString *urlString = [NSString stringWithFormat:kConsumerAuthorizeURL, requestToken.key]; NSURL *url = [NSURL URLWithString:urlString]; [[NSWorkspace sharedWorkspace] openURL:url];

  What steps will reproduce the problem? 1. Ask a request token from the OAuth provider as described in the wiki 2. Call the openURL method as described in the wiki 3. The provider (yammer.com in this case) said: "no request token found" What is the expected output? What do you see instead? I expected to see the token in the URL. Not sure if it's passed as a POST request? The URL didn't show the the token in the URL so it's missing if it should be a GET request. What version of the product are you using? On what operating system? Head version from SVN on Mac off course. Please provide any additional information below. I fixed it by adding the request token to the URL (the GET way that is). Not sure if that's correct but it seems to work. This could be a Yammer problem as well, don't know. Here is the code NSString *urlString = [NSString stringWithFormat:kConsumerAuthorizeURL, requestToken.key]; NSURL *url = [NSURL URLWithString:urlString]; [[NSWorkspace sharedWorkspace] openURL:url];
• Nov 15, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by hamfilter   -   I had some problems authorizing the request token. The OAuth provider complained I did not provide a request token with the example code in the wiki here: {{{ NSURL *url = [NSURL URLWithString:@"http://example.com/authorize"]; [[NSWorkspace sharedWorkspace] openURL:url]; }}} I added the request token to the URL sent to the OAuth provider like this: {{{ NSString *urlString = [NSString stringWithFormat:@"http://example.com/authorize?auth_token=%@", requestToken.key]; NSURL *url = [NSURL URLWithString:urlString]; [[NSWorkspace sharedWorkspace] openURL:url]; }}} Probably not the best way to do it but hey, it works.

  I had some problems authorizing the request token. The OAuth provider complained I did not provide a request token with the example code in the wiki here: {{{ NSURL *url = [NSURL URLWithString:@"http://example.com/authorize"]; [[NSWorkspace sharedWorkspace] openURL:url]; }}} I added the request token to the URL sent to the OAuth provider like this: {{{ NSString *urlString = [NSString stringWithFormat:@"http://example.com/authorize?auth_token=%@", requestToken.key]; NSURL *url = [NSURL URLWithString:urlString]; [[NSWorkspace sharedWorkspace] openURL:url]; }}} Probably not the best way to do it but hey, it works.
• Nov 15, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by simon.schoeters   -   I had some problems authorizing the request token. The OAuth provider complained I did not provide a request token with the example code in the wiki here: {{{ NSURL *url = [NSURL URLWithString:@"http://example.com/authorize"]; [[NSWorkspace sharedWorkspace] openURL:url]; }}} I added the request token to the URL sent to the OAuth provider like this: {{{ NSString *urlString = [NSString stringWithFormat:@"http://example.com/authorize?oauth_token=%@", requestToken.key]; NSURL *url = [NSURL URLWithString:urlString]; [[NSWorkspace sharedWorkspace] openURL:url]; }}} Probably not the best way to do it but hey, it works.

  I had some problems authorizing the request token. The OAuth provider complained I did not provide a request token with the example code in the wiki here: {{{ NSURL *url = [NSURL URLWithString:@"http://example.com/authorize"]; [[NSWorkspace sharedWorkspace] openURL:url]; }}} I added the request token to the URL sent to the OAuth provider like this: {{{ NSString *urlString = [NSString stringWithFormat:@"http://example.com/authorize?oauth_token=%@", requestToken.key]; NSURL *url = [NSURL URLWithString:urlString]; [[NSWorkspace sharedWorkspace] openURL:url]; }}} Probably not the best way to do it but hey, it works.
• Nov 15, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by hamfilter   -   Is there anyone who can add the verifier code (proposed by pchukwura and kimptoc) to the SVN repository? The framework seems kinda useless without this, no? Thank you!

  Is there anyone who can add the verifier code (proposed by pchukwura and kimptoc) to the SVN repository? The framework seems kinda useless without this, no? Thank you!
• Nov 15, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by simon.schoeters   -   Is there anyone who can add the verifier code (proposed by pchukwura and kimptoc) to the SVN repository? The framework seems kinda useless without this, no? Thank you!

  Is there anyone who can add the verifier code (proposed by pchukwura and kimptoc) to the SVN repository? The framework seems kinda useless without this, no? Thank you!
• Oct 06, 2009

  issue 5 (When POSTing, ampersands (&) are always considered as delimi...) reported by i...@neoos.ch   -   What steps will reproduce the problem? 1. POST e.g. XLM data in the HTTP body 2. have some encoded XML special characters in there (like < and > and so on) 3. launch the request What is the expected output? What do you see instead? Expected: XML with encoded chars goes straight through Instead: "*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** - [NSCFArray objectAtIndex:]: index (1) beyond bounds (1)" What version of the product are you using? On what operating system? // NSMutableURLRequest+Parameters.m // // Created by Jon Crosby on 10/19/07. Please provide any additional information below. - The code that's in question resides in the - (NSArray *)parameters method of NSMutableURLRequest+Parameters.m. - & character is considered a delimiter for key/value pairs which is not always the case (as for instance with XML data where & is used to escape special characters)

  What steps will reproduce the problem? 1. POST e.g. XLM data in the HTTP body 2. have some encoded XML special characters in there (like < and > and so on) 3. launch the request What is the expected output? What do you see instead? Expected: XML with encoded chars goes straight through Instead: "*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** - [NSCFArray objectAtIndex:]: index (1) beyond bounds (1)" What version of the product are you using? On what operating system? // NSMutableURLRequest+Parameters.m // // Created by Jon Crosby on 10/19/07. Please provide any additional information below. - The code that's in question resides in the - (NSArray *)parameters method of NSMutableURLRequest+Parameters.m. - & character is considered a delimiter for key/value pairs which is not always the case (as for instance with XML data where & is used to escape special characters)
• Sep 29, 2009

  issue 3 (Not includable in iPhone project) commented on by sebastian.derossi   -   "...resolve the issue by not including KeychainExtensions in the build..." I am getting the same error but can seem to fix it. I removed the Bundle Identifier, is that what you meant? Thanks

  "...resolve the issue by not including KeychainExtensions in the build..." I am getting the same error but can seem to fix it. I removed the Bundle Identifier, is that what you meant? Thanks
• Aug 13, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by mon.casier   -   GUYS THERE IS A BUG! IF YOU USING REQUEST BODY ( [request setHTTPBody: body]; ) FIRST - SIGN THE REQUEST ( eg [request prepare];) and then SET THE BODY OR fix it in _signatureBaseString for OAMutableURLRequest

  GUYS THERE IS A BUG! IF YOU USING REQUEST BODY ( [request setHTTPBody: body]; ) FIRST - SIGN THE REQUEST ( eg [request prepare];) and then SET THE BODY OR fix it in _signatureBaseString for OAMutableURLRequest
• Aug 12, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by mon.casier   -   Hmm, looks like I didn't get some point: 1. I'm creating a OAMutableURLRequest 2. fulfill httpMethod amd headers 3. I can choose - use native SDK NSURLConnection or proposed OADataFetcher I already have a valid access token and can't make queries with it through native SDK: But I'm getting refuse from server (Couldn't authenticate you) {{{ NSString* strUrl = [[[NSString alloc] initWithFormat:@"%@%@", apiServer, requestUrl] autorelease]; NSURL* url = [NSURL URLWithString:strUrl]; OAMutableURLRequest *request = [[OAMutableURLRequest alloc] initWithURL: url consumer: consumer token: accessToken realm: nil signatureProvider: [[OAPlaintextSignatureProvider alloc] init]]; [request setHTTPMethod: method]; if(body != nil) { NSData* dataRequestBody = [body dataUsingEncoding:NSUTF8StringEncoding]; [request setHTTPBody:dataRequestBody]; } [request setValue:@"application/x-www-form-urlencoded" forHTTPHeaderField:@"Content-Type"]; if( [method compare:@"PUT"] == NSOrderedSame ) { [request setValue:@"PUT" forHTTPHeaderField:@"X_HTTP_METHOD_OVERRIDE"]; } [request prepare]; NSHTTPURLResponse* resp = nil; NSError* err = nil; NSData *serverData = [NSURLConnection sendSynchronousRequest: request returningResponse: &resp error: &err]; SEL selector = (serverData != nil) ? success : fail; NSObject* param = (serverData != nil) ? (NSObject*) serverData : (NSObject*) err; if(selector != nil) { if( object != nil) { [self performSelector: selector withObject: object withObject: param ]; } else { [self performSelector: selector withObject: param ]; } } }}} this is app log: {{{ 2009-08-12 21:32:14.495 MyTool[4469:20b] String: PUT&http%3A%2F%2F10.1.1.1%2Fapi%2F0.9%2Fdataset%2Fcreate&%253Cdata%253E%253Cdataset%253E%253Cdata%2520k%3D%2522created_by%2522%2520v%26oauth_consumer_key%3DdwntFN9NJv9HrvMuqNgWbA%26oauth_nonce%3D067BD7D5-9C90-47EC-B19E-E8ACED9472E0%26oauth_signature_method%3DPLAINTEXT%26oauth_timestamp%3D1250101934%26oauth_token%3DubZlywqgHWaaoUlPqdDnvQ%26oauth_version%3D1.0, Array: %253Cosm%253E%253Cdataset%253E%253Cdata%2520k=%2522created_by%2522%2520v&oauth_consumer_key=dwntFN9NJv9HrvMuqNgWbA&oauth_nonce=067BD7D5-9C90-47EC-B19E-E8ACED9472E0&oauth_signature_method=PLAINTEXT&oauth_timestamp=1250101934&oauth_token=ubZlywqgHWaaoUlPqdDnvQ&oauth_version=1.0 2009-08-12 21:32:14.496 MyTool[4469:20b] Headers: { Authorization = "OAuth realm=\"\", oauth_consumer_key=\"dwntFN9NJv9HrvMuqNgWbA\", oauth_token=\"ubZlywqgHWaaoUlPqdDnvQ\", oauth_signature_method=\"PLAINTEXT\", oauth_signature=\"3iF9JIzYQPT5JkvrEXHujCLhI03An302P94JeQoF8%26minE6ZinCiaNlCFfbazOamC1DsD3FcvVF4C1fM5k\", oauth_timestamp=\"1250101934\", oauth_nonce=\"067BD7D5-9C90-47EC-B19E-E8ACED9472E0\", oauth_version=\"1.0\""; "Content-Type" = "application/x-www-form-urlencoded"; "X_http_method_override" = PUT; } }}}

  Hmm, looks like I didn't get some point: 1. I'm creating a OAMutableURLRequest 2. fulfill httpMethod amd headers 3. I can choose - use native SDK NSURLConnection or proposed OADataFetcher I already have a valid access token and can't make queries with it through native SDK: But I'm getting refuse from server (Couldn't authenticate you) {{{ NSString* strUrl = [[[NSString alloc] initWithFormat:@"%@%@", apiServer, requestUrl] autorelease]; NSURL* url = [NSURL URLWithString:strUrl]; OAMutableURLRequest *request = [[OAMutableURLRequest alloc] initWithURL: url consumer: consumer token: accessToken realm: nil signatureProvider: [[OAPlaintextSignatureProvider alloc] init]]; [request setHTTPMethod: method]; if(body != nil) { NSData* dataRequestBody = [body dataUsingEncoding:NSUTF8StringEncoding]; [request setHTTPBody:dataRequestBody]; } [request setValue:@"application/x-www-form-urlencoded" forHTTPHeaderField:@"Content-Type"]; if( [method compare:@"PUT"] == NSOrderedSame ) { [request setValue:@"PUT" forHTTPHeaderField:@"X_HTTP_METHOD_OVERRIDE"]; } [request prepare]; NSHTTPURLResponse* resp = nil; NSError* err = nil; NSData *serverData = [NSURLConnection sendSynchronousRequest: request returningResponse: &resp error: &err]; SEL selector = (serverData != nil) ? success : fail; NSObject* param = (serverData != nil) ? (NSObject*) serverData : (NSObject*) err; if(selector != nil) { if( object != nil) { [self performSelector: selector withObject: object withObject: param ]; } else { [self performSelector: selector withObject: param ]; } } }}} this is app log: {{{ 2009-08-12 21:32:14.495 MyTool[4469:20b] String: PUT&http%3A%2F%2F10.1.1.1%2Fapi%2F0.9%2Fdataset%2Fcreate&%253Cdata%253E%253Cdataset%253E%253Cdata%2520k%3D%2522created_by%2522%2520v%26oauth_consumer_key%3DdwntFN9NJv9HrvMuqNgWbA%26oauth_nonce%3D067BD7D5-9C90-47EC-B19E-E8ACED9472E0%26oauth_signature_method%3DPLAINTEXT%26oauth_timestamp%3D1250101934%26oauth_token%3DubZlywqgHWaaoUlPqdDnvQ%26oauth_version%3D1.0, Array: %253Cosm%253E%253Cdataset%253E%253Cdata%2520k=%2522created_by%2522%2520v&oauth_consumer_key=dwntFN9NJv9HrvMuqNgWbA&oauth_nonce=067BD7D5-9C90-47EC-B19E-E8ACED9472E0&oauth_signature_method=PLAINTEXT&oauth_timestamp=1250101934&oauth_token=ubZlywqgHWaaoUlPqdDnvQ&oauth_version=1.0 2009-08-12 21:32:14.496 MyTool[4469:20b] Headers: { Authorization = "OAuth realm=\"\", oauth_consumer_key=\"dwntFN9NJv9HrvMuqNgWbA\", oauth_token=\"ubZlywqgHWaaoUlPqdDnvQ\", oauth_signature_method=\"PLAINTEXT\", oauth_signature=\"3iF9JIzYQPT5JkvrEXHujCLhI03An302P94JeQoF8%26minE6ZinCiaNlCFfbazOamC1DsD3FcvVF4C1fM5k\", oauth_timestamp=\"1250101934\", oauth_nonce=\"067BD7D5-9C90-47EC-B19E-E8ACED9472E0\", oauth_version=\"1.0\""; "Content-Type" = "application/x-www-form-urlencoded"; "X_http_method_override" = PUT; } }}}
• Aug 05, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by zuksh.5   -   i resolved that issue ... now this one .... kindly reply soon, i cannot understand the cause of this error dyld: Library not loaded: @executable_path/../Frameworks/OAuthConsumer.framework/Versions/A/OAuthConsumer Referenced from: /Users/dssd/Desktop/MGTwitterEngine/MGTwitterEngine/build/Debug/MGTwitterEngine.app/Contents/MacOS/MGTwitterEngine Reason: image not found ---

  i resolved that issue ... now this one .... kindly reply soon, i cannot understand the cause of this error dyld: Library not loaded: @executable_path/../Frameworks/OAuthConsumer.framework/Versions/A/OAuthConsumer Referenced from: /Users/dssd/Desktop/MGTwitterEngine/MGTwitterEngine/build/Debug/MGTwitterEngine.app/Contents/MacOS/MGTwitterEngine Reason: image not found ---
• Aug 04, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by pchukwura   -   What compile are you seeing?

  What compile are you seeing?
• Aug 04, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by zuksh.5   -   Where do we find this OAuthConsumer.Framework ? One in the repository wont compile. Help !!! any help regarding this issue will be highly appreciated.

  Where do we find this OAuthConsumer.Framework ? One in the repository wont compile. Help !!! any help regarding this issue will be highly appreciated.
• Jul 30, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by kimptoc   -   Same problem here, but fixed very quickly thanks to pchukwura, thanks for sharing the solution. For the impatient, just add an extra 'if' clause to only add the whole verifier clause if the verifier value is set, ie dont include the verifier= bit if no verifier...

  Same problem here, but fixed very quickly thanks to pchukwura, thanks for sharing the solution. For the impatient, just add an extra 'if' clause to only add the whole verifier clause if the verifier value is set, ie dont include the verifier= bit if no verifier...
• Jul 29, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by pchukwura   -   If anyone else had the same issues I had, i was able to resolve them... i posted the issue, and fix on my blog. http://nullagenda.com/oauthconsumer-and-twitter-114

  If anyone else had the same issues I had, i was able to resolve them... i posted the issue, and fix on my blog. http://nullagenda.com/oauthconsumer-and-twitter-114
• Jul 29, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by pchukwura   -   yes I am having toruble. I keep getting "invalid/used nonce" error when trying to do a status update from Twitter, even though the nonce is indeed unique. Has anyone solved this issue?

  yes I am having toruble. I keep getting "invalid/used nonce" error when trying to do a status update from Twitter, even though the nonce is indeed unique. Has anyone solved this issue?
• Jul 29, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by akc1085   -   Is anyone else having trouble getting this to work after twitter's last update on July-27-2009? The update is supposed to prevent invalid signatures from being accepted.

  Is anyone else having trouble getting this to work after twitter's last update on July-27-2009? The update is supposed to prevent invalid signatures from being accepted.
• Jul 28, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by akc1085   -   Twitter made a change to their API yesterday and now my app (OAuthConsumer + MGTwitterEngineOAuth[OAuth added by Adium]) doesn't work. Supposedly the change requires that the signature have both consumer secret and access token secret. Looking at OAMutableURLRequest, it looks like the signature does have those two. Any ideas on what's wrong? Hopefully Twitter will give out more information about what was actually changed soon.

  Twitter made a change to their API yesterday and now my app (OAuthConsumer + MGTwitterEngineOAuth[OAuth added by Adium]) doesn't work. Supposedly the change requires that the signature have both consumer secret and access token secret. Looking at OAMutableURLRequest, it looks like the signature does have those two. Any ideas on what's wrong? Hopefully Twitter will give out more information about what was actually changed soon.
• Jul 28, 2009

  issue 3 (Not includable in iPhone project) commented on by mathieu.fancello   -   Hi, i'm triyng to include this framework in my iPhone app. When I try to build it, i have this error : ",objc_class_name_OAMutableURLRequest", referenced from: literal-pointer@_OBJC@_cls_refs@OAMutableURLRequest in MGTwitterEngine.o symbo(s) not found collect2 : Id returned 1 exit status Someone have any ideas ?

  Hi, i'm triyng to include this framework in my iPhone app. When I try to build it, i have this error : ",objc_class_name_OAMutableURLRequest", referenced from: literal-pointer@_OBJC@_cls_refs@OAMutableURLRequest in MGTwitterEngine.o symbo(s) not found collect2 : Id returned 1 exit status Someone have any ideas ?
• Jul 24, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by pchukwura   -   When it comes to the Twitter PIN the user receives, I have my application expect the PIN the user gets after a successful request is made to get the request token. so basically follow the steps of this wiki but do this right before the Obtaining an Access Token step: * Get the PIN number from the NSTextField that the user entered and set it to the 'verifier' property of the token... {{{ [requestToken setValue:[twitterPIN stringValue] forKey:@"verifier"]; url = [NSURL URLWithString:@"http://twitter.com/oauth/access_token"]; }}} This is assuming that OAToken has a 'verifier' property (which I added). Then continue with the steps in this wiki. Hope this helps.

  When it comes to the Twitter PIN the user receives, I have my application expect the PIN the user gets after a successful request is made to get the request token. so basically follow the steps of this wiki but do this right before the Obtaining an Access Token step: * Get the PIN number from the NSTextField that the user entered and set it to the 'verifier' property of the token... {{{ [requestToken setValue:[twitterPIN stringValue] forKey:@"verifier"]; url = [NSURL URLWithString:@"http://twitter.com/oauth/access_token"]; }}} This is assuming that OAToken has a 'verifier' property (which I added). Then continue with the steps in this wiki. Hope this helps.
• Jul 24, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by pchukwura   -   When it comes to the Twitter PIN the user receives, I have my application expect the PIN the user gets after a successful request is made to get the request token. so basically follow the steps of this wiki but do this right before the Obtaining an Access Token step: * Get the PIN number from the NSTextField that the user entered and set it to the 'verifier' property of the token... [requestToken setValue:[twitterPIN stringValue] forKey:@"verifier"]; url = [NSURL URLWithString:@"http://twitter.com/oauth/access_token"]; This is assuming that OAToken has a 'verifier' property (which I added). Then continue with the steps in this wiki. Hope this helps.

  When it comes to the Twitter PIN the user receives, I have my application expect the PIN the user gets after a successful request is made to get the request token. so basically follow the steps of this wiki but do this right before the Obtaining an Access Token step: * Get the PIN number from the NSTextField that the user entered and set it to the 'verifier' property of the token... [requestToken setValue:[twitterPIN stringValue] forKey:@"verifier"]; url = [NSURL URLWithString:@"http://twitter.com/oauth/access_token"]; This is assuming that OAToken has a 'verifier' property (which I added). Then continue with the steps in this wiki. Hope this helps.
• Jul 22, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by fares.farhan   -   Hi, As mrjjwright has mentioned, its a great sample you've bring Isaiah, but I also can't figure it out when Twitter replied successful registration and then respond with PIN and additional message "now simply back to application and enter the PIN". Where do this PIN need to be included, another URL post to Twitter or something else needs to be done first? Cheers, Fares

  Hi, As mrjjwright has mentioned, its a great sample you've bring Isaiah, but I also can't figure it out when Twitter replied successful registration and then respond with PIN and additional message "now simply back to application and enter the PIN". Where do this PIN need to be included, another URL post to Twitter or something else needs to be done first? Cheers, Fares
• Jul 11, 2009

  UsingOAuthConsumer (A developer's guide to using OAuthConsumer in a Mac applicat...) Wiki page commented on by mrjjwright   -   Hey Isaiah, Thanks for the cool project bringing this together. I notice however that your code doesn't seem to take the user's pin that is displayed by Twitter after successful authentication, and I can't seem to authenticate with Twitter without it. Is there something I am missing? I get this error in the console after the pin is displayed (it goes away automatically): 2009-07-11 15:43:52.228 oauth_test_app[59733:10b] fail: 'Error Domain=NSURLErrorDomain Code=-1012 UserInfo=0x10a9b20 "Operation could not be completed. (NSURLErrorDomain error -1012.)"'

  Hey Isaiah, Thanks for the cool project bringing this together. I notice however that your code doesn't seem to take the user's pin that is displayed by Twitter after successful authentication, and I can't seem to authenticate with Twitter without it. Is there something I am missing? I get this error in the console after the pin is displayed (it goes away automatically): 2009-07-11 15:43:52.228 oauth_test_app[59733:10b] fail: 'Error Domain=NSURLErrorDomain Code=-1012 UserInfo=0x10a9b20 "Operation could not be completed. (NSURLErrorDomain error -1012.)"'
• Jul 06, 2009

  issue 1 (Tests fail for ppc (when building on i386)) commented on by peter.m.mcevoy   -   Hiya, Just thought you'd like to know, I ran into this issue today after connecting to the repo and building the project. Quick google found this issue. However, I can't see any README in the obj-c folder, although there is one in the obj-c1 folder. I'll just ignore those tests for now.

  Hiya, Just thought you'd like to know, I ran into this issue today after connecting to the repo and building the project. Quick google found this issue. However, I can't see any README in the obj-c folder, although there is one in the obj-c1 folder. I'll just ignore those tests for now.
• May 29, 2009

  issue 3 (Not includable in iPhone project) commented on by miha.hribar   -   Ahh, have managed to resolve the issue by not including KeychainExtensions in the build. Great stuff!

  Ahh, have managed to resolve the issue by not including KeychainExtensions in the build. Great stuff!
• May 29, 2009

  issue 3 (Not includable in iPhone project) commented on by miha.hribar   -   Hi folks, I'm having problems including this great looking framework in my iPhone app. I have followed the wiki instructions and compiled the framework and included it my app (had to change the frameworks Installation Directory to @executable_path/Frameworks) and added the new copy files build phase. It always builds successfully, but when I run the app I get a strange looking error for which I could not find an answer thus far: dyld: Symbol not found: _CFXMLNodeGetInfoPtr Referenced from: /System/Library/Frameworks/Security.framework/Versions/A/Security Expected in: /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Fra meworks/CoreFoundation.framework/CoreFoundation Any ideas?

  Hi folks, I'm having problems including this great looking framework in my iPhone app. I have followed the wiki instructions and compiled the framework and included it my app (had to change the frameworks Installation Directory to @executable_path/Frameworks) and added the new copy files build phase. It always builds successfully, but when I run the app I get a strange looking error for which I could not find an answer thus far: dyld: Symbol not found: _CFXMLNodeGetInfoPtr Referenced from: /System/Library/Frameworks/Security.framework/Versions/A/Security Expected in: /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Fra meworks/CoreFoundation.framework/CoreFoundation Any ideas?
• May 29, 2009

  issue 3 (Not includable in iPhone project) commented on by miha.hribar   -   Hi folks, I'm having problem including this great looking framework in my iPhone app. I have followed the wiki instructions and compiled the framework and included it my app (had to change the frameworks Installation Directory to @executable_path/Frameworks), added the new copy files build phase. It always builds successfully but when I run the app I get a strange looking error for which I could not find an answer thus far. dyld: Symbol not found: _CFXMLNodeGetInfoPtr Referenced from: /System/Library/Frameworks/Security.framework/Versions/A/Security Expected in: /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Fra meworks/CoreFoundation.framework/CoreFoundation Any ideas?

  Hi folks, I'm having problem including this great looking framework in my iPhone app. I have followed the wiki instructions and compiled the framework and included it my app (had to change the frameworks Installation Directory to @executable_path/Frameworks), added the new copy files build phase. It always builds successfully but when I run the app I get a strange looking error for which I could not find an answer thus far. dyld: Symbol not found: _CFXMLNodeGetInfoPtr Referenced from: /System/Library/Frameworks/Security.framework/Versions/A/Security Expected in: /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Fra meworks/CoreFoundation.framework/CoreFoundation Any ideas?
• May 25, 2009

  issue 3 (Not includable in iPhone project) commented on by kimptoc   -   Hi hsabri, Looks like you have added the OAuth code as a dynamic library to your iphone project - you should add the classes directly, or compile it as a static library. HTH, Chris

  Hi hsabri, Looks like you have added the OAuth code as a dynamic library to your iphone project - you should add the classes directly, or compile it as a static library. HTH, Chris
• May 18, 2009

  issue 3 (Not includable in iPhone project) commented on by hsabri   -   Hey fellows. i'm fairly new to iPhone development. I followed the instructions in the wiki, compiled fine, but when i run the simulator, i get the following message: dyld: Library not loaded: @executable_path/../Frameworks/OAuthConsumer.framework/Versions/A/OAuthConsumer Referenced from: /Users/hsabri/Library/Application Support/iPhone Simulator/User/Applications/0FD6336E-19C5-4533-A3A3-DB358BF0223A/ID.app/ID Reason: image not found Does that look familiar to anyone?

  Hey fellows. i'm fairly new to iPhone development. I followed the instructions in the wiki, compiled fine, but when i run the simulator, i get the following message: dyld: Library not loaded: @executable_path/../Frameworks/OAuthConsumer.framework/Versions/A/OAuthConsumer Referenced from: /Users/hsabri/Library/Application Support/iPhone Simulator/User/Applications/0FD6336E-19C5-4533-A3A3-DB358BF0223A/ID.app/ID Reason: image not found Does that look familiar to anyone?
• May 07, 2009

  issue 3 (Not includable in iPhone project) commented on by mpelzsherman   -   I found that I also had to remove all of the test classes since they have dependencies on SenTestingKit, which I am not using (though perhaps I should be...?)

  I found that I also had to remove all of the test classes since they have dependencies on SenTestingKit, which I am not using (though perhaps I should be...?)
• Apr 30, 2009

  issue 3 (Not includable in iPhone project) commented on by kimptoc   -   Hi, Since my comment above I have it working on the iphone - I just copied the source files into my iphone project, which all worked fine in the simulator. The only problem then was on the phone with the keychain extensions - which I just then removed as I was not using them - but I guess they could be made to work. Thanks Jon. Regards, Chris

  Hi, Since my comment above I have it working on the iphone - I just copied the source files into my iphone project, which all worked fine in the simulator. The only problem then was on the phone with the keychain extensions - which I just then removed as I was not using them - but I guess they could be made to work. Thanks Jon. Regards, Chris
• Apr 30, 2009

  issue 3 (Not includable in iPhone project) commented on by cyrus.najmabadi   -   You can see my port here: http://code.google.com/p/metasyntactic/source/browse/#svn/trunk/iPhoneShared/External/OAuth It may no longer be necessary (since i haven't been keeping up with the development here). Feel free to email me directly if you have any questions: cyrusn@stwing.upenn.edu

  You can see my port here: http://code.google.com/p/metasyntactic/source/browse/#svn/trunk/iPhoneShared/External/OAuth It may no longer be necessary (since i haven't been keeping up with the development here). Feel free to email me directly if you have any questions: cyrusn@stwing.upenn.edu
• Apr 30, 2009

  issue 3 (Not includable in iPhone project) commented on by jermillers   -   Hi Cyrus. I too would be interested in getting the details of the ported code that is compatible with the iPhone.

  Hi Cyrus. I too would be interested in getting the details of the ported code that is compatible with the iPhone.
• Apr 24, 2009

  issue 3 (Not includable in iPhone project) commented on by kimptoc   -   Hi Cyrus, I would be interested in details on the steps needed to port it to the iPhone.

  Hi Cyrus, I would be interested in details on the steps needed to port it to the iPhone.

Older

• Dec 27, 2008

  issue 3 (Not includable in iPhone project) commented on by cyrus.najmabadi   -   I've ported the code over so it can be used on the iPhone. Please contact me if you'd like it to be included in the main OAuthConsumer distribution.

  I've ported the code over so it can be used on the iPhone. Please contact me if you'd like it to be included in the main OAuthConsumer distribution.
• Oct 23, 2008

  issue 4 (Mixed-mode memory management patch) Status changed by jon.r.crosby   -  

  Status: Accepted

  Status: Accepted
• Oct 20, 2008

  issue 4 (Mixed-mode memory management patch) reported by bumppo   -   OAuthConsumer appears to have been written to assume GC, and leaks exuberantly when run in a non-GC environment. I've got a patch to add mixed-mode memory management, which was pleasantly straightforward to put together. I really appreciate how clearly written the framework is, and I've tried not to gum that up. I opted to use properties for accessor generation, and in a couple of places needed read-write in places where you'd specified read-only. I compromised by making those members private if they weren't marked as such already. Here's a summary of the property-related changes: OAMutableURLRequest: signature and nonce moved from protected to private, their properties changed from read-only to read-write. Properties added for consumer, token, realm, signatureProvider, and timestamp. Added "self." to ivar usage in .m to go through accessors. OADataFetcher - Properties added for request, responseData, and delegate. The 'delegate' property retains its ivar, which is a little questionable, but I went with it to match the GC behavior. "self." usage added. OAServiceTicket: ivars were already private, property access changed to read-write. 'self.' usage added. OAConsumer, OAToken, OARequestParameter: Properties were in place, no changes needed. OAHMAC_SHA1SignatureProvider, OAPlaintextSignatureProvider: No ivars, no changes needed. Here's a summary of the other implementation changes in r678-memory-management.diff: OAConsumer.m, OADataFetcher.m, OAHMAC_SHA1SignatureProvider.m, OAPlaintextSignatureProvider.m, OARequestParameter.m, OAServiceTicket.m: Added dealloc only. OAMutableURLRequest.m - Added dealloc, fixed two CF leaks in _generateNonce, additional autoreleasing in _signatureBaseString. OAToken.m - Added dealloc, reformatted initWithUserDefaults[...], storeInUserDefaults[...]. OAToken_KeychainExtensions.m - Changed NSMakeCollectable to CFRelease (outside GC, NSMakeCollectable's returned id objects aren't marked autoreleased). NSMutableURLRequest+Parameters.m - Autoreleasing a couple of things. I also ran into the same URL encoding problem that Mike fixed, and made some further changes there, which are in r678-url-encoding.diff. In NSString+URLEncoding.m, * CFStringRefs are now returned as NSStrings using NSMakeCollectable, which should plug leaks under GC. Returned strings are autoreleased, which plugs leaks not under GC. * I applied the same character overrides to encodedURLString as encodedURLParameterString, because I couldn't figure out why they should be different, given that section 9.1.3 of oauth's spec references the parameter encoding section. (If the overrides are properly the same, perhaps the two encoding methods should be merged.) * I trimmed three chars out of Mike's character overrides, which testing indicates the CF encoding method knows about by default. In NSString+URLEncodingTest.m, Mike's overridden characters are appended to the encoding test. Tested under Intel, all tests passed, no warnings. My OAuth app is just an infant but it exercises most of OAuthConsumer's functionality, and Instruments says I'm now leak-free across my code and the framework. I realize it's a large patch, and if I can do anything to answer questions or make it easier to digest, please let me know. Thanks very much, it was a huge help not to have to learn the protocol from scratch.

  OAuthConsumer appears to have been written to assume GC, and leaks exuberantly when run in a non-GC environment. I've got a patch to add mixed-mode memory management, which was pleasantly straightforward to put together. I really appreciate how clearly written the framework is, and I've tried not to gum that up. I opted to use properties for accessor generation, and in a couple of places needed read-write in places where you'd specified read-only. I compromised by making those members private if they weren't marked as such already. Here's a summary of the property-related changes: OAMutableURLRequest: signature and nonce moved from protected to private, their properties changed from read-only to read-write. Properties added for consumer, token, realm, signatureProvider, and timestamp. Added "self." to ivar usage in .m to go through accessors. OADataFetcher - Properties added for request, responseData, and delegate. The 'delegate' property retains its ivar, which is a little questionable, but I went with it to match the GC behavior. "self." usage added. OAServiceTicket: ivars were already private, property access changed to read-write. 'self.' usage added. OAConsumer, OAToken, OARequestParameter: Properties were in place, no changes needed. OAHMAC_SHA1SignatureProvider, OAPlaintextSignatureProvider: No ivars, no changes needed. Here's a summary of the other implementation changes in r678-memory-management.diff: OAConsumer.m, OADataFetcher.m, OAHMAC_SHA1SignatureProvider.m, OAPlaintextSignatureProvider.m, OARequestParameter.m, OAServiceTicket.m: Added dealloc only. OAMutableURLRequest.m - Added dealloc, fixed two CF leaks in _generateNonce, additional autoreleasing in _signatureBaseString. OAToken.m - Added dealloc, reformatted initWithUserDefaults[...], storeInUserDefaults[...]. OAToken_KeychainExtensions.m - Changed NSMakeCollectable to CFRelease (outside GC, NSMakeCollectable's returned id objects aren't marked autoreleased). NSMutableURLRequest+Parameters.m - Autoreleasing a couple of things. I also ran into the same URL encoding problem that Mike fixed, and made some further changes there, which are in r678-url-encoding.diff. In NSString+URLEncoding.m, * CFStringRefs are now returned as NSStrings using NSMakeCollectable, which should plug leaks under GC. Returned strings are autoreleased, which plugs leaks not under GC. * I applied the same character overrides to encodedURLString as encodedURLParameterString, because I couldn't figure out why they should be different, given that section 9.1.3 of oauth's spec references the parameter encoding section. (If the overrides are properly the same, perhaps the two encoding methods should be merged.) * I trimmed three chars out of Mike's character overrides, which testing indicates the CF encoding method knows about by default. In NSString+URLEncodingTest.m, Mike's overridden characters are appended to the encoding test. Tested under Intel, all tests passed, no warnings. My OAuth app is just an infant but it exercises most of OAuthConsumer's functionality, and Instruments says I'm now leak-free across my code and the framework. I realize it's a large patch, and if I can do anything to answer questions or make it easier to digest, please let me know. Thanks very much, it was a huge help not to have to learn the protocol from scratch.
• Oct 07, 2008

  issue 3 (Not includable in iPhone project) Status changed by jon.r.crosby   -   @adrian.cockcroft is correct. The iPhone does not allow binary user frameworks. I will add a README that explains this now that the NDA has been lifted.

  Status: Accepted

  @adrian.cockcroft is correct. The iPhone does not allow binary user frameworks. I will add a README that explains this now that the NDA has been lifted.

  Status: Accepted
• Oct 07, 2008

  issue 2 (Some sub-delims aren't URLEncoded in OAuth Parameters) Status changed by jon.r.crosby   -   Patch committed. Thanks, Mike!

  Status: Fixed

  Patch committed. Thanks, Mike!

  Status: Fixed
• Sep 05, 2008

  issue 3 (Not includable in iPhone project) commented on by alper.cugun   -   I see now. Thanks! I guess this issue can be closed then.

  I see now. Thanks! I guess this issue can be closed then.
• Sep 05, 2008

  issue 3 (Not includable in iPhone project) commented on by alper.cugun   -   I see now. Thanks!

  I see now. Thanks!
• Sep 04, 2008

  issue 3 (Not includable in iPhone project) commented on by adrian.cockcroft   -   I also tried, and found that Apple does not allow binary user frameworks to be added to Xcode for iPhone targets. However I copied all the source code to my app and it compiles and runs once you change the header includes from <OA....h> to "OA....h".

  I also tried, and found that Apple does not allow binary user frameworks to be added to Xcode for iPhone targets. However I copied all the source code to my app and it compiles and runs once you change the header includes from <OA....h> to "OA....h".
• Aug 30, 2008

  issue 3 (Not includable in iPhone project) reported by alper.cugun   -   I currently can't figure out how to include the oauthconsumer framework in an iPhone app. There seem to be some issues including third party frameworks and some other frameworks have released (jsonframework) have released versions which are precompiled and includable as additional SDKs for iPhone development. Enabling iPhone development would be very nice.

  I currently can't figure out how to include the oauthconsumer framework in an iPhone app. There seem to be some issues including third party frameworks and some other frameworks have released (jsonframework) have released versions which are precompiled and includable as additional SDKs for iPhone development. Enabling iPhone development would be very nice.