Why does an “ion cord assembly” generate unsigned agribusinesses?

Question

I use the command below to create a signed APK, I'm sure it worked a few months ago:

$ ionic cordova build android --prod --release --keystore="./my-keystore-file.keystore" --storePassword=mypass --alias=[e-mail] --password=mypass

However, only an unsigned APK is generated. How can I generate a signed APK using ionic?

Answer 1

You need to include -- --up to Cordoba's arguments:

$ ionic cordova build android --prod --release -- -- --keystore="./my-keystore-file.keystore" --storePassword=mypass --alias=[e-mail] --password=mypass

The parameters are build android --prod --releaseprocessed by the Ionic CLI, while everything after the first --is passed to the Ionic Cordova plugin. Then everything after the 2nd --is transferred to Cordoba itself.

Answer 2

Publish an ionic Android app.

• Adding a platform to the project.

ionic cordova platform add android

cordova build android --release

3. APK platforms/android/build/outputs/apk. APK.

keytool, JDK.

keytool -genkey -v -keystore <name_of_keystore>.keystore -alias alias_name 
-keyalg RSA -keysize 2048 -validity 10000

keystore. , . . . , !

4. unsigned APK, jarsigner, JDK:

jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore name_of_keystore.keystore path_to_unsigned_apk_file.apk alias_name

, apk root filename.apk .

.

5. , zip align APK

zipalign -v 4 HelloWorld-release-unsigned.apk new_apk_name.apk

HelloWorld.apk, Google Play Store.

: docs