Yes! The paths are OK!
So, I don't understand why this difference:
My Project *.lpi
<CustomOptions Value="-Xd -CfSoft -CpARMV7A -XParm-linux-androideabi- -FDC:\android\ndkr18b\toolchains\arm-linux-androideabi-4.9\prebuilt\windows-x86_64\bin"/>
Your Project *.lpi don't have "-FDC:...........", why? weird ....
<CustomOptions Value="-Xd -CfVFPv3 -CpARMV7A -XParm-linux-androideabi-"/>
Maybe if you click OK in the "Setting Paths" can solve this issue...
My premise is the radio "NDK Version" don't was captured....
I clicked on OK and now you can see the line
-FDC:\android\ndkr18b\toolchains\arm-linux-androideabi-4.9\prebuilt\windows-x86_64\bin" in the .lpi file.
Unfortunately, this does not solve the problem.
So, the file
gradle-local-apksigner.bat can create the two release unsigned .apk files without any problems but it is unable to create the release signed one.
This means that the problem could reside in the following line:
apksigner sign --ks newapp-release.keystore --ks-pass pass:123456 --key-pass pass:123456 --out C:\LAMWProjects\newapp\build\outputs\apk\release\newapp-release.apk C:\LAMWProjects\newapp\build\outputs\apk\release\newapp-armeabi-v7a-release-unsigned-aligned.apk
Please note that, if the app is built in Ant, the signed release .apk is created correctly.
The problem could also reside in the file
newapp-release.keystore which is created by executing
release-keystore.bat.
My conclusion: what I need to do now is detect all of the files that come into play when
release-keystore.bat and
gradle-local-apksigner.bat are executed. This is because I can do everything with LAMW on my PC except sign a Gradle .apk. Presumably, the files used by
release-keystore.bat and
gradle-local-apksigner.bat are either missing or "outdated" on my computer so I need to reinstall them.
To jmpessoa:
do you know which files are called by the two .bat files to sign the .apk?