topic Follow the link to see the in Software Archive

Google play do not accept 2 versions Android

Hamilton_Tenório_da_ — Sat, 13 Jun 2015 12:13:29 GMT

I am trying to publish a new version of an APP, builded with Android Cordova. When I upload the second version the Google Play do not accpet:

It says that the version 20xxx does not apply to any new device. All devices use 60xxx version.

Normally the Google Play accept both. Why here not?

This sounds like you have an

PaulF_IntelCorp — Mon, 15 Jun 2015 19:47:15 GMT

This sounds like you have an APK that does not contain any architecture-specific code?! Did you build with Crosswalk and get two APK files?

Yes, I build as Crosswalk

Hamilton_Tenório_da_ — Mon, 15 Jun 2015 20:36:22 GMT

Yes, I build as Crosswalk Android. I received 2 files (20xxx and 60xxx).

When I publish in Google Play the first one, it is OK. When the second is uploaded, it informs that no device will use the second.

I will try to send some images to best understanding (actually it is not accepting the images here).

Follow the link to see the

Hamilton_Tenório_da_ — Mon, 15 Jun 2015 21:00:20 GMT

Follow the link to see the images about the problem:

https://www.dropbox.com/sh/z69ax4mg3yfxvij/AAC1xZCCg2oQnF-qAwN3oX0la?dl=0

You can see that in both details, in Google Play, all architecture is present.

I tryed sunday (2 times) and today (2 times again) and the result is allways the same.

The dropbox link takes me to

PaulF_IntelCorp — Mon, 15 Jun 2015 21:48:32 GMT

The dropbox link takes me to an empty folder, can't see any images...

Uhn, for me they are there.

Hamilton_Tenório_da_ — Tue, 16 Jun 2015 02:18:30 GMT

Uhn, for me they are there. Can you try again? Maybe the are not syncronized yet.

@Paul

Hamilton_Tenório_da_ — Wed, 17 Jun 2015 14:14:49 GMT

@Paul

Could you see the files? Have any idea?

I tryed yesterday and receive the same error.

Hi Hamilton, now I see the

PaulF_IntelCorp — Wed, 17 Jun 2015 18:15:09 GMT

Hi Hamilton, now I see the images. I'm guessing that the version you have in there with the 60110 label is a regular Android build and not a Crosswalk build. In that case, the store will prefer the higher number version code, which, if it is a standard Android build, will satisfy the ARM architecture, because it is architecture agnostic.

In other words, if my theory is correct, you need to remove the old 60110 APK to get things to work.

If you are not able to remove the old 60110 copy you'll have to change your version codes in your Build Settings. If you set the version code in the build settings to 40111 it should generate a Crosswalk ARM build with version code 60111 and an x86 build with version code 100111.

Hi Paul,

Hamilton_Tenório_da_ — Wed, 17 Jun 2015 22:09:06 GMT

Hi Paul,

No, the version 60110 wal build with Android Crosswalk. But the Google Play only accepted this first file. The second one (20110) was not accepted. It informs that no device will use the second one.

Se in the image attached the list of versions. Until the version 2.0.4 was used the normal Android build. Above that, all the others were uploads of new versions Crosswalk, without success.

Reading the details of version on Google Play panel, both files (20xxx and 60xxx) is set to all devices. Look my last try:

20113 Plataformas nativas arm64-v8a, armeabi, armeabi-v7a, x86, x86_64

60113 Plataformas nativas arm64-v8a, armeabi, armeabi-v7a, x86, x86_64

It seems strange.

I look another APP that I use

Hamilton_Tenório_da_ — Wed, 17 Jun 2015 22:23:54 GMT

I look another APP that I use Crosswalk (ConfirmAki Empresarial), to compare. See:

60004: Plataformas nativas x86
Dispositivos Android compatíveis 240 dispositivos

20004: Plataformas nativas armeabi-v7a
Dispositivos Android compatíveis 8672 dispositivos

Here, the information is according with each file. This publish was at 27/04/2015 04:41:58

There is something wrong with this build (ConfirmAki PRO). Is there any modification on Crosswalk building?

Very odd. Can you share the

PaulF_IntelCorp — Thu, 18 Jun 2015 21:29:42 GMT

Very odd. Can you share the APKs that are getting marked as supporting ARM and x86? You can attach to a private message or put them into a dropbox or similar and send a private message with a link to that download.

Which Crosswalk version did you build for?

Sure. I put in the same link

Hamilton_Tenório_da_ — Thu, 18 Jun 2015 23:28:20 GMT

Sure. I put in the same link above. There are 4 files: 2 (version 3.0.0 builded 06/13/15) and other 2 (version 3.0.3 builded 06/16/15). All of them using Crosswalking 12.

Hi Hamilton, sorry it has

PaulF_IntelCorp — Sat, 20 Jun 2015 00:42:00 GMT

Hi Hamilton, sorry it has taken so long to look at this, I've been extremely busy with lots of non-forum tasks (all of us work only part-time on the forum).

It appears that the SQLite database you are using includes some native code libraries for both x86 and ARM. So I can see why this is happening. Even though each of the APKs contains only a single architecture (ARM or x86) for the Crosswalk library, it contains multiple architecture libraries for the SQLite database. I believe the presence of these other architecture libraries is what is causing the Google store to behave this way.

If we provided a "fat binary" build for Crosswalk, that contained both Crosswalk binaries, it would exceed your APK size limit, so that's not a valid solution. There are two alternatives until we can fix this:

Create an unsigned build (two unsigned APK files) and then remove the "wrong" architecture files from each APK and then manually sign the resulting APK files (this can be done, but requires some manual labor and retrieval of your Android signature from our build system).
Wait for our shared model build option (which will appear very soon, with the next release of the XDK), which will allow you to build a single APK file that works on both architectures. This solution only works (initially) with apps that are distributed via the Google Play store. It will not work (until some future date) with other distribution mechanisms.

The ultimate solution is to have our build system remove the extraneous architecture libraries before signing and sending you the finished APK files. That will take some time to implement, but is something I'm going to request of our engineering group in charge of the build system.

Thank you for your analysis.

Hamilton_Tenório_da_ — Mon, 22 Jun 2015 13:34:38 GMT

Thank you for your analysis. I confirmed that. I changed the plugin (from cordova.sqlite.storage to com.triarc.sqliteplugin) and builded again. It works well.

I don´t remenber well, but I used this plugin before but I need to change because iOS. Now I return to them. They are very similar.