I don't know whether it's the only working solution, but it is the only
proper OAuth procedure and as far as I'm aware, also the recommended one.
On 5/3/11 4:50 AM, Bess wrote:
I'd like to confirm the all the developers here on this mailing list.
Does the new OAuth redesign page prevent you from using OAuth in a new
This OAuth hack is officially not going to work going forward?
Hi Tom van der Woerdt,
Your recommend using the workaround launching OAuth in a safari
browser outside the app? Your suggested approach will require user to
quit and exit app and authenticate with OAuth using device mobile
browser. Then ask user to go back to the app again. Is this the only
On Apr 30, 9:09 am, Tom van der Woerdt<i...@tvdw.eu> wrote:
I've heard this before.
It sounds like all UIWebView, WebBrowser and probably Android's WebView
are blocked. This is definitely a *good* thing for security reasons.
The "workaround" I recommend: launch the actual browser, using a
<yourapp>:// link (something like myapplication://tokenDone) as the
return URL. This is a LOT safer for the users.
On 4/30/11 8:55 AM, Bob12345 wrote:
I'm having this problem too. My login browser inside the phone app is
now rendered useless, it doesn't even scroll.
On Apr 28, 1:41 pm, Shannon Whitley<shannon.whit...@gmail.com> wrote:
I was surprised to see a newly formatted oAuth Authenticate Page. The
new page doesn't account for the scores of oAuth implementations that
popup a new window.
There is an ad-hoc standard for the window height and width that makes
for a decent user experience. The new format will cause issues for
the user since it results in page scrolling.
Can we discuss this new page format and determine if it can be changed
or if we can have alternate formats?
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: