Google Play 64-bit requirement

Rob, I contacted the support and also filled up the form telling them about our upgrade plans and extension required as the delay will be due to 3rd party i.e. Corona in this regards.

I have got a clear reply saying that it will not be allowed. Only Unity apps with 5.6… and older will get extension for 1 more year.

And just a note for other developers: I first noticed this message in Q3 last year and so it has been there for a long enough.

Rob, do you have an approx date when Corona 64 bit for Android will be ready?

This is critical as some apps might require updates in August due to some unforeseen issues and we will not be able to update anything unless the the support is ready from your side.

The only way Google Play will extend this is if Corona contacts then like Unity and talks about the reason for extension - it will not happen no matter how many developers contact them. I am certain on this.

We need a solution here or else it is going to be difficult - but first you need to let us know the approx dates for this being ready.

thank you, Rajat

I don’t want to come across as mean, but let’s get real.

1) There is no realistic scenario in which Google would grant further extensions to other engines/SDKs.

2) For anyone who has has been following this topic during the past several months should have learned by now that this is a “it’ll be ready when it’s ready”-issue and Rob has been adamant on not throwing any estimates in the air.

3) This has been a serious issue since it was announced and will continue to be so until it has been addressed. Corona Labs and every Android developer knows is and piling on to state that “this is important” or “needs to be solved/fixed” won’t do anything but to add to peoples’ general frustration.

Based on following this topic for months, there’s nothing to do but to wait.

The way this is being handled by Corona is not how a company that has a serious business plan will go about it. I have enough reason to believe they are winding down.

Everyone here understands the implications of not meeting the 64 bit deadline including the corona staff and yet there is absolutely no word of assurance or any ETA even after many months.

https://docs.google.com/forms/d/e/1FAIpQLSfIK3I3MM9LHEBHr74DHgyFYUlfGIz5Zi1mul9V9LJw1Fo4-g/viewform

Google survey

What did you put in under “When do you intend to publish a 64-bit variant of your app”?

I put “I don’t know” - sad but true.

show this post:

https://coronalabs.com/blog/2019/05/28/corona-google-play-apps-and-64-bit/

@XeduR @Spyric

Yes you are right that there is no realistic scenario that Google Play will grant an extension.

And I looked into the Forum post today in detail (my partner generally follows it) and got a feeling that there is no definite answer of when it will be ready.

We need to know when it will be ready - because things have to be planned on a developer’s end - if its 1/2 months, then its a different strategy, but if its 3/4 months and then the strategy changes - and if it is (god forbid) longer than that, then its a nightmare right and may even have to migrate some of the apps. It all depends how big the apps are and how often the critical updates are required - so its different scenario for each developer - for us, we dont have a choice of not upgrading for so long for some of our apps.

I understand all realistic scenarios, and the fact has to be faced - thats all good. Corona team has to mention a date - that is for sure - they cannot keep us in the dark regarding this.

We fully understand the impact of this requirement. We fully understand that you need time to update your apps and we are working at all expedience to get this to you as soon as humanly possible. It’s a huge, huge change to our entire Android build pipeline with many points that need touched along the way.

I can also appreciate your frustration at our refusal to give out dates. But historically when we’ve given dates you have taken them as absolute promises instead of target goals and rip us badly for missing the dates. Continuing to ask for dates is going to continue to get this response.

I will say that Engineering said “It’s going good” a few days ago. I’m confident that will get this done in time. 

Finally, Google has reached out to us, based on your survey responses to see what information they can provide us to get us to help meet the deadline. They can’t create more hours in the day, nor can we expect any engineering resources from them, but we are in contact with them. I doubt they will grant us more time. I don’t see a way they can really help us speed up the process up, but they are listening to you.

Hopefully we will have some news soon!

Rob

Thanks for your replay. You said it is a huge thing for your build process, but what about corona native where builds are done locally? Would it be possible to get corona native up and running first to make sure we have MVP in place? If that would work, in worst case people would just have to build it with corona native which is not that complicated.

Rob, thank you for making us aware, it is very important in this kind of situations where there is a group of people anxious (not to say desperate) to keep a fluent communication and to know the advances, although they are not the most promising, but it is better to be clear the situation no matter how hard it is and so we can anticipate or establish strategies to follow.

I think they can achieve it even if it is not on the deadline, but we know that they are putting all the effort.

Thank you

(Sorry for my awful english) :slight_smile:

Everyone, we need to discuss the 64-bit requirement for plugins - so I created this new thread about it: https://forums.coronalabs.com/topic/75655-google-64-bit-requirement-for-corona-plugins/

Thanks Rob - not an enviable position yours these days.

Keep up the good work, we need you!

In our last blog post on this:  https://coronalabs.com/blog/2019/05/28/corona-google-play-apps-and-64-bit/

“To see our progress, you can check out gradle branch from the open source version of Corona from our GitHub and build a Gradle-based 64-bit version of Corona. We’re working on integrating this build system into Corona Simulator/Native and supporting existing plugins and settings.”

You can download this, build your own version of Corona that produces 64-bit APK builds. This is sort of like a native build. You won’t get to build with the simulator. You won’t be able to use any plugins. But if you’re app doesn’t need plugins you should be able to use this and make 64-bit apps… Let me get Engineering to confirm that.

It sounds like a big part of the challenge are the plugins. Could we in this situation expect to have middle release where only corona itself will be compatible? I have few apps which does not require any plugins at all so that would help me a lot.

I’m not sure what is possible. I know a lot of our backend build process is tied to the plugin system, but switching from ANT to Gradle creates new possibilities that may make plugins on Android, in particular with dependencies, a lot easier to build.

But if you don’t need plugins, there is the option I posted above.

Rob

So does anyone know if this applies to the Amazon App Store?  I’m not so worried if the Amazon store forces 64bit, as I am that the same upcoming 64 build can just be signed for the Amazon store as well.

I haven’t got an email from amazon so nada

Amazon runs a (customised) but old version of Android.  Even the latest devices are only running Android 6.

Let me add a little qualification to that. Amazon Kindle Fire devices are running an open source version of Android that’s a little behind the current shipping version of Android. However Amazon sells non-Kindle Fire devices that will have Android 9 on them. But I’ve not heard anything about Amazon having a 64-bit requirement. That may come with Android 10.