TC70 device is not supported on the Play store

M Mike Bedford 3 years 6 months ago
142 1 0

Hello all, I have two devices that I am developing an app (using Xamarin), one is the TC75X and the other is the TC70X. I followed the EMDK samples and have these two lines in my app manifest.

As you can see, I don't have those marked as required.

The issue is, I can install on the TC75X device but not the TC70X. I get ‘Your device isn’t compatible with this version’

I noticed that when I submit an app release via the Play store console, Google automatically says my app supports only 4 devices.

I did not select these four, it found them for me automatically. I believe it is narrowed down to only these four based on the EMDK library that is needed. So, I investigated that a bit further and found this for the TC75X

Notice the TC75X lists the com.symbol.emdk library as supported. However, look at the TC70X

So, I believe this clearly explains why I can only support 4 devices and the TC70X is not one of them. However, I don't know how to fix it. I cannot see a way to force the TC70X in my list, it is greyed out, like many others and I cannot do anything with them.

Here are all 17 of the devices, you can see all but four are greyed out and say not supported. I don't care about many of these but I do care about the TC70X.

Anybody know how to get around this? How did Google get the wrong information about these devices and how is that fixed as it is the root cause of the issue.

Another related question, how can I support and test on devices I know do not have an EMDK? For example, I have the two lines above in my manifest for the Zebra devices but what if I want to load my app on my Samsung device, which I know does not have support for the EMDK and simply just not try to load/use any of the barcode scanner/EMDK components when I am loading on this device or any other non-EMDK device?

Thanks!

Mike

Please Register or Login to post a reply

1 Replies

Y Yanis Dalabiras

Hi Mike,

All those devices which are not grayed out are WAN devices which contain a GPS chip, I suspect somewhere in your manifest you are saying that GPS or WAN is required, can you check that?  Or share your manifest here?  I haven't heard of a device in the Play Store not being able to support the EMDK before.

Regarding the second question, most customers put the EMDK library behind a sort of proxy, I have an example from one of my own projects here: WakeLock_WifiLock_Exerciser/EMDKProxy.java at master · darryncampbell/WakeLock_WifiLock_Exerciser · GitHub

If you are not too far in your development, you may choose to use DataWedge rather than the EMDK & there is a tutorial here if that appeals: .  With DataWedge you would not have had either these issues as it has no library dependencies so your app could have been installed on any Android device.

CONTACT
Can’t find what you’re looking for?