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

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

Closed
sschendel opened this issue Apr 11, 2019 · 58 comments
Closed

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

sschendel opened this issue Apr 11, 2019 · 58 comments

Comments

@sschendel
Copy link
Contributor

@sschendel sschendel commented Apr 11, 2019

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
Copy link

@brenwell brenwell commented Apr 12, 2019

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!

Loading

@janpio
Copy link
Member

@janpio janpio commented Apr 12, 2019

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:

client.list_apk_listings(

apk_listing_object = Androidpublisher::ApkListing.new({

So this definitely will not be a drop in replacement.

Loading

@janpio
Copy link
Member

@janpio janpio commented Apr 12, 2019

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.

Loading

@lidorDF
Copy link

@lidorDF lidorDF commented May 12, 2019

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?

Loading

@janpio
Copy link
Member

@janpio janpio commented May 13, 2019

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.

Loading

@fastlane-bot

This comment has been hidden.

@gwynjudd
Copy link

@gwynjudd gwynjudd commented Jun 12, 2019

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

Loading

@iagormoraes
Copy link

@iagormoraes iagormoraes commented Jun 13, 2019

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

Loading

@BrianJVarley
Copy link

@BrianJVarley BrianJVarley commented Jun 14, 2019

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

Loading

@alexgarret
Copy link

@alexgarret alexgarret commented Jun 14, 2019

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 🚀

Loading

@matthewkrueger
Copy link

@matthewkrueger matthewkrueger commented Jun 26, 2019

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!

Loading

@janpio
Copy link
Member

@janpio janpio commented Jun 26, 2019

Thanks for the update @matthewkrueger, and thanks to Google Play Store actually being so communicative on this. Won't slip through the cracks until end of the year 🥇

Loading

@scorpion35
Copy link
Contributor

@scorpion35 scorpion35 commented Aug 6, 2019

Started some work. Got the download (supply init) part down. Any contributions are more than welcome!

Branch: https://github.com/scorpion35/fastlane/tree/androidpublisherv3

Tracking doc: https://github.com/scorpion35/fastlane/blob/androidpublisherv3/supply/androidpublisherv3_tracking.md

Next: Migrate supply run stuff.

Loading

@janpio
Copy link
Member

@janpio janpio commented Aug 19, 2019

Possibly relevant context for you @scorpion35 on how a tool doing similar things solved this: microsoft/google-play-vsts-extension#129

Loading

@scorpion35
Copy link
Contributor

@scorpion35 scorpion35 commented Aug 19, 2019

Thanks, @janpio! Didn't know there's competition 😁

Think I got halfway through supply run stuff. Updated the tracking doc with all changes so far. Can you take a look when you get a min, please? Would like early feedback if possible :) Added comments on each commit!

Everything above uploader.rb#L36* is working. Let me know if you have any questions!

*except, bundles stuff. Getting some test bundles to test tomorrow!

Update: Uploading app bundles is working as well!
--version_name 1.2.3 --track 'beta' --release_status inProgress --aab_paths 'test.aab' --rollout 0.01 created version 1.2.3 in beta track and released it at 1%

Loading

@scorpion35
Copy link
Contributor

@scorpion35 scorpion35 commented Aug 23, 2019

Hit a road block. Helpppp :)
#15222

Loading

@SimonErich
Copy link

@SimonErich SimonErich commented Sep 3, 2019

Sorry guys, just to make sure:
There is work being done on upgrading the internal workings of fastlane to go with v3 right now, right?
Or is there a solution already available, that we can use to get fastlane working, without having to relace it with another tool?

Loading

@janpio
Copy link
Member

@janpio janpio commented Sep 3, 2019

Yes, there is work going on, in this case by contributor @scorpion35. But there will also be a directed effort by the fastlane team to get this fixed before EOL in Dec 2019 if need be. @SimonErich

Loading

joshdholtz added a commit that referenced this issue Oct 25, 2019
#14573

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "no"
@joshdholtz
Copy link
Member

@joshdholtz joshdholtz commented Oct 26, 2019

Hello, again! I wanted to give a little bit more information and the in-and-outs and status of this changes while my 🧠 is warming up with a cup of this morning 😊

Task Status

Working/Fixed

  • Release APK
    • With and without rollout
    • With uploading main and patch OBB
    • With referencing existing main and patch OBB
  • Release bundle (AAB)
    • With and without rollout
  • Update rollout of track
  • Promote
    • Move release from one track to another
    • Also can update rollout
  • Change log
    • Download
    • Upload
  • Images
    • Download
    • Upload
  • Screenshots
    • Download
    • Upload
  • Metadata
    • Download
    • Upload

Untested/Working On

  • Updating unit tests

Why is this change taking so long?

The update from Google::Apis::AndroidpublisherV2 to Google::Apis::AndroidpublisherV3 is not as simple of a replacement as just updating a gem/module (even though some updates have been in the past 😇). V2 to V3 had a name change to almost everything service method that supply uses and it also included a different data model change to tracks, releases, and version codes (which are pretty much the heart of supply). What this meant was that pretty much nothing ran when changing to the new module 🙃

The replacement process had to start at our lowest level of services and slowly work its way up the higher functional. Some of these new additions included explicitly creating tracks that didn't exist yet (things that we didn't need to do in V2) and manually creating releases (which wasn't as complicated but still a change). Rollout and promoting tracks also took a pretty big chunk of time since the APIs and logic behind these were almost a 100% change. Releases in a track can also now be custom named meaning they are no longer the "version name" which also forced an internal change of things are looked up.

The last big change was that tracks can have multiple releases which can have multiple versions. What this meant was that we could always say just "promote beta to production". Beta might have multiple version codes in it so we had to add a new optional configuration into supply called version_code which can be used to specify which release you would like to promote up from a track.

This isn't even all of the changes from Google::Apis::AndroidpublisherV2 to Google::Apis::AndroidpublisherV3 that had to happen but just the ones that come to mind 😊 But all of these changes had to be backwards compatible with the existing supply interface and docs so that none our users existing setups broke.

Along with all of this, there were also the yearly Xcode and iOS updates that required new support from fastlane and its other tools along with handling any other changes/fixes that our users reported 😇 We always try to do things as quick as we can for our users so you are all the reason we make fastlane ❤️ Its always hard balancing what to give our attention to and sadly this fix kept getting interrupted.

I can't thank @scorpion35 enough for starting the PR (and congrats on fatherhood!). The ground work that @scorpion35 laid out was amazing. Finishing up the PR with the features that still need fixing, making sure its backwards compatible, fixing the unit tests, and updating documentation was still however a pretty big task but its my highest priority right now 💪

I could have definitely provided more transparency about these updates so my sincerest apology to the community for not providing that 😔 fastlane is my passion and my life so I'm taking this as a lesson learned and going to grow from it 📈

Can't wait to get these changes out to everyone who needs them. I will post back next week the PR is ready for some early testing (with instructions provided on how to do that). I appreciate everyone's patience ❤️

Now its time to get back to development now that I'm warmed up 😏🚀

Loading

@mieliespoor
Copy link

@mieliespoor mieliespoor commented Oct 27, 2019

Thank you for the comprehensive feedback and status update. Much appreciated!

Loading

@joshdholtz
Copy link
Member

@joshdholtz joshdholtz commented Oct 29, 2019

Hello, everyone 👋

I thhiinnnkkkk PR #15269 is ready for some early testers if anybody wants to give AndroidpublisherV3 a shot 🙃 All the functionality should be working but I"m sure there are some edge cases that may have been missed 😇

I have to get unit tests all fixed up yet but hopefully that's the easy part 🙏 If anybody has any issues when testing this out, please post them in the PR for me to see 👌

How to use this PR

Updated your Gemfile to 👇 and run bundle install, bundle update fastlane, or bundle update

gem 'fastlane', :git => 'https://github.com/scorpion35/fastlane.git', :branch => 'androidpublisherv3'

Loading

@joshdholtz
Copy link
Member

@joshdholtz joshdholtz commented Nov 6, 2019

Hello!

Another update for you all today 😊 PR #15269 is pretty much code complete and all functionality has been tested and seems like it should be zero work for most people. There are some new options and some deprecated options but nothing that will be a breaking change.

I'm doing one more final pairing session with @snatchev today to code review and integration test. After this it should be pretty much 💯 to release.

The tests in supply have always been lacking so there aren't a ton of tests to fix for this but we are going to improve the test coverage. It may or may not be in this PR but there will be improved test coverage coming 💪

This PR will probably be good to release on Friday but will probably wait until next Monday or Tuesday so that nothing could possibly break over the weekend 😇

Thanks again for the patience ❤️

Loading

joshdholtz added a commit to scorpion35/fastlane that referenced this issue Nov 8, 2019
fastlane#14573

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "no"
@joshdholtz
Copy link
Member

@joshdholtz joshdholtz commented Nov 8, 2019

Alright, fastlane fam! PR #15269 is ready 💪 All the things in supply work, all the actions that also use supply have been tested and fixed if needed, tests pass, and migration doc has been added explaining whats new and what is deprecated. This should not be a breaking change for majority of users 🤞

I'm not expecting any major issues with most users upgrading to this but I'm sure things will come up as software is software 🙃 I'm going to merge this tomorrow but will releasing this on Monday under version 2.135.0. I'll be paying super close attention to issues the whole week 😝

🙏 Please mention me in the issue if you see anything
😱 If its super bad you can tweet me a link to the GitHub issue at @joshdholtz but don't abuse 😇

And a huge thanks to @scorpion35 for getting this PR started and @snatchev for pairing and code reviewing with me ❤️

Loading

@markwongsoontorn
Copy link

@markwongsoontorn markwongsoontorn commented Nov 8, 2019

Thanks guys, totally understand that this requires more testing on edge cases to get it right, patience is the key.
Keep up the good work fastlane !

Loading

@wman1980
Copy link

@wman1980 wman1980 commented Nov 8, 2019

@joshdholtz awesome and its very appreciated. Looking forward for the release and have a nice and relaxed weekend until next week 🙃

Loading

joshdholtz added a commit that referenced this issue Nov 11, 2019
* AndroidPublisher API V3 init

#14573

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "no"

* Added a method to return a list of all tracks

Can filter out tracks as well

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "yes"

* Bug fix

Branch: "androidpublisherv3" | Commit Type: "Bug fix" | Changes tested: "yes"

* Updated methods for listings and images from v3

Branch: "androidpublisherv3" | Commit Type: "Refactor" | Changes tested: "yes"

* Added tracking doc for v3 migration

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "yes"

* [In progress] Fetching release listings for given version number

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "yes"

* Updated tracking doc

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "yes"

* Added track to ReleaseListing

Would be useful to identify which track the version was found in.

Branch: "androidpublisherv3" | Commit Type: "Enhancement" | Changes tested: "yes"

* Properly setting version number

Branch: "androidpublisherv3" | Commit Type: "Bug fix" | Changes tested: "yes"

* [In progress] Supply/setup/store_metadata downloading successfully

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "yes"

* Downloading full size screenshots

Copied from https://github.com/fastlane/fastlane/pull/14322/files. Hoping to get in integrated with AndroidPublisherV3 migration

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "no"

* Writing changelogs

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "yes"

* Updated tracking doc

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "no"

* Added notes to tracking doc

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "yes"

* Renamed method name

Branch: "androidpublisherv3" | Commit Type: "Minor refactor" | Changes tested: "yes"

* Removed test line

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "on"

* Removed test line

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "no"

* Added version flag to list of accepted args

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "no"

* Using -n instead to specify version flag

Also tweaked the error message to be more clear

Branch: "androidpublisherv3" | Commit Type: "Bug fix" | Changes tested: "yes"

* Setting track precedence if version is found in more than one track

Error catching as well

Branch: "androidpublisherv3" | Commit Type: "Bug fix / Enhancement" | Changes tested: "yes"

* Updating tracking doc

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "no"

* Fixed link

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "no"

* Made version number optional and automatically getting latest version if not specified

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "yes"

* Updated tracking

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "yes"

* Returning full resolution screenshots/images from a single source

Branch: "androidpublisherv3" | Commit Type: "Enhancement" | Changes tested: "yes"

* Updated tracking doc

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "yes"

* Checking in other tracks if specified, when production track doesn't have any version

Also added default track variable to avoid hardcoding in various places

Branch: "androidpublisherv3" | Commit Type: "Bug fix / Enhancement" | Changes tested: "yes"

* Tracking doc update

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "yes"

* Bug fix

Branch: "androidpublisherv3" | Commit Type: "Bug fix" | Changes tested: "yes"

* Bug fix - Checking if version is nil and track is set by default to 'production'

Took a while to figure out. --track options default value is set in options.rb

Branch: "androidpublisherv3" | Commit Type: "Bug fix" | Changes tested: "yes"

* [In progress] Uploading changelogs

Added a couple of global variables to avoid hard coding; Added new option (-e) to specify release status; Deprecated old API methods

Branch: "androidpublisherv3" | Commit Type: "New feature" | Changes tested: "yes"

* Tracking doc update

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "yes"

* Validation - Cannot specify rollout percentage when release status is 'draft'

Branch: "androidpublisherv3" | Commit Type: "Enhancement" | Changes tested: "yes"

* Fixed lines removed by mistake from previous commit

Also turned off fastlane update checker temporarily. It's crashing for some reason (psych something something. can't figure out what it is exactly)

Branch: "androidpublisherv3" | Commit Type: "Bug fix" | Changes tested: "yes"

* Updated tracking doc

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "no"

* Added new option to just upload changelogs (i.e. without touching storefront metadata)

Branch: "androidpublisherv3" | Commit Type: "New feature / Enhancement" | Changes tested: "yes"

* Moved upload_changelogs to uploader.rb to just have client methods in client.rb

Branch: "androidpublisherv3" | Commit Type: "Refactor" | Changes tested: "yes"

* Converting --version_codes_to_retain to numbers

Branch: "androidpublisherv3" | Commit Type: "Bug fix / Enhacement" | Changes tested: "yes"

* Can now specify version codes to be added to release

Branch: "androidpublisherv3" | Commit Type: "Enhancement" | Changes tested: "yes"

* Tracking doc update

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "yes"

* Uploading apk's first if specified

This allows to get the version codes to be added to track release. And also, don't have to duplicate the code for uploading changelogs!

Branch: "androidpublisherv3" | Commit Type: "Refactor / Enhancement" | Changes tested: "yes"

* Updated tracking doc

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "no"

* Adding rollout percentage to release

Branch: "androidpublisherv3" | Commit Type: "Enhancement" | Changes tested: "yes"

* Updating tracking doc

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "no"

* [In progress] Updating rollout for a release

Also changed defaults for upload metadata/screenshots to be explicit if only the user wants to. For example, if I am trying to just update the rollout for an already released version.

Branch: "androidpublisherv3" | Commit Type: "Refactor" | Changes tested: "yes"

* Updating tracking doc

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "no"

* Fixed link

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "yes"

* Removed comment

Branch: "androidpublisherv3" | Commit Type: "Minor" | Changes tested: "yes"

* Things upload right now

* In the middle of reworking tracks on supply

* Promote and rollout work pretty well

* promote and rollout are better and obb works

* Meta stuff works now

* Rename AVAIALBLE_TRACKS to DEFAULT_TRACKS, removed deprecated and commented out code

* Moved tracka and releases to constants

* Some typos

* Improved code for not looing at [0] in release_listing

* Cleaned up supply download images to use URI to remove query params

* More description on options

* Updated options

* Applied some changes to setup

* Used fetch_track_and_releases other places

* More cleanup from review

* rubo-ed

* Tests pass I thiiiinnnkkk

* Fix google-cloud-env for less than Ruby 2.4

* Added migration notes

* Cleaned up some code and fixed an supply related action

* Removed is_string from supply

* Need bool

* Improved rollout so :version_code isn't required
@joshdholtz
Copy link
Member

@joshdholtz joshdholtz commented Nov 11, 2019

Last comment! This migration has now been released in 2.135.0 😊 Please create any new issues and mentioned me in them if you have any issues 🙏 Thanks again for all the patience! ❤️

Loading

@joshdholtz joshdholtz unpinned this issue Nov 11, 2019
@fastlane-bot
Copy link

@fastlane-bot fastlane-bot commented Nov 11, 2019

The pull request #15269 that closed this issue was merged and released as part of fastlane 2.135.0 🚀
Please let us know if the functionality works as expected as a reply here. If it does not, please open a new issue. Thanks!

Loading

@Saifullah6
Copy link

@Saifullah6 Saifullah6 commented Nov 21, 2019

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!

Hi i have same problem i don't know how to resolve the problem could you resolve please
ACTION REQUIRED: Your automated publishing to Google Play will stop working on 1 December 2019

Your app is using an old version of the Google Play Developer API. From 1 December 2019, versions 1 and 2 of this API will no longer be available, and any calls to these versions will fail. Update to version 3 before this date

Loading

@wman1980
Copy link

@wman1980 wman1980 commented Nov 21, 2019

@Saifullah6 if you are using Fastlane to deploy your App to Goople Play Store just update your Fastlane to latest version 2.136.0 and deploy your app again with Fastlane. The issue should be gone then otherwise its something else within your app.

Loading

@Saifullah6
Copy link

@Saifullah6 Saifullah6 commented Nov 21, 2019

@wman1980 Thank You
but i dont use Fastlane
i don't know what is the problem
here is the link details
https://android-developers.googleblog.com/2019/03/changes-to-google-play-developer-api.html

Loading

@mieliespoor
Copy link

@mieliespoor mieliespoor commented Nov 21, 2019

@Saifullah6 if you don't use fastlane, then this is not the place to get your issue resolved. You can follow the instructions in the link you posted to get your integrations using the latest version of the api, or you can start using fastlane.

Loading

@claudioviola
Copy link

@claudioviola claudioviola commented Nov 21, 2019

Hey @joshdholtz
I updated to fastlane-2.135.0 but I still see the warning message in the Google Play Console Page

Look at my build log here
Schermata 2019-11-21 alle 18 43 41
Schermata 2019-11-21 alle 18 44 08
Schermata 2019-11-21 alle 18 45 57

This my simple supply

supply(
   package_name: 'my.app.package',
   track: "assembleRelease",
   apk: "#{lane_context[SharedValues::GRADLE_APK_OUTPUT_PATH]}"
)

Can I provide any other staff to help for understanding if I made a mistake?

Many thanks

Loading

@freewil
Copy link

@freewil freewil commented Nov 21, 2019

@claudioviola If you click the Learn more link in the warning banner I believe it explains what you are seeing: the banner warning appears if the old api has been used at all in last 7 days, so it may be outdated relative to current state

Loading

@janpio
Copy link
Member

@janpio janpio commented Nov 23, 2019

Also please open a new issue for your problem instead of posting in a closed issue - then we can properly investigate and possibly help.

Loading

@Saifullah6
Copy link

@Saifullah6 Saifullah6 commented Nov 24, 2019

Also please open a new issue for your problem instead of posting in a closed issue - then we can properly investigate and possibly help.

Thank You @janpio

I don't know how to update version 3
and tomuch spend time on google for searching the solution but did not get any solution

ACTION REQUIRED: Your automated publishing to Google Play will stop working on 1 December 2019
Your app is using an old version of the Google Play Developer API. From 1 December 2019, versions 1 and 2 of this API will no longer be available, and any calls to these versions will fail. Update to version 3 before this date.

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

Loading

@fastlane fastlane locked as resolved and limited conversation to collaborators Nov 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.