No, you can't. What you find is Chiara-arm64-v8a-release-unsigned.apk
Please, change it to "Chiara-release-unsigned.apk" and try again!
We will fix/improve the LAMW scripts!!
Edited:
Done!!!
Please, update the LAMW or simply the file "androidwizard_intf.pas"
ref:
https://github.com/jmpessoa/lazandroidmodulewizard/tree/master/android_wizard
Maybe, using LAMW Manager or some git client or simply copying.... [to LAMW folder ".....\android_wizard"]
Then re-install the "lazandroidwizardpack.lpk" [".....\android_wizard"] before you create a new project!
Hint: Close any LAMW project [and open a default lazarus project] before re-install a LAMW package....
Thank you!!!
Thanks a lot.
I have upgraded my lazandroidwizardpack.lpk following your directions and now I no longer get the error messages in the DOS window.
My Android emulator is now able to run the debug version built with Gradle and ARMv7a+VFPv3.As far as the release version is concerned, I still have to understand what I must do to sign an .apk built with Gradle.
Considering that I don't have a Google developer account, is there any way I can sign my .apk or is it impossible?
Right now, after I execute
gradle-local-apksigner.bat, I can find
myapp-armeabi-v7a-release-unsigned.apk and
myapp-armeabi-v7a-release-unsigned-aligned.apk in the
C:\LAMWProjects\myapp\build\outputs\apk\release folder. There's no file named
myapp-armeabi-v7a-release.apk or the like (I mean, without the word "unsigned" in its name).
In this forum, Segator said: "No you not need a Google account, but at least you need to sign your app and google account is not needed for that."
I just want to remind you that, if I use Ant as an .apk builder, then myapp-release.apk is built correctly (without any Google developer account password) and it can run in the emulator without any problems. Is this only possible with Ant or am I missing something?
Thanks.