Someone already did it.

https://issues.apache.org/jira/browse/CB-11875

But yeah, this is a newbie one, since it's literally one line in
plugin.xml.  I'll do it tomorrow, but if someone wants an easy PR done, do
it up.

On Wed, Sep 21, 2016 at 4:55 PM, Steven Gill <stevengil...@gmail.com> wrote:

> Do it!
>
> On Tue, Sep 20, 2016 at 12:20 PM, Joe Bowser <bows...@gmail.com> wrote:
>
> > FYI.  I'm going to create an issue to add this to the plugin.xml for
> > geolocation later.
> >
> > ---------- Forwarded message ----------
> > From: Google Play <googleplay-nore...@google.com>
> > Date: Tue, Sep 20, 2016 at 11:40 AM
> > Subject: Google Play change to Android ACCESS_FINE_LOCATION permissions
> > To: bows...@gmail.com
> >
> >
> > 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
> > <https://www.google.com/appserve/mkt/p/bWVg1YSZPx-2Sk1mB8v3V5DE2_
> > HelAsLfkx0mUzuENWxtqMA6Ax7dkRwzYtv5u1mnNjWZye17r3zTTrs1z_Q2AUnAygTF2M-
> > deVbIrIsu2evapXjKKgv4ttr0ngMFag=>
> > .
> >
> > Regards,
> >
> > The Google Play Team
> >
> > Up to 20 affected app(s) and version(s) are listed below. If you have
> more
> > than 20 apps in your catalogue, make sure to check each app for this
> issue.
> >
> > ca.dontflyhere.app   18
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ©2016 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
> >
> > Email preferences: You have received this mandatory email service
> > announcement to update you about important changes to your Google Play
> > Developer account.
> >
>

Reply via email to