On Apr 30, 12:09 pm, 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.
They are not blocked, it's *only* a problem of layout. > 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. I have the same problem, and I don't see why using a webcontrol is a security problem. Since xauth is the exception, why twitter is making the use of oauth so hard ? Matthieu -- 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