[Android] Gradle build failed with signing key

[amirudin]

Build with gradle success if no signing key been specified (debug). It will eventually failed otherwise.

Original report: http://gsfn.us/t/4snxg

[bau720123]

hi all
I am the reporter
hope can solve the issue as soon as possible

[wildabeast]

There are currently issues on Build with plugins that include libraries for both x86 and arm architectures -- specifically the crosswalk plugin in this case. Looking into a fix for this but in the meantime you should source the pgb version of the crosswalk plugin. There's actually two versions of this plugin on build -- one for each architecture (both compile fine both signed and unsigned). The default compiles for arm:

<gap:plugin name="org.crosswalk.engine" version="1.3.0" source="pgb" />

And to build for x86:

<gap:plugin name="org.crosswalk.engine.x86" version="1.3.0" source="pgb" />

Working on better support for the mainline npm crosswalk plugin. Stay tuned.

[bau720123]

hi @wildabeast
I post some information right here
the bottom...
so...which place should I post in the future will help PGB team more Easy to management ?
the "community.phonegap.com/" or "git" ?

[frederikbosch]

+1

[kdmon]

+1

The older PGB plugin version of Crosswalk unfortunately does not support the functionality I require, so reverting to that package is not a solution for me. I need Crosswalk 15 to correctly gain camera access through:

<input type="file" accept="image/*" capture>

See my original posts for details:
http://community.phonegap.com/nitobi/topics/crosswalk-cli-5-2-0-build-issues#reply_16374450

Any idea as to when a fix may be available or alternatively if/when the PGB plugin could be updated to a more recent version of Crosswalk?

Thank you

[frederikbosch]

We have exactly the same problem. Our app cannot be build with an older version of Crosswalk. Only signed builds of the app have the problem.

[kdmon]

As a temporary workaround, I'm looking into whether it is possible to manually sign the debug package outside of phonegap build. I'll keep you posted.

http://developer.android.com/tools/publishing/app-signing.html#signing-manually

[kdmon]

It is possible to manually sign the debug package outside of phonegap build, but the process is rather convoluted and requires several tools.

1. Install jarsigner, apktool and zipalign

   Jarsigner is part of Java, so make sure you have Java JDK installed if you can't find it.

   Apktool is a tool for extracting and building packages. To install it, follow instructions at:
   http://ibotpeaches.github.io/Apktool/install/

   Zipalign is part of the Android SDK. If you're on Linux and don't want to download 300mb+ of the SDK to obtain zipalign, the utility can be found in this github repository:
   https://github.com/aureljared/zipaligner

   For mac users, try this repo: https://github.com/catccaatt/zipalign

2. Extract your debug/unsigned Phonegap Build package

   To sign the package successfully, we need to make changes to some files inside the package. So extract it using apktool:

   apktool d -s name_of_your_package.apk

   This will extract your package into a folder labelled name_of_your_package.

3. Remove the debug flag from AndroidManifest.xml and the debug signature added by Phonegap Build

   Packages built using Phonegap Build without a valid key are set to debuggable. Google Play will not accept debuggable packages.

   Inside the extracted package folder, find the AndroidManifest.xml and delete the attribute Android:debuggable="true" (or set it to false) in the <application> section.

   Then delete the files inside the original/META-INF directory. These files contain the debug signature and prevents us from signing the package with our real keystore certificate.

4. Repackage the app

   apktool b name_of_folder_with_package_files

   This creates a new apk file inside the dist subdirectory of your package directory.

5. Sign the new package with your keystore certificate

   You can add your own signature using:

   jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore name_of_your_keystore_file.keystore name_of_your_package.apk name_of_your_alias

6. Run zipalign

   Finally, optimise the memory profile of your signed package using zipalign, as per the Android developer instructions linked above.

   ./zipalign -v 4 your_signed_package.apk your_aligned_package.apk

Your package should now be accepted by Google Play (I can verify this process works for my own app)

[frederikbosch]

That is great. Thanks for the thorough explanation. Nonetheless, I would like to see bug being fixed! @wildabeast Any news on the progression? We have problems building all our android apps now.

[tonijn]

+1

[dahel]

any news about it?

[goya]

does someone have a recent app id # that can reproduce this issue?

[bau720123]

hi @goya
is you mean my post issue ?
http://community.phonegap.com/nitobi/topics/-cordova-plugin-crosswalk-webview-still-not-work-with-pgb-gradle

<gap:plugin name="cordova-plugin-crosswalk-webview" source="npm" version="1.4.0" />
option1,a keystore file,it will build fail on Android (but I am very sure my keystore file is good to work,because I use it to upload GooglePlay for many times) 
option2,no any ketstore file,it will build success 

if yes，my app id is 697726
and here is the latest log
http://justpaste.it/q9p7
you can search the keyword "crosswalk"

by the way
@wildabeast also can prove this point

[tonijn]

This app id will reproduce the issue
959643

[p-schuler]

Guys, this issue was reported in October. There are several issues with older crosswalk builds and multiple people do run into them. Can we bump the priority on this one? I have the same problem