cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-11875) Cordova-Plugin-Geolocation requires feature android.hardware.location.gps (android 21+)
Date Sat, 01 Oct 2016 15:55:20 GMT

    [ https://issues.apache.org/jira/browse/CB-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15538721#comment-15538721
] 

ASF GitHub Bot commented on CB-11875:
-------------------------------------

Github user mikepsinn commented on the issue:

    https://github.com/apache/cordova-plugin-geolocation/pull/81
  
    @stevengill Good points. Thanks for the explanation!  
    
    Do you think I should add something to the "Android Quirks" section of the README warning
people that their app won't be available to non-GPS devices if they use this plugin unless
they remove that line before building?


> Cordova-Plugin-Geolocation requires feature android.hardware.location.gps (android 21+)
> ---------------------------------------------------------------------------------------
>
>                 Key: CB-11875
>                 URL: https://issues.apache.org/jira/browse/CB-11875
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android, Plugin Geolocation
>            Reporter: Warren Parad
>            Assignee: Audrey So
>              Labels: easyfix, newbie, patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Hello Google Play Developer,
> We're writing to let you know that the apps listed at the end of this email may be affected
by an upcoming platform change.
> Action required: If your app requires GPS hardware to operate properly, you will need
to explicitly add the "android.hardware.location.gps" uses-feature to your manifest.
> What’s changing
> We’re making a change on October 15th, 2016 that will affect apps targeting API version
21 (Android 5.0, Lollipop) or higher that use ACCESS_FINE_LOCATION but don't explicitly have
the "android.hardware.location.gps" uses-feature. Going forward, these apps will be available
to install on devices that don't have GPS hardware. In most cases this won't be an issue since
Wi-Fi and Cell-ID based location provides high enough fidelity for the typical operation of
these apps. However, any apps that require GPS hardware, such as GPS navigators, should explicitly
add the *"android.hardware.location.gps" uses-feature* to their manifest.
> If your app requires GPS to function properly and you do not include android.hardware.location.gps
in your manifest declaration, your users may have a poor app experience.
> Also, if you’re using the fused location provider and wish to receive the most accurate
location samples from GPS (i.e. with PRIORITY_HIGH_ACCURACY), you must include the "android.hardware.location.gps"
feature in your app’s manifest to ensure that Google Play only distributes your app to devices
with GPS sensors.
> You can read more about this change in the Android Developers Help Center.
> Regards,
> The Google Play Team



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message