search

gluonhq / gluonfx-gradle-plugin

Plugin that simplifies using Gluon Client for Java/JavaFX gradle projects
BSD 3-Clause "New" or "Revised" License
100 stars 21 forks source link

Could't created apk Android for device armeabi-v7a #151

Open websystemtechnology opened 2 years ago

websystemtechnology commented 2 years ago

I Think it's impossible to create apk for device with ABI armeabi-v7a. I check into the ply store, at moment around the world there are 7K device with ABI aarch64 and 13K of Device with armeabi-v7a. do you tink in the Feature we can create app for armeabi-v7a?

jperedadnr commented 2 years ago

GluonFX plugin relies on GraalVM for creating a native image, and it doesn't have support for 32 bits for any platform so far. As an alternative it is possible to combine two APKs into one bundle, one for each type of arch. For armeabi-v7a you could use the old JavaFXPorts plugin, and for arm64 the GluonFX plugin. It is ugly but so far there are no better options.

websystemtechnology commented 2 years ago

How can I add into the bundle the second apk?

jperedadnr commented 2 years ago

Sorry, I wasn't very clear: Actually you don't bundle them together in one APK, you can upload two APKs to Google Play for the same app but for different architectures. See https://developer.android.com/google/play/publishing/multiple-apks

websystemtechnology commented 2 years ago

First I'll try to generate apk with javafxport to test the upload on the store; then I create aab file, create the new release with this aab file, than I attach to the same release and I receive this error:

Hai caricato un APK con una firma non valida (ulteriori informazioni sulle firme). Errore dello strumento apksigner: ERROR: MIN_SIG_SCHEME_FOR_TARGET_SDK_NOT_MET: Target SDK version 30 requires a minimum of signature scheme v2; the APK is not signed with this or a later signature scheme

I use the same keystore. what I'm wrong?