Android Market incorrectly reporting device incompatibility after version update

Solar2D General Questions/Discussion
#1

We recently published the first update to one of our apps on the Android Market and immediately afterwards found that the market was reporting several types of devices as incompatible when they were previously compatible.

I believe this to be an Android market issue but am getting the expected run around from support regarding manifests and market filtering. I can prove it because after I suspected what was happening I aborted the upgrade of the paid version of our app. Sure enough the paid version is still showing as compatible on the same devices that are now showing as incompatible.

Needless to say we did not change anything in the manifest.

I am wondering if any other Corona developers are experiencing similar issues, and if so how they resolved them.

If they are unresolved perhaps we can join forces and make enough noise to get noticed by Google. [import]uid: 60648 topic_id: 22880 reply_id: 322880[/import]

#2

Which particular devices? [import]uid: 10389 topic_id: 22880 reply_id: 91385[/import]

#3
  1. Kogan Agora Tablet (MID7007)
  2. HTC Sensation
  3. Samsung Galaxy Ace

Thanks for your help. [import]uid: 60648 topic_id: 22880 reply_id: 91393[/import]

#4

Samsung Galaxy Ace is ARMv6, I’m unsure on the others - was the original version built with an old version of Corona to support those devices? [import]uid: 52491 topic_id: 22880 reply_id: 91403[/import]

#5

The Kogan Agora is definitely not an Arm V6 and remember that the first version of the app was able to be downloaded from the market. I can’t add attachments here but I can send you screenshots showing the lite version of our app is incompatible and the paid version is not. I’m pretty confident if I upgrade the paid version it will no longer be compatible either.

HTC Sensation has an Dual-core 1.2 GHz Scorpion - is that an issue? Although the user reported the same issue as above, i.e. that they can download one version and not the other.

According to the following the Samsung Galaxy Ace has an ARM 11 which is presumably high enough?:
http://www.gsmarena.com/samsung_galaxy_ace_s5830-3724.php

The original version is only a couple of weeks old and was built with exactly the same version of corona as the newer one.

[import]uid: 60648 topic_id: 22880 reply_id: 91431[/import]

#6

The samsung galaxy ace is an armv6 device. ARM and ARMV aren’t the same thing.

From a google search, it seems all those devices you mentioned are armv6, which corona doesn’t support.

Only Armv7 and above [import]uid: 84637 topic_id: 22880 reply_id: 91474[/import]

#7

The Kogan Agora tablet has a Cortex A8 CPU which is uses the ARMv7 instruction set. Evidence at the links below:
Specifications: http://www.kogan.com.au/shop/7-inch-android-tablet-pc/
ARMv7: https://en.wikipedia.org/wiki/ARM_Cortex-A8

Likewise the Scorpion is ARMv7 compatible:
https://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)

@Danny can you please check your facts and if you find evidence contrary to the above post the evidence?

I now understand that an ARM 11 CPU uses the ARMv6 instruction set so that explains the Galaxy Ace and I will inform our user - perhaps they hadn’t experienced the same symptoms after all.

There is still an issue with the first two - can anyone shed any light? [import]uid: 60648 topic_id: 22880 reply_id: 91600[/import]

#8

James it appears you are correct, as I said i just did a google search, usually you can find specific armv details by searching for mydevice armv

So on those two devices, does the market simply not allow the device to download the app ? [import]uid: 84637 topic_id: 22880 reply_id: 91727[/import]

#9

Only after the second version of the app, the initial version is fine - I think this happened to our previous app, Mandarin Madness, as that is not available on those same devices yet it was briefly initially. I wasn’t tracking it carefully at the time so can’t be sure it coincided with the first version up grade but the same symptoms were observed i.e. the MID7007 device had the app installed from the market but then couldn’t get the updated version and could no longer even see the app on the market.

This is why I was carefully watching the compatibility of our second app Spanish Smash. It was definitely visible after launch and I downloaded both the lite and paid versions on the device.
After publishing the second lite version I went to ensure the update worked on the device and that’s when I discovered the device could no longer see the app, and could not get the update. Going to the web and logging in to the market with the same credentials as on the device revealed the market reporting the lite version of the app is incompatible with the MID7007, yet the still to be upgraded paid version was reported as compatible.

Could this be anything to do with the way Corona creates the manifest file?

Google is giving me absolutely no help. [import]uid: 60648 topic_id: 22880 reply_id: 91771[/import]