Hi DenVog, First, cool, you quoted my post at droolfactory.
Raffi: Yes, the Twitter-OAuth-iPhone code from http://github.com/bengottlieb/Twitter-OAuth-iPhone is using page scraping and javascript to pull out the PIN. This is the code that DenVog is referencing from my post. The better way to do this I have been informed is to use the URL callback scheme and have the application handle a unique URL which Twitter would call. I have not found code for this or made the changes yet but it sounds fairly easy to implement. -- Mark Thistle http://droolfactory.blogspot.com/ On Feb 16, 12:02 am, Raffi Krikorian <[email protected]> wrote: > yeah - i remember that issue... your application is screen scraping to get > the OAuth PIN? > > > > > > On Mon, Feb 15, 2010 at 8:07 PM, DenVog <[email protected]> wrote: > > Hi Raffi. Thanks for your reply. > > > After a lot of searching, I found a thread related to my issue. <a > > href="http://droolfactory.blogspot.com/2010/02/fix-for-twitter-oauth- > > iphone-due-to.html">Fix for Twitter-OAuth-iPhone Due to Twitter Mobile > > OAuth Update</a>. I implemented the recommended change, and it appears > > to address the problem. Unfortunately, the fix won't be available to > > users until the app update is approved by Apple (average 2 weeks). > > > How could I have found out about this change in advance? I don't see > > any heads-up notifications related to this. It sucks that users will > > be left with broken functionality until the update is approved. > > > On Feb 15, 5:41 pm, Raffi Krikorian <[email protected]> wrote: > > > hi denvog. > > > > could you please file a report in the google code tracker? i'm not aware > > of > > > a change here. > > > > if you could - please post the path through the API that your application > > is > > > taking, report what used to occur, and then report what is currently > > > happening? do you know when this started happing to your app? > > > > please just post to this list after you file that report, and we'll look > > at > > > it. > > > > On Mon, Feb 15, 2010 at 4:59 PM, DenVog <[email protected]> wrote: > > > > I've been using OAuth in my iPhone application for several weeks now > > > > without issue. Today users started reporting that they can no longer > > > > complete login with username and password. Now it returns a > > > > "Connection Allowed" with a PIN, and wants the user to enter the PIN > > > > into the app. Which of course there is no place in my app to do this. > > > > > I've been poking around the API and discussion forums, but don't see > > > > any formal announcement from Twitter that changes are being made that > > > > are related to this. This seriously screws up my application! Any > > > > insight would be appreciated. I'm hoping this is a temporary Twitter- > > > > side issue. If I'm forced to make changes to my app, the approval > > > > cycle at Apple is averaging 2 weeks. > > > > -- > > > Raffi Krikorian > > > Twitter Platform Teamhttp://twitter.com/raffi > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi
