-
Notifications
You must be signed in to change notification settings - Fork 11
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
Doesn't work in UWP #79
Comments
@chrisgull The .NET Core 3.1 console itself uses LoginAsync. |
Hi Alex, thanks for quick reply. Other than that, THANK YOU for sharing this package, it's extremely helpful. Lars |
More info: https://docs.microsoft.com/en-us/windows/uwp/networking/sockets This is missing in the project above. Adding such capability does however not resolve the issue. |
OK, some research yielded this: you are using google.apis.auth, which does not support UWP. |
I'm going to try Maui again, see if I can leave UWP behind soon. With some luck your package should work as is. |
Ok and good luck :) |
OK. Tried Maui. Not sure why you closed this issue - it's still an issue? Should I open a new issue? |
I have re-opened it, but at the moment I've very little time to further investigate... |
@chrisgull interested in what your use case is for UWP. I've tried it successfully it in both WPF and MAUI Hybrid (Blazor), FWIW. |
Keeping it open communicates that UWP is not at this time working (and my comments above tell others that it's a Google problem). |
Xamarin, which only supports UWP on windows. |
Hallo , and if you want the oaut working in Xamarin check this doc: https://codingforfun.de/xamarin-google-authentication-with-oauth/ i should be easily translated to maui! |
ConsoleApp sample code works fine as a .NET Core 3.1 console app.
Same code in an UWP app crashes deep in LoginAsync, seems async-related trying to access a disposed Socket object.
I could post a project to reproduce but you already have the code, it's a pretty hard crash and burn.
Let me know if you have questions.
Lars
The text was updated successfully, but these errors were encountered: