[supply] Update to Google Play Developer API v3 (v2 end of life Dec 2019)

[sschendel]

Google Play Developer Developer Publishing API v2 (currently used by supply) will end of life Dec 2019.

https://android-developers.googleblog.com/2019/03/changes-to-google-play-developer-api.html

[brenwell]

fastlane/supply/lib/supply/client.rb

Line 2 in a8a602e

require 'google/apis/androidpublisher_v2'

Spent a few minutes running through my server code this morning trying to find references to v2 pleased its only here in the supply lib.

Thanks for the awesome lib Team Fastlane!

[janpio]

Ruby client is available for v3: https://developers.google.com/api-client-library/ruby/apis/androidpublisher/v3
Code for that at the expected place: https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google/apis/androidpublisher_v3

---

A diff of https://developers.google.com/apis-explorer/#p/androidpublisher/v2/ vs https://developers.google.com/apis-explorer/#p/androidpublisher/v3/ shows that some methods seem to be gone:

androidpublisher.edits.apklistings.delete	Deletes the APK-specific localized listing for a specified APK and language code.
androidpublisher.edits.apklistings.deleteall	Deletes all the APK-specific localized listings for a specified APK.
androidpublisher.edits.apklistings.get	Fetches the APK-specific localized listing for a specified APK and language code.
androidpublisher.edits.apklistings.list	Lists all the APK-specific localized listings for a specified APK.
androidpublisher.edits.apklistings.patch	Updates or creates the APK-specific localized listing for a specified APK and language code. This method supports patch semantics.
androidpublisher.edits.apklistings.update	Updates or creates the APK-specific localized listing for a specified APK and language code.

We will have to look into if our code uses any of those.

---

Quick look through a diff of https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google/apis/androidpublisher_v2 vs. https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google/apis/androidpublisher_v3:

• classes.rb:
  • ApkListing and ListApkListingsResponse are indeed gone
  • some renaming
  • new CountryTargeting and LocalizedText
  • SubscriptionPurchase has new accessor auto_resume_time_millis
  • Track has several new accessors
• representations.rb
  • similar to classes.rb
• service.rb
  • delete_apk_listing, delete_all_apk_listings, get_apk_listing, list_apk_listings, patch_apk_listing, update_apk_listing are gone
  • many other methods are (slightly) renamed

Unfortunately we are using some of these methods and classes that seem to be gone:

fastlane/supply/lib/supply/client.rb

Line 215 in a8a602e

client.list_apk_listings(

fastlane/supply/lib/supply/client.rb

Line 344 in a8a602e

apk_listing_object = Androidpublisher::ApkListing.new({

So this definitely will not be a drop in replacement.

[janpio]

Here is another blog post from Google that highlights some of the changes in the API: https://android-developers.googleblog.com/2018/06/automating-your-app-releases-with.html

---

API docs v2: https://developers.google.com/android-publisher/archive/v2/
API docs v3: https://developers.google.com/android-publisher/api-ref/

Comparing this gives a more positive outlook:

• apklisting seems to have been the place for release notes, which are now part of the track.
• there is a new bundle endpoint collection

So stuff we had still seems to be there in one way or another.

[lidorDF]

Google Play Developer Developer Publishing API v2 (currently used by supply) will end of life Dec 2019.

https://android-developers.googleblog.com/2019/03/changes-to-google-play-developer-api.html

Any estimations regarding this issue?

[janpio]

What are you asking for @lidorDF?

It will be a problem, we created an issue about it, now someone can do the work and fix it.

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[gwynjudd]

This doesn't appear to be resolved, a quick search shows that supply is still using the v2 API

[iagormoraes]

First of all, great work Fastlane team, the product it's fantastic, now, what is the release of the new version that uses V3 of Google Play Developer API as we will have until December 1 of 2019 to finish it

[BrianJVarley]

This doesn't appear to be resolved, a quick search shows that supply is still using the v2 API

Also following this thread for update

[alexgarret]

Hi Fastlane team,

I am also following this thread, to be notified when the update supporting Google API V3 will be ready.
Looking forward to update Fastlane 🚀

[matthewkrueger]

The Play Store Developer console started showing a warning recently about this issue

We’ve detected that your app is using an old version of the Google Play Developer API. From December 1 2019, versions 1 and 2 of this API will no longer be available. Update to version 3 before this date.

I imagine there are many people who scratched their heads for a minute to figure out what was using the Google Play Developer API, only to realize it's fastlane. I'm just commenting here to help others save time tracking down what's going on. Thanks fastlane team!