iOS ~ Backgrounding & Geolocation

Asked this on forum.qt.io, but with no help...can someone here offer any insight?
=========================================
When running my app on iOS 9 that collects the user's location (typically once per second) and the app is backgrounded, the OS kills the geolocation service. I have updated the info.plist to account for required background modes and the location services according to the Apple docs. But, processing still stops.

On iOS 6.1, however, this does not happen, processing continues when the app is backgrounded.

According to StackOverflow, we should be using this to enable background locations in iOS 9...but how do we do that with Qt?

Code:

---

if ([self.locationManager respondsToSelector:@selector(allowsBackgroundLocationUpdates:)]) {
    self.locationManager.allowsBackgroundLocationUpdates = YES;
}

---

http://stackoverflow.com/questions/3...-in-background

SO, I am doing the following, which works in the iOS simulator (iOS 9, iPhone6), but not on the phone.

I call EnableIOSBackgroundLocation() in my main.cpp file. The return Boolean sets a QML Image to be visible (either a green GPS icon on success or a red one on failure).

In the simulator, the green GPS icon shows up...and the location continues to be logged when the app is put in the background. On a real iPhone running iOS 9, the green GPS icon shows up also, but the GPS is killed after a couple of minutes when the app is backgrounded.

Anyone have any ideas why?

iosLocation .mm:

Code:

---

#include "ioslocation.h"
 
#import <CoreLocation/CoreLocation.h>
 
bool IOSLocation::EnableIOSBackgroundLocation()
{
  CLLocationManager *locationManager;
  locationManager = [[CLLocationManager alloc] init];
 
  if ([locationManager respondsToSelector:@selector(allowsBackgroundLocationUpdates:)]) {
    locationManager.allowsBackgroundLocationUpdates = YES;
 
    if ([locationManager respondsToSelector:@selector(pausesLocationUpdatesAutomatically:)]) { 
      locationManager.pausesLocationUpdatesAutomatically = NO;
 
      // Request location authorization
      [locationManager requestAlwaysAuthorization];
 
      // Set an accuracy level. The higher, the better for energy.
      locationManager.desiredAccuracy = kCLLocationAccuracyBest;
 
      // Specify the type of activity your app is currently performing
      locationManager.activityType = CLActivityTypeOtherNavigation;
 
      // Set distance filter to NONE
      locationManager.distanceFilter = kCLDistanceFilterNone;
 
      return true;
    } else {
      return false;
    }
  }
  return false;
}

---

iosLocation .h:

Code:

---

#ifndef _iosLocation_h
 #define _iosLocation_h
 
class IOSLocation
 {
 public:
 static void EnableIOSBackgroundLocation();
 };
 
#endif

---

Anyone have any ideas on why this is happening? Ideas on how to get around it and make it work?

--Sam

I've had a thought on what may be happening. Since the locationManager instance is declared inside the EnableIOSBackgroundLocation function, is it possible that it is not persisting beyond that function? And therefore those CLLocationManger values are not remaining after the function exits?

If that is the case, then how can I create a locationManger variable that persists throughout the application? How can I declare it and access it from the QT code?

Ok, more info...

Using this code:
*.h

Quote:

---

#ifndef __iosLocation_h_
#define __iosLocation_h_

class IOSLocation
{
public:
static bool EnableIOSBackgroundLocation();
};

#endif

---

*.mm:

Quote:

---

#include "ioslocation.h"

#import <CoreLocation/CoreLocation.h>

bool IOSLocation::EnableIOSBackgroundLocation()
{
CLLocationManager *myLocMan;
myLocMan = [[CLLocationManager alloc] init];

if ([myLocMan respondsToSelector:@selector(allowsBackgroundLocat ionUpdates:)]) {
myLocMan.allowsBackgroundLocationUpdates = YES;

if ([myLocMan respondsToSelector:@selector(pausesLocationUpdates Automatically:)]) {
myLocMan.pausesLocationUpdatesAutomatically = NO;

// Request location authorization
[myLocMan requestAlwaysAuthorization];

// Set an accuracy level. The higher, the better for energy.
myLocMan.desiredAccuracy = kCLLocationAccuracyBest;

// Specify the type of activity your app is currently performing
myLocMan.activityType = CLActivityTypeOtherNavigation;

// Set distance filter to NONE
myLocMan.distanceFilter = kCLDistanceFilterNone;

return true;
} else {
return false;
}
}
return false;
}

---

And debugging with XCode while running on an attached iPhone... SOME of the variables are set correctly (such as allowsBackgroundLocationUpdates and myLocMan.activityType). However, the other essential pieces do not get set (pausesLocationUpdatesAutomatically, myLocMan.distanceFilter and myLocMan.desiredAccuracy).

So, I again did more Googling...and have come up with a possible reason. It seems to be that the 'extra' parameters can only be set IF the delegate of CLLocationManager is set... does that sound right to anyone?

Being as that may be the case...how can I set it? I've pulled code from https://github.com/colede/qt-app-delegate, but am not sure exactly how to get the AppDelegate and set it properly.

Anyone???

And...with more searching and headscratching... I see that MANY examples of using CoreLocation set the delegate to 'self'...

So that raises the question... How & Where do I get 'self' when compiling this QT project in XCode? I've tried, but I keep getting 'self is undefined'.

My guess would be that such information can be found at Apple's developer site.
After all that is not related to Qt but would apply to all C++ based applications.

Cheers,
_

It IS related to QT/QML, as this is a project I am using QT for....and outputting a XCode project to compile.

Just hoping someone here had seen this and found a solution.

Quote:

---

Originally Posted by scgrant327

It IS related to QT/QML, as this is a project I am using QT for....and outputting a XCode project to compile.

Just hoping someone here had seen this and found a solution.

---

I didn't want to imply that this wasn't relevant for this forum, just that an Apple developer site might have a higher chance of yielding results.
After all the questions is about integrating Objective-C with C++, regardless of whether the C++ is also using Qt.

Cheers,
_

So, as indicated by Anda_Skoa here, SGaist on forum.qt.io and 'Eskimo' over on the Apple Dev Forum, this is an Objective-C issue.

However.. since I am trying to use Objective-C in my QT app, the issue then becomes...How Do I Use Objective-C?

In short, the posted code runs without any real issues. Just some of the variables are not getting set as I need them to. Not being an Objective-C (or iOS) guru, I have to ask the noob question... Is the code I posted truly Objective-C? If it is not, then how do I make it Objective-C (so I can get to the 'self' object), and call it from my QT C++ functions?