Looking good! Just a heads up that on Safari on a Mac you have to press enter twice to submit the "username and password" form. Just like with the old oAuth Screen. =)
On 29 Apr., 19:36, bitrace <[email protected]> wrote: > Hi Matt, > > While we welcome improvements to the OAuth screens making it clearer > what an App can or can not do on a users behalf, the changes that you > have rolled out have broken our iPhone App TweetIgnite currently live > in the App store. [http://itunes.apple.com/app/tweetignite/id411873391?mt=8 > ]. Our App uses an OAuth PIN/out-of-band flow. > > As far as I am aware we formatting our OAuth requests correctly (it > all worked before) and indeed we do receive back the html for the > Authorisation page, however it is being rendered in the UIWebView as > blank! > > Some investigation indicates that the style sheet may contain an > incorrectly formed link: > > <link rel="stylesheet" type="text/css" href="//ajax.googleapis.com/ > ajax/libs/yui/3.3.0/build/cssfonts/fonts-min.css"> > > should this not be: > > <link rel="stylesheet" type="text/css" href="http:// > ajax.googleapis.com/ajax/libs/yui/3.3.0/build/cssfonts/fonts-min.css"> > > Also the html returned from our OAuth request contains: > > <style type="text/css"> > html { display:none; } > </style> > > which is clearly why the page is being rendered blank. > > Not sure if this is due to how you now handle certain user-agent > headers? The user-agent presented by our App is TweetIgnite/1.0.3 > (iPhone; iPhone OS 4.3). > > I would be grateful for some help to resolve this? It would also be > good to get advanced warning of future changes, and even have the > ability to test against them before they go live. > > Best regards, > Clive Twist > @clivetwist > > On Apr 28, 10:02 pm, Matt Harris <[email protected]> wrote: > > > > > Hey Developers, > > > Some of you may have noticed already that earlier today we deployed a > > redesign of the OAuth screens. > > > We know both you and your users have been asking for better clarity about > > what an application can see and do with an account and these screens are a > > step towards doing that. > > > One of the areas we wanted to improve is showing the details of your > > application. If you visit the new screens you will see we've separated your > > application details from the permissions that are being requested. We did > > this to help users see that it is your application, not Twitter's. Remember > > you can update your application details at anytime > > onhttp://dev.twitter.com/apps. > > > Mobile and international support has also been improved and we now use the > > same rendering templates as those created for Web Intents. This ensures the > > design matches the rest of #newtwitter and, more importantly, works > > cross-browser, cross-platform, and multilingual. > > > We hope you find the new designs more welcoming and friendly. Let us know > > what you think. > > > Best, > > @themattharris > > Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
