cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-10600) 'cordova run android --release' does not use signed and zip-aligned version of APK
Date Mon, 14 Mar 2016 17:35:33 GMT

    [ https://issues.apache.org/jira/browse/CB-10600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193707#comment-15193707
] 

ASF GitHub Bot commented on CB-10600:
-------------------------------------

Github user dpolivy commented on the pull request:

    https://github.com/apache/cordova-android/pull/273#issuecomment-196426128
  
    @daserge Thanks for looking at this. What's the exact cmd line you're using that generates
that error? Is that due to the change I made? It seems like in that case the signing is not
happening, so the unsigned build isn't being picked up, but I don't think the unsigned build
will run anyways so you're right the error message should probably change to reflect the need
to sign. Do you want me to update this PR with that change or do you want to handle it separately?


> 'cordova run android --release' does not use signed and zip-aligned version of APK
> ----------------------------------------------------------------------------------
>
>                 Key: CB-10600
>                 URL: https://issues.apache.org/jira/browse/CB-10600
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>         Environment: Tested on Windows 8.1 with Cordova CLI 6.0.0 (and Ionic CLI 1.7.14)
>            Reporter: Eric Gopak
>            Assignee: Joe Bowser
>            Priority: Minor
>              Labels: triaged
>
> Running command `cordova run android --release` builds the app successfully, both unsigned
and signed/zip-aligned versions. However, it then tries to use the unsigned version of the
APK. Here are the last lines of the output:
> .....
> BUILD SUCCESSFUL
> Total time: 31.35 secs
> Built the following apk(s):
>         C:/XXXXX/platforms/android/build/outputs/apk/android-armv7-release-unsigned.apk
>         C:/XXXXX/platforms/android/build/outputs/apk/android-armv7-release.apk
> Using apk: C:/XXXXX/platforms/android/build/outputs/apk/android-armv7-release-unsigned.apk
> ERROR running one or more of the platforms: Failed to install apk to device: pkg: /data/local/tmp/android-armv7-release-unsigned.apk
> Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
> You may not have the required environment or OS to run this project
> It has worked before I updated Cordova with 'npm install -g cordova'.
> I specify signing properties in a file 'release-signing.properties', which I copy to
platforms/android/ folder. During the run/build I get prompted for the password, just as it
has always been.
> I believe it is just a problem of choosing the wrong APK from the list of built APKs
(Cordova probably chooses the one that comes earlier lexicographically)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message