Google-api-ruby-client: Oauth_v2

Created on 4 Sep 2020 · 6Comments · Source: googleapis/google-api-ruby-client

Oauth_v2 is deleted from 0.44.0 Due to that we have issues with the app crashes and google login stopped working. Can you please update on this and let us know why is this being done.

Thanks for stopping by to let us know something could be better!

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

Please run down the following list and make sure you've tried the usual "quick fixes":

Search the issues already opened: https://github.com/googleapis/google-api-ruby-client/issues
Search Stack Overflow: https://stackoverflow.com/questions/tagged/google-api-client+ruby

If you are still having issues, please be sure to include as much information as possible:

Environment details

OS:
Ruby version:
Gem name and version:

Steps to reproduce

Code example

# example

Making sure to follow these steps will guarantee the quickest resolution possible.

Thanks!

question

Source

davidraj

👍4

All 6 comments

This API is no longer listed in the google discovery service (https://www.googleapis.com/discovery/v1/apis). Hence the client no longer generates it. I'm not sure why it's disappeared from discovery, though. I'll open an inquiry.

dazuma on 9 Sep 2020

Subscribing to this thread as I also want to know why OauthV2 was removed.

mightymercado on 10 Sep 2020

@dazuma Thank you for looking into this! Has there been any response about the discovery service? I've pinned this dependency for now, but is there any risk to the availability of the actual API?

bak on 21 Sep 2020

Readded in 0.46.1, but apparently deprecated (see https://www.googleapis.com/discovery/v1/apis)

ojab on 13 Oct 2020

👍1

Yes, OAuth2 V2 was re-added. It is deprecated, and a replacement is in the works, but the existing library should not be removed until the replacement is in place and an appropriate migration period has elapsed.

dazuma on 9 Nov 2020

👍1

Yes, OAuth2 V2 was re-added. It is deprecated, and a replacement is in the works, but the existing library should not be removed until the replacement is in place and an appropriate migration period has elapsed.

Thanks for following up on that @dazuma ! I was searching for replacement plans. Do we have any place to track that? Should we just follow the repo for updates? Or perhaps some announcements section anywhere in the docs?