touch-packages team mailing list archive

[Didier Roche <didrocks@xxxxxxxxxx>]

Public bug reported:

With OTA5. Note that I don't know if the caching is done in location-
service or is due to PositionSource Qt components.

1. Starts an application with location capability, accept the location permission
-> You have some console.log() callback on position changed
2. Without closing the app, go to system settings and disable location permission for that app
3. Put back your application in focus
-> You will still see regular (at updateInterval refresh) console.log() callback onPositionChanged, firing the same QGeoCoordinate than the last known one.

I guess it should send QGeoCoordinate(nan, nan, nan) (and should set the
Error parameter) as when we can't theorically get the current position
anymore.


----

snippet:

import QtPositioning 5.2
import QtLocation 5.3

PositionSource {
    active: true
    updateInterval: 120000 // 2 mins
    onPositionChanged: {
        console.log("coordinates " + positionSource.position.coordinate);
    }
}

** Affects: location-service (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: devexp

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1488795

Title:
  Still getting cached last location even if the permission is denied in
  system settings after the application started

Status in location-service package in Ubuntu:
  New

Bug description:
  With OTA5. Note that I don't know if the caching is done in location-
  service or is due to PositionSource Qt components.

  1. Starts an application with location capability, accept the location permission
  -> You have some console.log() callback on position changed
  2. Without closing the app, go to system settings and disable location permission for that app
  3. Put back your application in focus
  -> You will still see regular (at updateInterval refresh) console.log() callback onPositionChanged, firing the same QGeoCoordinate than the last known one.

  I guess it should send QGeoCoordinate(nan, nan, nan) (and should set
  the Error parameter) as when we can't theorically get the current
  position anymore.

  
  ----

  snippet:

  import QtPositioning 5.2
  import QtLocation 5.3

  PositionSource {
      active: true
      updateInterval: 120000 // 2 mins
      onPositionChanged: {
          console.log("coordinates " + positionSource.position.coordinate);
      }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1488795/+subscriptions