This is the link to my google app
QuizByte
The app was developed for android api level 13 and above. after publishing some of the phones (Samsung Duos(GT-S7262) )which should be compatible cant see the app in google play. sending a direct link to the phone to email and checking shows that 'this device is no compatible'.
I searched and tries everything I can
Tried adding and removed unused permissions but still no luck.
And when I upload it into google play it shows lots of samsung and sony(which should be compatible) in the incompatible-device list.
Thank you.
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
.
<uses-feature android:name="android.hardware.location" android:required="false"/>
<uses-feature android:name="android.hardware.location.network" android:required="false" />
<uses-feature android:name="android.hardware.location.gps" android:required="false"/>
<uses-feature android:name="android.hardware.touchscreen" android:required="false"/>
<uses-feature android:name = "android.hardware.screen.portrait" android:required="false"/>
<uses-feature android:name="android.hardware.faketouch" android:required="false" />
.
Compatible devices were increased (~+500) when I added in manifest
But it still shows not compatible with sony and samsung models
Made it working after Changing the minimun SDk Level to 9. Now its showing in the samsung sony devices,
Dont know the exact reson though.Thought that Someone with a similar problem may try this
Related
I am trying to publish app bundle on play store. It shows wifi only tablet not supported because of android.hardware.telephony feature. I set this feature's required flag to false. But still play console shows the same error in device catalogue. Any idea why it is showing an error as not supported device samsung galaxy A7 lite (wifi only)?
I am checking this problem in a following way: I upload app bundle then I save it. Before publishing I go to device catalogue to check the supported devices for the same app bundle. And there I see an error.
My AndroidManifest permissions and features:
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-feature
android:name="android.hardware.camera"
android:required="false"
tools:node="replace"/>
<uses-feature
android:name="android.hardware.camera.autofocus"
android:required="false"
tools:node="replace"/>
<uses-feature
android:name="android.hardware.telephony"
android:required="false"
tools:node="replace"/>
Merged manifest:
Play console error:
Doesn't support required feature: android.hardware.telephony
This issue is solved. For others I am putting an answer here. It's funny that I just ignored that device catalogue for the saved release and rolled it out directly. That manifest changes started working for the release and play console started showing supported for the device which was unsupported previously. :)
I have searched through the google but could not find any reason why google play showing support for only 45% devices it support to 90 to 92 percent devices on the play store
here my manifest permissions
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission
android:name="android.permission.READ_PROFILE"
android:required="false" />
<uses-permission
android:name="android.permission.READ_CONTACTS"
android:required="false" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="com.android.vending.BILLING" />
but google play showing some extra permissions am also wondering why play store showing this
Also i have a question that can google play filtering apps on camera flash or flash light availability?
any help will be appreciated thanks
You likely have a library that uses those other features. In particular, it looks as though you have a library that uses the camera and thus adds the camera, microphone, flash, and autofocus features.
You can easily identify the library that is adding these features by looking at the manifest merger report generated by Gradle. This is located at app/build/outputs/logs. The manifest merger report text file there will list out every manifest element pulled in from different manifest files and which file they came from.
If you truly do not require those features, you can declare your own <uses-feature> elements with the android:required attribute set to false.
Please try to add the following to your manifest, please change the required in order of your functionalities:
<uses-feature
android:name="android.hardware.camera"
android:required="true" />
<uses-feature
android:name="android.hardware.camera.autofocus"
android:required="false" />
<uses-feature
android:name="android.hardware.camera.flash"
android:required="false" />
<uses-feature android:name="android.hardware.microphone"
android:required="false" />
<uses-feature android:name="android.hardware.screen.portrait"
android:required="false" />
Also, why is your api lvl 16+? If you switch to 15+ you will have a lot of more devices.
I have published my first camera app, and in developer console currently there are 4282 supported devices and 0 excluded.
Three Nexus 7 models are listed in the supported list (1.Google Nexus 7 - flo, 2.Google Nexus 7 - deb and 3.Nexus 7), however i cannot install the apk on my Nexus 7 (2012) through Google Play saying it's not compatible. (i use to test my app on that device, it runs perfectly).
I know my manifest should include
<uses-feature android:name="android.hardware.camera" android:required="false" />
to be compatible with Nexus 7, but why does it appear in the supported list?
Using the device availability dialog document states:
Device Availability provides a dynamic list of compatible devices
based upon your manifest settings
so my Nexus 7 should not be listed!
Do i miss something?
EDIT
here's manifest permissions and features:
<uses-sdk android:minSdkVersion="9" android:targetSdkVersion="19"/>
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.WRITE_SETTINGS" />
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.INTERNET"/>
<uses-feature android:name="android.hardware.camera" android:required="true" />
<uses-feature android:name="android.hardware.sensor.accelerometer" android:required="true"/>
<uses-feature android:name="android.hardware.telephony" android:required="false" />
<uses-feature android:name="android.hardware.microphone" android:required="false" />
<uses-feature android:name="android.hardware.screen.portrait" android:required="false" />
Adding
<uses-feature android:name="android.hardware.camera" android:required="false" />
to the manifest file (although i wouldn't, because actually camera is required), 56 devices were added to the supported devices list, included two more Nexus 7, now they are:
GoogleNexus 7– grouper
Nexus 7
GoogleNexus 7– tilapia
GoogleNexus 7– deb
GoogleNexus 7– flo
I deduce that deb and flo are the new ones, with back camera, and old ones (v2012) are grouper and tilapia, i don't know about the ones labeled "Nexus 7" only.
Basically, some Nexus 7 devices do not need any user permission for Camera or WiFi, but has to be used the uses feature instead.
For example, use these
<uses-feature android:name="android.hardware.camera" android:required="false"/>
<uses-feature android:name="android.hardware.wifi" android:required="false"/>
instead of
<uses-permission android:name="android.permission.CAMERA"/>
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
Does your G7 has camera? If not, it is correct that you cannot see it from GooglePlayStore on your G7 (since you have set require camera = true).
And another check point, might mean you should have a GPS.
Does anyone know how you can see why Google Play Store is marking specific devices for an app you created as 'not compatible' ?
I created an app and one of my testdevices was a GalaxyTab2. On this device all functions of the app are working no problem when you just put the apk on the device using a USB cable/or just downloading it from a website.
However when I upload the app to playstore the GalaxyTab2 is listed as an unsupported device. So GalaxyTab2 users are unable to install the app.
In the Google Play Developer Console you can see an overview of unsupported devices. But it seems that you can't get any info 'why' the device is unsupported.
This currenlty lists 1000 devices. Of these a lot will be unsupported due to the fact that their Android version is too old. But from some devices (like the GalaxyTab 2) I am sure they can and run the apk no problem.
Some lines of my manifest:
<supports-screens android:smallScreens="true"
android:normalScreens="true"
android:largeScreens="true"
android:xlargeScreens="true" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.FLASHLIGHT" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-sdk
android:minSdkVersion="9"
android:targetSdkVersion="16" />
Try adding:
<uses-feature android:name="android.hardware.camera.flash" android:required="false" />
<uses-feature android:name="android.hardware.camera.autofocus" android:required="false" />
To your manifest. Your FLASHLIGHT permission may imply that it is a required feature, and as the Galaxy Tab 2 doesn't have a flash, it'd be incompatible. Same for autofocus, as pointed out by #323go.
The problem can be with the feature requirements for certain permissions.
For example
<uses-permission android:name="android.permission.CAMERA" />
may include the requirement of AutoFocus, so I would try to add
<uses-feature android:name="android.hardware.camera.autofocus" android:required="false" />
to the AndroidManifest.xml.
Also the permission
<uses-permission android:name="android.permission.FLASHLIGHT" />
may include the requirement of flash hardware so I would add
<uses-feature android:name="android.hardware.camera.flash" android:required="false" />
as well.
Here you can find a list that shows all permissions that imply Feature Requirements
http://developer.android.com/guide/topics/manifest/uses-feature-element.html#permissions
Remove android:allowBackup="true"
A potential user of my Android app has contacted me to report that they are unable to install my app from the Android Market.
They receive the following error when attempting to install the application:
"Application requires features not available on your device."
My app declares the following requirements in its manifest:
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.BATTERY_STATS" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-feature
android:name="android.hardware.camera"
android:required="false" />
<uses-feature
android:name="android.hardware.camera.autofocus"
android:required="false" />
<uses-feature
android:name="android.hardware.location"
android:required="true" />
<uses-feature
android:name="android.hardware.location.gps"
android:required="true" />
<uses-feature
android:name="android.hardware.screen.portrait"
android:required="true" />
The user's device is a Samsung Infuse 4G. I have been over the specs for Samsung Infuse and it is clear that has the necessary hardware to satisfy these requirements.
Moreover, the Samsung Infuse 4G is listed as a supported device for my app in the Android Market Developer Console "Device Availability" dialog.
Has anyone else seen this error? Can anyone suggest any possible causes for this error which could be addressed/worked around?
Many thanks.
When this happens on my app, I have a "debug" app that I temporarily publish in the market. I remove one restriction at a time until it installs properly for the customer.