如果从foursquare传递到Facebook，WebAuthenticationBroker会挂起 [英] WebAuthenticationBroker hangs if passed off to Facebook from foursquare

问题描述

我写了一个基于XAML的WinRT应用程序，它通过WebAuthenticationBroker.AuthenticateAsync调用连接到foursquare。

I've written a XAML-based WinRT app that connects to foursquare via the WebAuthenticationBroker.AuthenticateAsync call.

如果用户选择直接通过foursquare进行身份验证或通过foursquare注册，则代码可以正常工作。但是，foursquare OAuth页面为用户提供了通过Facebook登录/注册的选项。如果选中，初始Facebook登录屏幕
将正确显示;用户可以输入用户名/密码并选择"登录"按钮;然后窗口变成空白。似乎控制权被传递到Facebook的弹出窗口，提示授予权限。但是，WebAuthenticationBroker
未显示此内容。出于所有意图和目的，WebAuthenticationBroker挂起。

The code works fine if the user chooses to authenticate directly through foursquare, or sign up through foursquare. However, the foursquare OAuth page gives the user the option of logging in/signing up via Facebook. If selected, the initial Facebook login screen displays correctly; the user can enter a username/password and select the 'log in' button; then the window goes blank. It appears control is being passed off to Facebook's popup prompting for permissions to be granted. However, the WebAuthenticationBroker is not displaying this. For all intents and purposes, WebAuthenticationBroker is hung.

是否存在这种行为的解决方法？

Does there exist a workaround for this behavior?

推荐答案

你可能最好不要问那些人。Foursquare的 如果你没有随身携带它们，那么给我发一个应用程序，我们会看看它。

You might be better off asking the folks at Foursquare.  If you don't get anywhere with them, then send me an app and we'll look at it.

这篇关于如果从foursquare传递到Facebook，WebAuthenticationBroker会挂起的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！