Bug with Crosswalk build and thirdparty plugins

[Jonatan_B_]

Hi

I believe I have found a bug when having third-party plugins and doing a crosswalk build. After following the documentation (https://software.intel.com/sites/default/files/managed/9a/72/Intel_Walkthrough_GP-Multiple_APK_Submissions.pdf) I get the following error in Google play:

This configuration cannot be published for the following reason(s):

• Version 20007 is not served to any device configuration: all devices that might receive version 20007 would receive version 60007.

If I look at the APK info for the 60007 version it says: 
Native platforms: armeabi, armeabi-v7a, x86

As I understand it that apk should just be for x86 so that all other devices get version 20007 instead. Acording to http://developer.android.com/google/play/publishing/multiple-apks.html the check is made by: "This is based on the native libraries included in each APK". When I open up my x86 apk there are folders for armeabi, armeabi-v7a and x86 under the "lib" folder. The "x86" folder contains "libxwalkcore.so" (which I assume is for crosswalk) and two other .so files which are my plugins. The other two folders just contain the two .so files for the plugins.

So the build system is including folders for armeabi, armeabi-v7a under the lib folder for the x86 build which is wrong.

This is a show stopper for me and I don't really know how to get around it since the apk is signed by the build system so I cannot manually delete the folders. Any solutions would be very welcome.

/Jonatan

[PaulF_IntelCorp]

This is a known issue that is caused by third-party plugins that include native code. As you pointed out, when you inspect the APKs there are x86 and ARM binaries for one of your third-party plugins, but only the respective architecture for the Crosswalk library binaries (the libxwalkcore.so file). Our build system needs to strip the unwanted binaries from the third-party plugins to fix this issue, and is not doing that at this time (a bug has already been filed to address this issue).

One workaround is to build unsigned, remove the binaries from the APKs and then sign locally. If you have already submitted something to the store that was signed by the XDK build system, you'll have to request your signing cert via html5tools@intel.com. BTW, we are adding a feature to allow you to submit your own certs, not sure when that will become available.

The other workaround is to use the "shared model" build, which creates a single architecture-agnostic APK, but requires that your users download and install the Crosswalk library (they will be prompted when your app first starts). See this doc for more details: https://software.intel.com/en-us/xdk/docs/choosing-crosswalk-build-options-shared-or-embedded

What plugins are you using? I've seen this with the SQLite plugin. Are you using that one or another?

[Jonatan_B_]

Paul Fischer (Intel) wrote:

...

What plugins are you using? I've seen this with the SQLite plugin. Are you using that one or another?

ZBar and SocialSharing.

[PaulF_IntelCorp]

ZBar appears to be the reason why, I'm assuming you're referencing this repo, see the binary bits that are part of the Android implementation: https://github.com/tjwoon/csZBar/tree/master/android/libs

[Jonatan_B_]

I emailed a request to get my signing certificate two weeks ago. I got asked for extra information last tuesday and I am still waiting for the certificates... 

[Pamela_H_Intel]

Jonatan - it looks like the signing cert was sent to you. You will now be able to resolve the code issue.

[Nick_B_2]

I am having the same issue that Jonatan was having. However, how to I remove the binaries from the APK? Or is there another solution to this problem now? 

[PaulF_IntelCorp]

@Nick -- this issue should be resolved. Are you still seeing it?