[
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!
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://jira.atlassian.com]
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!
> 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)
