Development issue/problem:
I have problems with the Google Play Store and insist that my application is supported on 0 devices. I’ve tried all the solutions I’ve found on SO and elsewhere. It’s not that the apk is inactive, it’s turned on by default, and I even tried to turn it off and on again.
I have tested it on my Galaxy Nexus and it works very well, there is no reason why it would not be compatible with an Android device……
Here’s my manifesto:
The full source code of the project can be found here: https://github.com/Nurgak/Android-Bluetooth-Remote-Control, because it is open source.
That’s what I see on Google Play.
The five characteristics are
android.hardware.ACCELEROMETER
android.hardware.BLUETOOTH
android.hardware.CAMERA
android.hardware.AUTOFOCUS
android.TOUCHSCRES
And four permits
android.permission.BLUETOOTH
android.permission.BLUETOOTH_ADMIN
android.permission.CAMERA
android.permission.INTERNET
I too was absolutely blown away by their support, I only received a generic email response to our FAQ.
How can I solve this problem?
Solution 1:
- Try changing the name of the apk from com.bluetooth to com.nurgak.bluetoothremote.
- Try setting all usage tags to false.
- Try to remove all permissions (I know the application won’t work without these permissions, but to see why Google Play says the application supports 0 devices).
P.S: You don’t need an android.hardware.screen.portrait if you set
to false. In this case it has no effect.
Solution 2:
I encountered a similar problem when I entered the camera hardware in the use-feature tag of the manifest file as follows:
If you do not specify the android:required attribute, the default value will be true. That’s why the Google Play Store assumes that the application will not work if the camera hardware is missing.
Once you have set android:required to false as below, the Play Store will accept the MOTOR and display the list of available devices for the application.
You can also check the function descriptions for typing errors. See http://developer.android.com/guide/topics/manifest/uses-feature-element.html#features-reference for supported job descriptions.
Read more : http://developer.android.com/guide/topics/manifest/uses-feature-element.html
Solution 3:
We recently switched to Android Studio (from Eclipse), and I tried to download my first production version made in Studio, and I got the dreaded Supported Android Devices 0 message when I downloaded the MOTK. The solution was to enable the Apache Commons codec library.
Check your build.gradle file – if you see anything like it:
Create ‘org.apache.directory.studio:org.apache.commons.codec:1.+’.
change it to:
Compile commons-codec:commons-codec:1.+.
My theory is that part of the namespace org.apache.directory.studio disrupts the developer’s console and the use of steno works well.
How did I find out? They got lucky and I found their promise message on a Google search.
Solution 4:
For me, the problem was this line in the manifest file:
I can spend a lot of time tracking them down, but fortunately Google offers an option in the developer’s console to contact them via chat (for some reason this option is no longer available on ATMW, maybe it’s closed?) They were able to locate the problem in a few minutes, I had to change the above line into
A considerable time saving, thanks to Google!
Solution No 5:
Go to Troubleshooting -> Device Catalog and select any unsupported device to view the data, and you will see the reason why it is not supported.
Solution No 6:
Sometimes this is due to a third party library you are referring to. If you can find out which ones, and if you can delete them, you can solve the problem.
In case I have to cancel:
org.apache.commons.io:2.4
Solution No 7:
I had a similar problem. My solution was to write this line correctly in the manifesto:
Solution No 8:
Although this question has been answered with some additional adjustments,
has removed any dependency on .jar (especially the general dependency on .*.jar).
I was able to solve the problem after the addiction was dealt with.
Solution No 9:
If you are using the gradle, make sure that all manifests in your project are aligned with the sdk min/max/target version.
Solution No 10:
I also had a problem with 0 supported devices, but the reason was different. One of the libraries creates a lib/README.txt file in the generated MOT. After downloading the MOT to the Google game console, the file lib/README.txt is retrieved by the MOTK parser and is considered a native library that is not supported by any device.
I solved the problem by deleting the MOTK file with the following Gradle configuration in the build.gradle file:
android {
…
packagingSettings {
excluding lib/README.txt
}
}
Good luck!
Related Tags:
google play console device catalog,android app compatibility mode,name the india's first mobile app,google play devices list,android compatibility test,can t find app in play store,recommended minimum sdk android 2019,developer android screen support,android gms requirements,which android versions are still supported,kindle amazon android manifest,amazon app store compatible devices,amazon developer upload apk,amazon developer update app,how to update amazon app store,screenshot amazon fire,amazon app store categories,amazon app submission checklist,manifest req amazon,amazon this device does not support,apply amazon drm,fire tv screen capture,how to make android app compatible with all devices,this app was built for an older version of android fix,how to make your device compatible with any app,0 devices supported after release apk android,<uses-feature android:name="android.hardware.camera2.full" />,how to make android app compatible with tablet,check app compatibility android,device support removed
