You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
I have a scenario where I have already created Facebook APP with existing Windows Store SID which is different from the one I have. I can check it with:
So I am tring to set WinAppId from the App in developer.facebook.com
sess->WinAppId = xxx // Where xxx is the ID from developer.facebook.com
Yet no matter what WinAppId is set it always run while Windows Store SID (in developer.facebook.com) is equal to an ID I get from WebAuthenticationBroker::GetCurrentApplicationCallbackUri()->DisplayUri
So my question is:
If it is possible to set sess->WinAppId to be different than the one I get WebAuthenticationBroker::GetCurrentApplicationCallbackUri()->DisplayUri; ?
Or I could just change Windows Store SID in visual studio somehow?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a scenario where I have already created Facebook APP with existing Windows Store SID which is different from the one I have. I can check it with:
WebAuthenticationBroker::GetCurrentApplicationCallbackUri()->DisplayUri;
So I am tring to set
WinAppId
from the App in developer.facebook.comsess->WinAppId = xxx // Where xxx is the ID from developer.facebook.com
Yet no matter what WinAppId is set it always run while Windows Store SID (in developer.facebook.com) is equal to an ID I get from
WebAuthenticationBroker::GetCurrentApplicationCallbackUri()->DisplayUri
So my question is:
If it is possible to set
sess->WinAppId
to be different than the one I getWebAuthenticationBroker::GetCurrentApplicationCallbackUri()->DisplayUri;
?Or I could just change Windows Store SID in visual studio somehow?
The text was updated successfully, but these errors were encountered: