[SOLVED] App on play store cannot be found if device does not have GPS



  • I have an app that utilises GPS, but doesn't essentially need it. I have two devices that dont have a GPS and they cannot find the app.

    Looking in the google developer console, under Required Permissions it lists:

    @
    android.permission.ACCESS_FINE_LOCATION
    android.permission.CAMERA
    android.permission.INTERNET
    android.permission.READ_EXTERNAL_STORAGE
    android.permission.RECORD_AUDIO
    android.permission.WRITE_EXTERNAL_STORAGE
    @

    Any idea how I remove requirements? None of them are essential for it to work.

    In the AndroidManifest.xml I only have:

    @
    <uses-permission android:name="android.permission.INTERNET"/>
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
    @



  • I do not understand your request.

    When developing an app that uses the XYZ you have to insert the permissions the app:

    <uses-permission android:name="android.permission.FOR_XYZ"/>

    But in your app you have to check if you can instantiate the object linked with XYZ.

    When you publish on play store you declare that your app use the component XYZ.

    it is normal that if the device does not have the possibility to use the XYZ component is not shown.

    If in your application you do not need to use the XYZ component then its reporting in the registration phase of play store.



  • Thanks, I went through adding the user-permission settings in the manifest on Tuesday evening.

    I also added the uses features:

    @
    <uses-feature android:name="android.hardware.location.GPS" android:required="false" />
    @

    Came to it Wednesday morning, and to my dismay it still didn't appear on the play store. If I did a search for it out of the play store I could get it to appear, but it said "Incompatible".

    Eventually I did a firmware update from Settings in Android, then it immediately appeared in the Play Store.

    Very odd. Maybe Google should give more advice as to why it's incompatible?



  • So I think it's a Google problem and not of qt.

    It sure would be nice to have an official response from Google.



  • Yes, not Qt at all.

    Google just need to give users (or maybe the developer console) a reason for deciding that it won't work on a particular hardware device. Otherwise it's just guesswork.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.