Login fails with no ErrorInfo about winsdkfb HOT 8 CLOSED

So you do get a valid token, but the SDK never asynchronosly returns this information to you, is that correct? Are you using the latest develop-branch or the NuGet packages, have you made sure you are using the latest NuGet packages? I am targetting Windows SDK 10.0.18362.0, and have min version of 10.0.17763.0. Using Visual Studio 2019 (v142)… I will try and create a minimal shareable sample of the code that works for me, and then you could potentially try that on your end...

from winsdkfb.

Omg, yes it was a version mishap with nuget. Im so sorry for wasting your time, and thank you so much for the help @johanlindfors.

from winsdkfb.

This is very strange, since I just tried following the documentation (skipping the Windows Phone ID though) and it works just fine for me. This was leveraging the Nuget packages.

I did however add a line to add the FBAppId to the session.

FBSession^ sess = FBSession::ActiveSession;
sess->FBAppId = "";

My test app is a published sample app that I'm using for these purposes.

from winsdkfb.

And it works fine when adding and configuring the _uwp.vcxproj project to the solution and running, no code changes...

from winsdkfb.

Maybe Im messing up something in the project configuration here, because i do get to enter my user/password in the prompt, but the return is an error - like if i dont have permission, or invalid access tokens or anything, its just empty error and no success.

from winsdkfb.

I have the following URL as Valid OAuth Redirect URI:

https://www.facebook.com/connect/login_success.html

from winsdkfb.

I tried with that too + with both and each of them. Sadly same result.
Im sorry i forgot to add in my first post that in the visual studio output window i do get this like
"FBResult destructor
file:///dev/null?access_token=EAADk4VQ8Ygg****************D&data_access_expiration_time=1570103036&expires_in=5182428"

but otherwise nothing changed. I also tried to use PhoneProductId as a WinAppId as one of the suggestion in the instructions were duting testing.. same result

from winsdkfb.

Also the app is still in development status? can that cause an issue too? Although last time i used this plugin i don't remember having such trouble - that was 1 year ago. only that i was forced to use only essionLoginBehavior::WebAuth)

from winsdkfb.