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

GoogleWebAuthorizationBroker not working for .net core 1.0 #872

Closed
Larswa opened this issue Nov 10, 2016 · 7 comments
Closed

GoogleWebAuthorizationBroker not working for .net core 1.0 #872

Larswa opened this issue Nov 10, 2016 · 7 comments
Assignees

Comments

@Larswa
Copy link

Larswa commented Nov 10, 2016

When trying to run this Google.Apis.Calendar sample (https://developers.google.com/google-apps/calendar/quickstart/dotnet) in a .net core 1.0 console application there are two classes that cant be resolved from .net core:

Google.Apis.Auth.OAuth2.GoogleWebAuthorizationBroker
Google.Apis.Util.Store.FileDataStore

@chrisdunelm
Copy link
Contributor

These two classes are not present in the PlatformServices part of the NetStandard build of Google.Apis.Auth.
That is, they're not in GoogleApis.Auth.NetStandard or GoogleApis.Auth.PlatformServices_Shared, which are the sources for NetStandard.
So it's expected that they can't be resolved.

In the v2.0 release (expected early 2017) we will revisit all these auth mechanisms and make sure the full range are available on as many (supported) platforms as possible.

@Larswa
Copy link
Author

Larswa commented Nov 10, 2016

Thanks Chris, for the update and the timeframe guesstimate.

@Grandizer
Copy link

It is now March and am wondering when "Early" will become "Now"? ETA Hours, Days, Weeks? Thank you.

@JoshZA
Copy link

JoshZA commented Mar 9, 2017

An updated would be appreciated 👍

@Grandizer
Copy link

I noticed after I posted that this thread is closed.

@LindaLawton
Copy link
Collaborator

see #787

@chrisdunelm
Copy link
Contributor

Yes, further discussion will be happening on #787.
But, as stated there: We have no specific timescale for this work. It'll be a matter of weeks/months until this is investigated.

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

5 participants