Google Play: Your device is incompatible with this version -> "No Carrier" - android

I can't find anything online for this.
A user mentioned that he couldn't download my App because Google Play wouldn't let him. So I bought the device the user has (Galaxy Tab 3) because I couldn't figure it out remotely.
I can't find the App in the Play Store on the device. If I log in with the same Google account, it tells me that my device is incompatible with this App. All the information I have is "No Carrier".
Could it be possible that if my App needs an Internet connection I can't download the App if the device doesn't have a Sim-Card or something?
Update:
I have another flavor of this app in the store. The only difference (manifest-wise) is that this app needs camera permissions. But even if I make those optional (setting 'required' to false), it doesn't help. Also the specific model 'GT-P5210' is not listed in neither of my Apps in the supported devices list (even though I can find the other app in the store with the device). Also I made sure that there are screenshots for every possible tablet size.
Also I can of course install the App from Android Studio.

in the google play console, under store listing
add some screenshots for "TABLET".
without that, google play will think that your app is not meant for Tablets (which Galaxy Tab 3 is classified under).

The error indicates that there is a requirement listed in the app's manifest for phone networking. You need a phone to use it.

Related

Android Play-store behavior on app download

I was just curious to know few basic behavior of the google play-store.
Tried to find the answers of below questions:
1) If my phone network is switched from cellular to WI-FI while i am downloading an app from the play-
store. How google manages the connection as it resumes the download from where it stopped, because as
far as i know the IP address will change and TCP connection restarts the session.
2) What are the detailed steps involved right from requesting for an app from play-store till it is
installed in our device. I mean what are the factors of the device google crosschecks, for instance,
if the minimum version of the app is 7.0 and i have a device of 6.0, will the .apk gets downloaded and
then the version is verified or it is verified before the download starts.
Couldn't able to find a document on these. Please share if you have one.
Regarding 2)
The Play Store won't offer you an app for download if your phone doesn't meet it's requirements. This means you won't be able to download the app via the play store if:
Your phone doesn't meet the required minimum android version
Your phone doesn't support one of the features that are marked with uses-feature required="true" in the manifest (see reference)
e.g. NFC, camera
The vendor explicitly excluded your phone from the list of supported devices
e.g. some Samsung apps are only available for Samsung smartphones, like Gear 360 app. Some games are only available for Nvidia Shield like Half Life 2
The vendor doesn't release the app in your region

<uses-feature> tag for AirGesture on Samsung devices

I am making an app which should only be installed on devices having the samsung airgesture capability. If the app were to be published on the play store that is very easy i can just select those devices, but it will not be published. So I thought of using the < use-feature > tag in the manifest so that the APK would not install if your phone does not have this feature. I could not find the identification of this feature to put that in the manifest. Some ideas?
Actually, i don't think that is possible. I checked the list of supported values for those tags and there is nothing related to this. http://developer.android.com/guide/topics/manifest/uses-feature-element.html#hw-features.
The fallback will be to have the app installed, but just display a message when the Device.model does not match the expected one
In the Google Play - Developer Console, you can specify on which devices you do not want your app installed.
This means, you have to know the devices with airgesture.

Getting a List of Supported Devices for Your App

It would seem that Google has provided for us to post our application online and they provide for a nice overall list of supported devices. This is just a list of all devices supported on the market however.
Within the Google Play Store, we as developers can choose to select filters on specific devices that we would like to support and can exclude devices as desired. However, support is questioning how we can let customers know which devices are on that support list.
The only way that I can currently see how to check if a device is on the supported list (before someone actually purchases a device and physically checks), would be for us to internally open up the developer console and check for them. This isn't really a manageable solution. I have to assume that there is somewhere that we as the developer can export the list of supported devices so that we can host it on a website somewhere and refer to it with a link from our website, or something similar. And yet I can find nothing. Has anyone had success in getting information from the Google Play Store for users?
Updates:
Simplistic means to try and retrieve this information have not proved fruitful. A select-all over the list of devices on the web window covering the supported devices does not show which devices have been excluded. It only shows devices that are supported by the restrictions from the manifest file. And of course there will be new devices added to the list of devices each day, and they don't seem to have much of an order to them when they are added in to the list of supported devices for the application. There doesn't seem to be much organization here.
Currently, we interact with specific external hardware for our application and we want to be sure that it works on families of devices before we support them, which is why it gets difficult to provide this list to customers. There doesn't seem to be any export functionality or physical way to share the supported list of devices with the customers.
For instance, if we support the Samsung Galaxy families that we have done extensive tests upon, but some of those devices are not USB OTG compatible, then we would want to show exactly which Samsung Galaxy ones in a list are available to them (but it doesn't stop with Samsung only of course).
This is what you need:
List of supported devices
Note :
It was updated on 2/18/2014 .
EDIT :
What would be needed is the list of devices that my application supports which is what gets filtered from the manifest file, as well as from exclusions that I have made within the store filters
AFAIK, there is no API provided by play store to get that list of devices because play-store applies filter on run time.
Reference:
Google Play uses the filter restrictions described below to determine whether to show your application to a user who is browsing or searching for applications from the Google Play app.
When determining whether to display your app, Google Play checks the device's hardware and software requirement, as well as it's carrier, location, and other characteristics. It then compares those against the restrictions and dependencies expressed by the application's manifest file and publishing details.
If the application is compatible with the device according to the filter rules, Google Play displays the application to the user. Otherwise, Google Play hides your application from search results and category browsing, even if a user specifically requests the app by clicking a deep link that points directly to the app's ID within Google Play.
checkout: How Filters Work on Google Play

Google play says my app has 0 app excluded but there are devices that can't find it

I just uploaded a Phonegap made app to google play and it displays that there are 0 devices excluded for it. This isn't true at all, since a friend cannot find the app by searching via google play. His device is a galaxy mini running Android 2.2, but as I said, my google play control panel says 0 devices excluded so I don't know the reason/what to do.I have allowed all screen types in my manifest and target sdk from 8 to 17.
Do anybody have a clue what's going on?
App name: Txorierri turismo.
Excluded is not the same as "not available."
You can choose specific devices and manually force them to be excluded, but they DO have to be compatible with your app, anyway.
If your app is only for large devices, for instance, all non-large devices won't see yout app in Play at all. You can choose some large devices, though, and exclude them, so they also won't be able to see the app (despite the fact of meeting your app's requirements).
So I finally find the problem, it has to do with galaxy mini model, if you have permission for camera in you manifest the app won't be available for this device. Hope this helps someone! Thanks!

App Not Running on Android Device (Tablet OS 4.0.3)

Recently, I uploaded an android application to Google play and checked it in various devices and it is running fine.
After a few days, my client purchased an Android tablet (Samsung Galaxy Tab GT-P3113,) which don't have GPS support, but my app uses it. Now when he tries to download this app from Google play he is getting "Device Not supported" message.
Please help me possible solutions.
When you download from g play it is a list with what applications needs/ uses.
A possibility may be that you have set a minimum android sdk and his tablet is lower that .
Another possibility ,but i am not sure, maybe in your project you had just customized folders of design without having a default one : ex: just drawable-hdmi , and no drawable
Other possibility : if the application uses maps the device has to support, you write in androidmanifest what it uses . Maybe you should do another apk and change manifest , remove maps and put it just for tablets.
This usually happens when, something called uses-feature in android which is automatically checked by Play Store
and in that you might have added GPS hardware because of which your application says device not supported.
For more details on this you can visit this link.

Categories

Resources