How to share an .apk without having a Google developer account lazarus / 43-Android ---------------------------------------------------------------------- pasquale · 2021-01-07 11:17 Hello, everybody. I've managed to install LAMW on my Windows PC and create an .apk package with a simple "Hello World" app. I'm using BlueStacks as an Android emulator. I still don't have a Google developer account, because I think it is not free and probably I will never be able to develop commercial apps for Android. Please consider that I don't have any experience with Android and I don't know much about the prerequisites for your apps to be compatible with current smartphones. Attached you will find some screenshots showing you what the characteristics of my "Hello World" app are. I have a couple of questions I would like to ask you: (1) Is it possible to share my app with someone else even though it is not signed with a Google developer account? If it is, how can I allow my friend to download the unsigned .apk package? (2) Considering the characteristics of my .apk package (Apk Builder: Ant, Ndk Api: 22, Min Device Api: 14, Target Api: 28, Architecture: ARMv7a+VFPv3), what is the percentage of current smartphones that would be able to run it if it were properly signed? Moreover, would my app be accepted by Google Play (I don't even know whether it is 32 or 64-bit) if I created a Google developer account? Thanks in advance. ---------------------------------------------------------------------- jmpessoa · 2021-01-07 12:27 Congratulations!!! (1) Yes.  Copy your *.apk from your project folder (/bin  for Ant  or /build for Gradle) to your device (or other) "Download" folder and "click it" the system will try to install the new apk...  (maybe you will need change some device config to permit to install the App from "unknown" source...) (2) "what is the percentage?":  Possibly all!         "ARMv7a+VFPv3"  is 32 bits!       "would my app be accepted by Google Play?": Yes!        But, Possibly you will need to generate the 64 bits, too!         LAWM can help you: go to menu "Project Options" -> [LAMW]... -> "Build"       (but, before you need prepare your Lazarus to generate a "arch64"  .so library) PS. Use the components properties "Anchor", "PosRelativeToAnchor" and "PosRelativeToParent" to layout your component... (Example:   PosRelativeToParent = [rpTop,rpCenterHorizontal])   will mimic your form designer.... ---------------------------------------------------------------------- pasquale · 2021-01-07 14:12 Thank you very much indeed, jmpessoa. You have been very helpful. If I understand correctly, Google Play asks you to produce two versions of your app, a 32-bit one and a 64-bit one, otherwise it will not be accepted on the Play Store. I tried compiling my .apk after setting Chipset=Aarch64 in the Build window (see attachment). Before recompiling, I changed the message in the click event of the button. I received no error message when I compiled the new .apk. Nevertheless, when I installed it, I realized it was the previous package, so the changes I had made were not included in it. Do I have to erase something manually before recompiling the .apk? Thanks again. ---------------------------------------------------------------------- pasquale · 2021-01-07 15:58 Could it be a cache problem within LAMW? If so, how can I erase the cache contents? Basically, after compiling the .apk the first time, whenever I compile it again the .apk does not change. I'm sure I'm missing something elementary, but I don't know what. ---------------------------------------------------------------------- jmpessoa · 2021-01-07 18:39 QuoteGoogle Play asks you to produce two versions of your app, a 32-bit one and a 64-bit No. Only one! After you generate the 32 and the 64 bits  *.so library  ("Project Options" -> [LAMW]... -> "Build") LAMW will package  all in an unique Apk.. QuoteI tried compiling my .apk after setting Chipset=Aarch64  ... Do you haver a Lazarus/FPC prepared to generate a "arch64"  .so library ??? QuoteDo I have to erase something manually before recompiling the .apk? No. But you need compile the same app layout for 32 and 64 bits.... In fact only one will be installed in your device .... (old devices are 32bits....) ---------------------------------------------------------------------- pasquale · 2021-01-07 18:46 Quote from: jmpessoa on January 07, 2021, 07:39:02 pmQuoteGoogle Play asks you to produce two versions of your app, a 32-bit one and a 64-bit No. Only one! After you generate the 32 and the 64 bits  *.so library  ("Project Options" -> [LAMW]... -> "Build") LAMW will package  all in an unique Apk.. QuoteI tried compiling my .apk after setting Chipset=Aarch64  ... Do you haver a Lazarus/FPC prepared to generate a "arch64"  .so library ??? I did nothing to have my Lazarus/FPC prepared to generate a "arch64"  .so library. I just set Chipset=Aarch64 in the Build window and then I created the .apk file. Please consider that I installed LAMW using LAMW MANAGER (which took a couple of hours). Probably the Manager also made the installation ready for arch64. Just guessing. Why can't I compile a second .apk? ---------------------------------------------------------------------- jmpessoa · 2021-01-07 19:59 QuotePlease consider that I installed LAMW using LAMW MANAGER... Great! Yes,  LAMW MANAGER install 32bits (ARMv7a+VFPv3) and arch64! QuoteWhy can't I compile a second .apk? In the same project there is not a second  .apk. (LAMW will pack the 32 and 64 bits in the same .apk) Maybe, you need some "Run" --> "Clean up and Build..."  before "Run" --> "[LAMW] Build Android Apk and Run" ---------------------------------------------------------------------- pasquale · 2021-01-07 20:54 Quote from: jmpessoa on January 07, 2021, 08:59:02 pmQuotePlease consider that I installed LAMW using LAMW MANAGER... Great! Yes,  LAMW MANAGER install 32bits (ARMv7a+VFPv3) and arch64! QuoteWhy can't I compile a second .apk? In the same project there is not a second  .apk. (LAMW will pack the 32 and 64 bits in the same .apk) Maybe, you need some "Run" --> "Clean up and Build..."  before "Run" --> "[LAMW] Build Android Apk and Run" Thanks a lot. I was able to solve my problem following your advice: I just compiled my .apk twice in a row (32-bit and 64-bit) and the resulting package was created correctly. Thanks again. ---------------------------------------------------------------------- jmpessoa · 2021-01-07 21:14 Great! just an advice: use "Gradle" and "AppCompat" themes for more professional APPs.. and update the Android SDK to Api 29 .... ---------------------------------------------------------------------- Remy Lebeau · 2021-01-07 22:23 Quote from: jmpessoa on January 07, 2021, 07:39:02 pmAfter you generate the 32 and the 64 bits  *.so library  ("Project Options" -> [LAMW]... -> "Build") LAMW will package  all in an unique Apk.. Note that later this year, Google Play will start requiring apps to be published using App Bundles instead of APKs, and target API level 30.  See New Android App Bundle and target API level requirements in 2021 for details. ---------------------------------------------------------------------- jmpessoa · 2021-01-08 01:48 Thanks Remy! We will improve LAMW to support  "App Bundles" format and API 30, coming soon! Until there someone can try some help from LAMW .../Docs: "How to Sign apk or bundle using gradle by ADiV.txt" ref. https://github.com/jmpessoa/lazandroidmodulewizard/blob/master/docs/Ho w%20to%20Sign%20apk%20or%20bundle%20using%20gradle%20by%20ADiV.txt ---------------------------------------------------------------------- pasquale · 2021-01-08 07:00 Quote from: jmpessoa on January 07, 2021, 10:14:20 pmGreat! just an advice: use "Gradle" and "AppCompat" themes for more professional APPs.. and update the Android SDK to Api 29 .... I certainly will, thank you. ---------------------------------------------------------------------- pasquale · 2021-01-08 07:21 Quote from: jmpessoa on January 08, 2021, 02:48:43 amThanks Remy! We will improve LAMW to support  "App Bundles" format and API 30, coming soon! Until there someone can try some help from LAMW .../Docs: "How to Sign apk or bundle using gradle by ADiV.txt" ref. https://github.com/jmpessoa/lazandroidmodulewizard/blob/master/docs/Ho w%20to%20Sign%20apk%20or%20bundle%20using%20gradle%20by%20ADiV.txt It looks like Gradle prevents me from building .apk packages (see attached screenshot). Do you know how I can fix it? Thanks. ---------------------------------------------------------------------- Segator · 2021-01-08 13:28 QuoteNote that later this year, Google Play will start requiring apps to be published using App Bundles instead of APKs, and target API level 30.  See New Android App Bundle and target API level requirements in 2021 for details. Google is trying to make us more and more depending of it, exits other App stores, like F-Droid. ---------------------------------------------------------------------- jmpessoa · 2021-01-08 13:46 QuoteWhat went error: Could not determine java version from 15.0.1 what about yours java foders?  something like that?    (My System) C:\Program Files\Java\jdk1.8.0_151 C:\Program Files\Java\jre1.8.0_151 Edited: From here: https://docs.gradle.org/6.0/release-notes.html QuoteCompatibility Notes A Java version between 8 and 13 is required to execute Gradle. Java 14 and later versions are not yet supported. ---------------------------------------------------------------------- pasquale · 2021-01-08 16:18 Quote from: jmpessoa on January 08, 2021, 02:46:57 pmQuoteWhat went error: Could not determine java version from 15.0.1 what about yours java foders?  something like that?    (My System) C:\Program Files\Java\jdk1.8.0_151 C:\Program Files\Java\jre1.8.0_151 Edited: From here: https://docs.gradle.org/6.0/release-notes.html QuoteCompatibility Notes A Java version between 8 and 13 is required to execute Gradle. Java 14 and later versions are not yet supported. I reinstalled Java and then I was able to build my .apk with Gradle and Arch64. Nevertheless, I only get 2 unsigned .apks (debug and release) which do not run in the emulator. Specifically, when I try to install these unsigned .apks, I get the following error message: INSTALL_PARSE_NO_CERTIFICATES So, when I use Ant, I manage to create and run a release version .apk (whose name does not contain "unsigned"), whereas the release version .apk built with Gradle (which contains the word "unsigned" in its name) cannot be run. Am I missing something? ---------------------------------------------------------------------- jmpessoa · 2021-01-08 20:37 You can try delete/uninstall your App from the device/emulator before try a new install... [and If you are using emulator then reset it...] ---------------------------------------------------------------------- pasquale · 2021-01-08 21:11 Quote from: jmpessoa on January 08, 2021, 09:37:05 pmYou can try delete/uninstall your App from the device/emulator before try a new install... [and If you are using emulator then reset it...] I don't think it depends on the emulator. It must be an issue dealing with signing the .apk. Attached you can see some significant screenshots. ---------------------------------------------------------------------- jmpessoa · 2021-01-09 01:49 QuoteIt must be an issue dealing with signing the .apk. Many different install can generate the conflict ... Uninstall the *.apk and re-install again... Please, update your gradle to 6.6.1  https://gradle.org/next-steps/?version=6.6.1&format=bin    Simply "extract here" the zip file to produce the folder "gradle-6.6.1" in a convenient location... and  then update the new path in "LAMW.ini" file (menu "Tools" --> [LAMW]....  --> "Paths and Settings ....") ---------------------------------------------------------------------- pasquale · 2021-01-09 09:23 Quote from: jmpessoa on January 09, 2021, 02:49:32 amQuoteIt must be an issue dealing with signing the .apk. Many different install can generate the conflict ... Uninstall the *.apk and re-install again... Please, update your gradle to 6.6.1  https://gradle.org/next-steps/?version=6.6.1&format=bin    Simply "extract here" the zip file to produce the folder "gradle-6.6.1" in a convenient location... and  then update the new path in "LAMW.ini" file (menu "Tools" --> [LAMW]....  --> "Paths and Settings ....") Thanks. I have upgraded Gradle to 6.6.1 successfully. The .apk is built regularly in Lazarus but I am still unable to install and run it in the emulators (I'm using two different ones: BlueStacks and Nox). In the instructions to sign the .apk (How to get your signed release Apk), I can read: warning: you need a google developer account! I still don't have a Google developer account. Is this the reason why I can't sign the .apk properly? What if I don't want to publish it on Google Play but on a different store? I have seen there are some free of charge. When I execute gradle-local-apksigner.bat, the final line in the DOS window reads the following: Keystore password for signer #1: (see screenshot 1) What does it mean? I'm unable to type anything in the DOS window, except for the Enter key which closes  the window itself. The only .apk file I get is the one you can see in screenshot 2. So, to sum up, that's what I do to try to build my .apk: (1) I set Apk Builder=Gradle and Chipset = Aarch64 (2) I save my project and click on [LAMW] Build Android Apk and Run (the .apk is built whithout any error message) (3) I close Lazarus, open my project folder, insert my personal data in keytool_input.txt (leaving 123456 as I don't have a Google developer account password) (4) I execute release-keystore.bat first, and then gradle-local- apksigner.bat. When I execute the latter, I get what you can see in screenshot 1. The .apk file that I get is the one you can see in screenshot 2. Shouldn't I get an .apk file named myappname-release.apk? That's what I get when I create my .apk using Ant (with Ant everything goes smoothly). If I try to install the unsigned .apk in the emulator, I get the error message you can see in screenshot 3. What am I doing wrong? Thank you very much for your help. ---------------------------------------------------------------------- pasquale · 2021-01-09 10:42 As Gradle is driving me crazy, I was wondering if using Ant (with which I seem to have no problems) will allow me to develop .apk files compatible with the new requirements that Google is going to impose by the end of this year. I'm referring to the creation of bundles that will replace the current distribution method for Android apps. In other words, will it be possible to create bundles containing .apk files developed with Ant? Is Ant deprecated? Thanks ---------------------------------------------------------------------- pasquale · 2021-01-09 10:47 Quote from: Segator on January 08, 2021, 02:28:11 pmQuoteNote that later this year, Google Play will start requiring apps to be published using App Bundles instead of APKs, and target API level 30.  See New Android App Bundle and target API level requirements in 2021 for details. Google is trying to make us more and more depending of it, exits other App stores, like F-Droid. Do you still need a Google developer account if you want to publish your apps on alternative Android app stores? Can you sign your apps in any way other than having a Google developer account? ---------------------------------------------------------------------- Segator · 2021-01-09 15:31 Quote Do you still need a Google developer account if you want to publish your apps on alternative Android app stores? Can you sign your apps in any way other than having a Google developer account? No you not need a Google account, but at least you need to sign your app and google account is not needed for that. ---------------------------------------------------------------------- pasquale · 2021-01-09 15:37 Quote from: Segator on January 09, 2021, 04:31:51 pmQuote Do you still need a Google developer account if you want to publish your apps on alternative Android app stores? Can you sign your apps in any way other than having a Google developer account? No you not need a Google account, but at least you need to sign your app and google account is not needed for that. Thank you very much for your reply. Unfortunately, I'm new to Android and I'm a bit confused about the meaning of "signing your app", in the sense that I don't know how Android signatures work. Do you need to buy a digital certificate to sign your apps in the same way as for MS Windows apps? Or can it be done free of charge? Any help would be greatly appreciated. ---------------------------------------------------------------------- jmpessoa · 2021-01-09 16:18 QuoteAs Gradle is driving me crazy... No. Gradle work for you very well! You got a "debug" and an  "unsigned release"   *.apk  and that is all!  "signing your app" is another task... ---------------------------------------------------------------------- pasquale · 2021-01-09 16:43 Quote from: jmpessoa on January 09, 2021, 05:18:05 pmQuoteAs Gradle is driving me crazy... No. Gradle work for you very well! You got a "debug" and an  "unsigned release"   *.apk  and that is all!  "signing your app" is another task... Thanks, I find your words very encouraging. It is now crystal clear to me that what I need to do is understand what signing an app consists of. As you probably know, Amazon allows you to publish your Android apps on its portal free of charge. For testing purposes, I opened an account on the Amazon developer section and uploaded my "Hello World" Android app (developed in Ant) just to see whether it would be refused or not. To my surprise, the final response was positive: my app was considered technically fit for publication (see attachment). I still don't understand how it was possible to accept my app considering that, for my signature, I used "123456" as a password and that I edited keytool_input.txt manually in which I typed my personal data (I could have invented it!). It looks like the method I used to sign my Ant app was correct. In fact, my Ant app can be played in the emulator without any problems. The same method does not seem to work with a Gradle app though. So my question is, what must I do to sign a Gradle app correctly? TIA ---------------------------------------------------------------------- jmpessoa · 2021-01-09 18:02 QuoteSo my question is, what must I do to sign a Gradle app correctly? from: https://github.com/jmpessoa/lazandroidmodulewizard/blob/master/docs/Ho w_To_Get_Your_Signed_Release_Apk.txt QuoteTutorial: How to get your signed release Apk           warning: you need a google developer account! 1)Edit/change the project file "keytool_input.txt" to representative information:" .Your  google account keystore password: 123456 .Re-enter/confirm the keystore password: 123456 .Your first and last name: MyFirstName MyLastName .Your Organizational unit: MyDevelopmentUnit .Your Organization name: MyCompany .Your City or Locality: MyCity .Your State or Province: MT .The two-letter country code: BR .All correct: y .Your key password for this Apk alias-key: 123456 2)If you are using "Ant" then edit/change "ant.properties" according, too! 3) Execute the [project] command "release-keystore.bat" or "release- keystore.sh" or "release-keystore-macos.sh" to get the "appniceproject1-release.keystore"             warning: the file "appniceproject1-release.keystore" should be created only once [per application] otherwise it will fail! 4 [Gradle]: execute the [project] command "gradle-local-apksigner.bat" [or .sh] to get the [release] signed Apk! (thanks to TR3E!)             hint: look for [project] folder "...\build\outputs\apk\release" 4 [Ant]: execute the [project] command "ant-build-release.bat" [.sh] to get the [release] signed Apk!"          hint: look for [project] folder "...\bin" Success! You can now upload your nice "AppNiceProject1-release.apk" to "Google Play" store! ---------------------------------------------------------------------- pasquale · 2021-01-09 19:01 Quote from: jmpessoa on January 09, 2021, 07:02:09 pm QuoteSo my question is, what must I do to sign a Gradle app correctly? from: https://github.com/jmpessoa/lazandroidmodulewizard/blob/master/docs/Ho w_To_Get_Your_Signed_Release_Apk.txt Thanks. Those directions are also contained in the app folder (file How_To_Get_Your_Signed_Release_Apk.txt). I have been trying to stick to them since my first attempt, but so far I've had no luck. I am clearly missing something elementary. Please find attached the screen I get when I try to create the release .apk. There are a couple of errors (unable to open... + Keystore password for signer #1 - Which password?) that I can't explain. TIA ---------------------------------------------------------------------- jmpessoa · 2021-01-09 19:43 from your print : QuoteUnable to open.... What about? ---------------------------------------------------------------------- pasquale · 2021-01-09 20:22 Quote from: jmpessoa on January 09, 2021, 08:43:07 pm from your print : QuoteUnable to open.... What about? Unable to open 'C:\LAMWProjects\Chiara\build\outputs\apk\release\Chiara-release- unsigned.apk' as zip archive (you can see it in the screenshot). Moreover, Chiara-release.apk was never created (I couldn't find it anywhere). 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." Question: how do I sign my Gradle app without a Google account? Is the password "123456" okay to sign my .apk? ---------------------------------------------------------------------- jmpessoa · 2021-01-09 20:28 QuoteUnable to open 'C:\LAMWProjects\Chiara\build\outputs\apk\release\Chiara-release- unsigned.apk' as zip archive (you can see it in the screenshot). But the "Chiara-release-unsigned.apk" can be find in this path? ---------------------------------------------------------------------- pasquale · 2021-01-09 20:46 Quote from: jmpessoa on January 09, 2021, 09:28:57 pm QuoteUnable to open 'C:\LAMWProjects\Chiara\build\outputs\apk\release\Chiara-release- unsigned.apk' as zip archive (you can see it in the screenshot). But the "Chiara-release-unsigned.apk" can be find in this path? No, you can't. What you find is Chiara-arm64-v8a-release-unsigned.apk ---------------------------------------------------------------------- jmpessoa · 2021-01-10 01:23 QuoteNo, 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!!! ---------------------------------------------------------------------- pasquale · 2021-01-10 10:42 Quote from: jmpessoa on January 10, 2021, 02:23:00 amQuoteNo, 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. ---------------------------------------------------------------------- jmpessoa · 2021-01-10 18:31 QuoteIn 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." Hello @segator! Can you help us? ---------------------------------------------------------------------- jmpessoa · 2021-01-10 20:04 I got some solution!! Please, wait.... ---------------------------------------------------------------------- Segator · 2021-01-11 03:20 to sign your app offline and with out Google account you must generate a key file: ( Windows only): 1- step cmd Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i  cd C:\Program Files\Java\jdk1.7.0_05\bin 2-step Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i  keytool -list -v -keystore C:\Users\yourusername\Desktop\test.jks 3-step type a password for the key store and copy the SH1 key, thos SH1 key is needed for the other app stores and with the test.jks file you can follow the signs step in the project path to put the correct data in the gradle.properties file ---------------------------------------------------------------------- jmpessoa · 2021-01-11 04:51 SOLVED!!! 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!!! ---------------------------------------------------------------------- pasquale · 2021-01-11 16:55 Quote from: Segator on January 11, 2021, 04:20:10 amto sign your app offline and with out Google account you must generate a key file: ( Windows only): 1- step cmd Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i  cd C:\Program Files\Java\jdk1.7.0_05\bin 2-step Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i  keytool -list -v -keystore C:\Users\yourusername\Desktop\test.jks 3-step type a password for the key store and copy the SH1 key, thos SH1 key is needed for the other app stores and with the test.jks file you can follow the signs step in the project path to put the correct data in the gradle.properties file It's so damn hard. I'll give up. ---------------------------------------------------------------------- Segator · 2021-01-11 23:07 Don't worry @jmpessoa now implement it in lamw, just update it an lamw make the job for you. ---------------------------------------------------------------------- rsu333 · 2021-01-17 06:42 Amazon appstore is best way to publish app instead of play store ---------------------------------------------------------------------- pasquale · 2021-01-17 10:46 Quote from: rsu333 on January 17, 2021, 07:42:36 amAmazon appstore is best way to publish app instead of play store Why do you think so? ---------------------------------------------------------------------- rsu333 · 2021-01-18 12:33 First , it is easy .No need of key ,release debug etc. Sec. it is free  and fast. ---------------------------------------------------------------------- pasquale · 2021-01-19 14:46 Quote from: rsu333 on January 18, 2021, 01:33:37 pmFirst , it is easy .No need of key ,release debug etc. Sec. it is free  and fast. Thanks for your reply. What I find very interesting is the fact that, as you said, if you publish your apps on the Amazon App Store, you don't need to care about anything like key, release, debug. What do you mean exactly? Suppose you create a release .apk with Laz4Android using a generic key (123456). Can it be uploaded to the Amazon App Store? What will happen when users download the .apk? Will they be able to install it on their Android smartphones without getting any error messages? Any help will be appreciated. ---------------------------------------------------------------------- rsu333 · 2021-01-20 14:30 Yes, you are right ,I have recently upload  an  apk without any problem but now tester report ,it is not run. Actually I have tested it local 5 devices [with whatsup file sending method] with run properly.   I hope only LAMW creator [jmpessoa] guide or solve this problem.