Return-Path: X-Original-To: apmail-flex-issues-archive@minotaur.apache.org Delivered-To: apmail-flex-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 48ECE17D79 for ; Fri, 1 May 2015 09:19:06 +0000 (UTC) Received: (qmail 98478 invoked by uid 500); 1 May 2015 09:19:06 -0000 Delivered-To: apmail-flex-issues-archive@flex.apache.org Received: (qmail 98451 invoked by uid 500); 1 May 2015 09:19:06 -0000 Mailing-List: contact issues-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list issues@flex.apache.org Received: (qmail 98442 invoked by uid 99); 1 May 2015 09:19:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 May 2015 09:19:06 +0000 Date: Fri, 1 May 2015 09:19:05 +0000 (UTC) From: "ccking (JIRA)" To: issues@flex.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLEX-34829) flex for mobile apk, android 4.3.0 above and below, with a project, with a p12 file, get the sha1 different; MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLEX-34829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ccking updated FLEX-34829: -------------------------- Description: flex for mobile apk, android 4.3.0 above and below, with a project, with a p12 file, get the sha1 different; !http://i4.tietuku.com/a5627ee468bdbd95.png! 4.1.1 !http://i4.tietuku.com/59721d0bd8d578ce.png! 4.3.1 This issue needs to be re-signed apk to resolve. But added a lot of development work; So we hope to get a clear fix to flex development apk, how can a reasonable solution keystore problems; The steps we resolve as follows: 1) Change the extension of your .apk to .zip 2) Open and remove the folder META-INF 3) Change the extension to .apk 4) Use the jarsigner and zipalign with your new keystore. was: flex for mobile apk, android 4.3.0 above and below, with a project, with a p12 file, get the sha1 different; !http://i4.tietuku.com/a5627ee468bdbd95.png! This issue needs to be re-signed apk to resolve. But added a lot of development work; So we hope to get a clear fix to flex development apk, how can a reasonable solution keystore problems; The steps we resolve as follows: 1) Change the extension of your .apk to .zip 2) Open and remove the folder META-INF 3) Change the extension to .apk 4) Use the jarsigner and zipalign with your new keystore. > flex for mobile apk, android 4.3.0 above and below, with a project, with a p12 file, get the sha1 different; > ------------------------------------------------------------------------------------------------------------ > > Key: FLEX-34829 > URL: https://issues.apache.org/jira/browse/FLEX-34829 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Mobile > Environment: android 4.3.0 above and below > Reporter: ccking > > flex for mobile apk, android 4.3.0 above and below, with a project, with a p12 file, get the sha1 different; > !http://i4.tietuku.com/a5627ee468bdbd95.png! > 4.1.1 > !http://i4.tietuku.com/59721d0bd8d578ce.png! > 4.3.1 > This issue needs to be re-signed apk to resolve. > But added a lot of development work; > So we hope to get a clear fix to flex development apk, how can a reasonable solution keystore problems; > The steps we resolve as follows: > 1) Change the extension of your .apk to .zip > 2) Open and remove the folder META-INF > 3) Change the extension to .apk > 4) Use the jarsigner and zipalign with your new keystore. -- This message was sent by Atlassian JIRA (v6.3.4#6332)