May be not for you! But it is new info for me so I am interested in know as to how does B4A handle generating 32bit (for older version of Android) and 64bit apps (for Android Oreo and higher).
Of it is dependent of which target SDK we have set in the manifest?
i can not answer about 64bit apps. And, as we do have a year to go, i´m not interested in investigating it at this time.
I´m sure there will be a solution for B4A
The 64 bit requirement is only relevant to libraries such as SQLCipher which include native binaries. There are very few such libraries. They will need to be updated to include a 64 bit binary.
Edit: latest version of SQLCipher includes a 64 bit binary.
Here is the link I received today from google describing the new 64-bit requirement on 8/2019, and I just want to make sure that it does NOT apply to B4A apps (and only to "libraries"):
So, just to be clear, if I do NOT use a problematic library (and most of the B4A libraries are NOT problematic), then the B4A compiler already automatically generates APKs that will meet Google's 64-bit requirement on 8/19?
I dont know. I did not wote b4a and for me it is not 2021 and there is as of today no need for 64 bit.
And based on Erels answer i do not expect any problem.
So, just to be clear, if I do NOT use a problematic library (and most of the B4A libraries are NOT problematic), then the B4A compiler already automatically generates APKs that will meet Google's 64-bit requirement on 8/19?
After reading the article last night, my understanding is that apps written in Java (which B4A apps are converted to before being compiled) are not native apps & are therefore not required to be 64bit.
I dont know. I did not wote b4a and for me it is not 2021 and there is as of today no need for 64 bit.
And based on Erels answer i do not expect any problem.
Native apps that don't include 64bit support won't be able to be uploaded to Play Store (new or updates) from 1 August 2019. Only Unity apps built using v5.6 or older will be allowed until August 2021.
Fyi - native Android apps are built using the Android NDK (https://developer.android.com/ndk/). For B4A developers it seems the only potential issue with the 64bit requirement is any library you might be using that contains native code.
I dont know. I did not wote b4a and for me it is not 2021 and there is as of today no need for 64 bit.
And based on Erels answer i do not expect any problem.
I am confused why you are mentioning 2021 because the article I posted said that all NEW and UPDATED apps posted to the Play Store NEED to include a 64-bit version by Aug of THIS year (2019 - in 6 months).
That was my reason.
Erel mentioned somewhere that it only applies to app using native .so file which needs to include an 64bit native in future.
Only a few libs are problematic so i do not care about. Even if it will be in 6 months. I am using 64bit java on a 64bit Windows 10 PC.
I´m positive that the apks generated by B4A will meet the requirements in 6 Months... Maybe we need a new version with a new compiler. I don´t know. But i´m sure Erel do have plans already.
I have no idea if the 64-bit SDK's requirement mentioned in the new post applies only for third-party SDK's or also apply to the SDK's we download using the SDK manager.
So my post was simply asking if Erel's response is still the same in light of the newer/broader post from Google.
All new apps and app updates that include native code are required to provide 64-bit versions in addition to 32-bit versions when publishing to Google Play.