Android Market - This application is available to over 0 devices?

Question

I have published apk to the Android Market, activated and setup for free for all countries.

Answer 1

Probably your uploaded APK file is not active. You can check this in the APK tab and switch to "Advanced mode". Here you should have 2 categories, "Active" and "Inactive".

Your file is probably in the Inactive category and you can change it by clicking the Activate link that should be behind it.

Hope my translations are correct as my Market account is in Dutch :)

Answer 2

I had a similar problem, I explained before but a moderator deleted it.

My app after an update had was available for 0 devices.

Anyway I found the solution for my case, so you can check if it works for you as well.

my mistake was that I included .jar files in order to add some external libraries and not the respective external class folders. When I removed the .jar files and I just added the class folder then devices became over 700 again.

for example I had the facebook API (an old one, not the current) and I had created a jar file out of it in order to include it like this in my app. So when I removed the jar files and added the Facebook API projecy (Project Properties -> Java Build Path -> Projects -> Add..., the app was OK for the android market.

Hope I helped you!

Answer 3

i had similar issue, and resolved it just following the advice from http://androidforums.com/threads/0-devices-support-my-app-no-compatible-devices-on-play-store.947943/ , which was to change in build.gradle line compile 'org.apache.directory.studio:org.apache.commons.codec:1.8' to compile 'commons-codec:commons-codec:1.8' (so more or less general rule can be drawn, that you need to delete org.apache.(...) up to the package name and then just double it before semicolon).

I would be glad though, if someone would point me out why it was like that. Looking for the second term in Maven Central through Android Studio returned no results actually, so I doubted at first if it is going to work at all.

Answer 4

For the records, I've found that one significant change that solved my case. Full explanation is at this post on Android Market Product Group.

Quick answer is remove the following uses-feature nodes from your manifest if present:

<uses-feature
    android:name="android.hardware.touchscreen"
    android:required="false" />
<uses-feature
    android:name="android.hardware.faketouch" />

Answer 5

Just activate the app on the APK files tab and you'll be ok.