Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

webAccount.username always null #101

Closed
LaurentTermeau opened this issue Aug 1, 2015 · 3 comments
Closed

webAccount.username always null #101

LaurentTermeau opened this issue Aug 1, 2015 · 3 comments

Comments

@LaurentTermeau
Copy link

In the WebAccountManagement sample, the scenario "login with default Microsoft Account" seems to login ok, but the webAccount.userName is always null.
Also, when,extending the scope with wl.emails in,addition,to wl.basics, no emails information is available.
Would This ne because I run,the code from a Windows 10 build 10240 included in,a,professional domain ? Or is This due to annoter reason ?
Laurent

@msftchcamp
Copy link

Normally you would use the token gained from the RequestTokenAsync with the Live APIs (https://msdn.microsoft.com/en-us/library/hh243641.aspx) but right now there is not a LiveSDK for Universal Windows Apps. It is coming, but for now the only way is to use OAUTH. (https://msdn.microsoft.com/en-us/library/hh243647.aspx)

@ryanwinter
Copy link

So is the UWP LiveSDK still coming?

@msftchcamp
Copy link

There is going to be a set of new SDKs that replaces what the LiveSDK used to do pre UWP. (liveservices/LiveSDK-for-Windows#58) But the logic is still the same, get a token from RequestTokenAsync and use it with these APIs.

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

No branches or pull requests

3 participants