Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Not Implemented Exception thrown when using Windows phone 8.1 SDK #7

Open
thehetz opened this issue Sep 30, 2014 · 0 comments
Open

Comments

@thehetz
Copy link

thehetz commented Sep 30, 2014

I am working through the samples for login on the facebooksdk.net site and have the sample for login working for a Windows store app working as expected.

I cannot get the sample for a Windows Phone app to work properly, however. When I follow the sample, I have to first modify the XAML namespace sample from: xmlns:facebookControls="clr-namespace:Facebook.Client.Controls;assembly=Facebook.Client" to xmlns:facebookControls="using:Facebook.Client.Controls". This is the same as it is for the Windows Store application and prevents a compilation error in VS 2013 from occurring. Even after doing this, I do NOT see the login button appear in the designer as I do for the Windows app. At runtime the button does appear in the emulator or on a device. When clicking the Facebook login button a “Not Implemented Exception” is thrown from deep in the stack which appears to be coming from Facebook.Client.FacebookSessionClient as can be seen in this stack trace:

at Windows.Security.Authentication.Web.WebAuthenticationBroker.AuthenticateAsync(WebAuthenticationOptions options, Uri requestUri, Uri callbackUri)
at Facebook.Client.FacebookSessionClient.d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter1.GetResult() at Facebook.Client.FacebookSessionClient.<LoginAsync>d__18.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Facebook.Client.FacebookSessionClient.d__e.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Facebook.Client.Controls.LoginButton.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Facebook.Client.Controls.LoginButton.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.b__3(Object state)
at System.Threading.WinRTSynchronizationContext.Invoker.InvokeCore()

I am wondering if this is something that is known and if there is a work around for this issue? Here are the versions of the NuGet packages that I am currently using:
Facebook: 6.0.10.0
Facebook.Client: 0.9.1.0
Visual Studio 2013 R3 with .NET 4.5.1

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant