-
Notifications
You must be signed in to change notification settings - Fork 12
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
port to v3 of the google play developer API #67
Comments
@JohanLorenzo - is this something we should prioritize? @jcristau - what do we gain? What happens if we don't do it? |
I'm not aware of a planned deprecation of the v2 API. I'd say: let move to v3 (or above) whenever v2 is deprecated or whenever we need some bits of data that is not exposed by the v2 API. How does that sound? |
makes sense. wfm |
It turns out there was this blog post[1], which was released 3 days before my comment 😅 API v2 will be decommissioned on December 1st, 2019. [1] https://android-developers.googleblog.com/2019/03/changes-to-google-play-developer-api.html |
We're using v2 at the moment, should probably look at porting to v3.
Doc for v3 is at https://developers.google.com/android-publisher/#publishing, v2 at https://developers.google.com/android-publisher/archive/v2/
The text was updated successfully, but these errors were encountered: