I’m unaware of that being related to 64-bit, but this will be part of the every rolling Google eco-system updates!
Rob
Version 3 of what google API. Do you have a copy/screenshot of the error?
Changes to the Google Play Developer API to V3 :
https://android-developers.googleblog.com/2019/03/changes-to-google-play-developer-api.html
Updating from versions 1 and 2 to the latest version 3:
Version 3 also supports all the functionality of previous versions, improving and simplifying how you manage workflows. Starting December 1, 2019, versions 1 and 2 of the Google Play Developer API will no longer be available so you need to update to version 3 ahead of this date.
What does this have to do with Corona apps? How are you using the API in your apps?
This apparently impacts in-app purchases.
Rob
@Rob this is for managing your play store listings and config. It is not related to actually consuming IAPs.
The Google Play Developer API allows you to perform a number of publishing and app-management tasks. It includes two components:
- The Subscriptions and In-App Purchases API lets you manage in-app purchases and subscriptions.
- The Publishing API lets you upload and publish apps, and perform other publishing-related tasks.
hi,
I do not have in-app purchases integrated in my application and however I’m getting that message to update to API version 3
Hello;
As the name suggests, this API should be used when using Google Play features.
There are no API warnings for apps I’m releasing and not using features.
The current warning is only the one associated with the change of the icon.
In fact, there is one other special warning, but maybe this is another issue and will not be described here.
When/where is the error? Screenshot maybe.
Is this on a new upload, update or general error message?
This discussion seems to be veering away from the 64-bit topic. However, on that topic, now that the Gradle branch on GitHub has been merged into the Master branch, I think it is fair to say that this issue will be resolved soonTM.
I see the Corona.aar archive in the gradle folder containing both 32 and 64 bit libraries (3487). Just wandering when the project template for android native will be updated so we can start testing :).
Here is the latest… As some of you have noticed, there have been a few daily builds hinting at 64-bit builds. We are calling this an early Alpha. If you want to participate in testing this, join the CDN Slack (https://coronalabs.com/slack) and then when there join the #Android64 channel. Read the pinned post and the next post after that.
Rob
Rob, I understand that the work is in early alpha. But Corona not giving us any tentative date is making things very difficult.
A lot of users are saying that they trust and believe in the Corona team - of course, I do the same and that is why we have continued to use it. It is a good platform and the team is great and even better that you guys have been here for long and so there is a continuity (even though the ownership has changed a few times 
But not having a date puts everyone in an impossible situation right. Things might be delayed and that is ok as we cannot do anything about it and there is no complaining or crying over it - that is not what I am trying to do.
But we need some planning and preparing on our end right. If we know that it will be delayed by a month or two, then basically any update we need to do (for various reasons) for the existing apps, we need to do it before end of July as after that, we will have for the time till this Corona 64 bit is ready and we can update or release any app.
Thats all I am asking - a date - so things can be planned.
Now you said, it is very difficult to say an exact date - and then you said if you mention a date then the developers hold you by it. Well, you are not new into development and keeping contingency in mind, you can work out a release date.
Hope you will understand and shed some light on it as we do not have much time left now to update the apps before the deadline.
Thank you.
Hey guys, Rob,
since some other companies have an excuse not to do this (for extra few years) - how does that work?
32-bits will work fine for them, that means they will work for all. Except it will be impossible to upload 32 builds for some publishers.
Is there a way to trick automatic check - to think that it is a 64? If that makes any sence. Like adding some unity stuff inside apk? =)
PS Sorry if this sounds silly =)
There is an error in your post. “, then basically any update we need to do (for various reasons) for the existing apps, we need to do it before end of July”.
But google say: “App will be deleted from google store if is not 64 bit”…
No the apps will exist in 32 bit, but you cannot update and of course cannot upload a new one after Aug 1, 2019 (unless its a 64 bit version)
Read https://android-developers.googleblog.com/2019/01/get-your-apps-ready-for-64-bit.html
I have been very, very clear. We do not provide dates for anything. Please stop asking us for one. Please stop beating us up for not providing one.
The latest build does produce 64-bit Android builds. You however have to do some stuff to enable it. You have to do some manual things to make it work. We thought we had all the plugins under our control converted, but found that some plugins like OpenSSL was still giving errors. It passed our tests, but it didn’t pass a tester’s use of the plugin. This is why we do limited testing (i.e. Alpha) so that we can get feed back and fix it. That plugin was fixed yesterday.
We found out yesterday that there is a new edict from Google that apps also have to target Pie/Android 8 by August too.
I can tell you we are very close to enabling them for the latest daily build. We are very very aware of the deadline and that you need time to update your apps before the deadline and we are working our team very, very hard to give you as much time as we can.
Thank you Rob for your hard work!
Thanks Rob.
Keep up the good work.
I may convert my religion to Robistianity after all this.