Yes. But I don't like xAuth :-) (Not that that should be relevant for you)

Anyway, the "Microsoft.Phone.Tasks.WebBrowserTask" is exactly what I meant. Can you get WM7 to recognize a yourapp:// URL (custom scheme)? You could have the OAuth login flow redirect back to that page with the oauth code (not talking about oob authorization, but the normal flow) and get the token that way. For the user, this would probably be the best way.


On 4/30/11 10:33 PM, Bob12345 wrote:
Thanks for your response Tom, but I am not sure whether this could be
done on a Windows Phone 7.
The only way to open a regular browser window from a Silverlight app
on the phone(that I know of) is to use
Microsoft.Phone.Tasks.WebBrowserTask and that just opens a webpage.

Would it be possible to bypass this new screen altogether if I were to
use xAuth?



On Apr 30, 9:09 am, Tom van der Woerdt<>  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:50 AM, Bob12345 wrote:

I've been using a WebBrowser control in my Window Phone application to
login into Twitter. Today I noticed that the login/authorization page
format had changed and it is now unusable in a web browser control
that my application displays. The text on the page is squeezed
together, and the page unscrollable. If I paste the URI into the
desktop browser it displays a full-sized desktop login screen listing
all of the app's capabilities. Is anybody else having this issue? Do
you know of a workaround for this problem?

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to