从iOS9开始,我们在CCLocationManager的位置遇到了一些奇怪的问题。iOS 7-8没有问题。这些奇怪的位置会导致应用程序中出现错误。这个应用程序是在开车时使用的,我们在TestFlight上有大约50个测试用户,其中一些人报告了这些问题。
该应用程序对位置更新做出反应,每次位置更新,每25m和每50m都有一些事情要做。为了测试,我将所有这些位置存储在一个数组中。我们的测试用户有一个按钮,将发送GPX格式的历史邮件给我。
例如以下12个发送给我的位置:
<?xml version="1.0" encoding="UTF-8"?>
<gpx xmlns="http://www.topografix.com/GPX/1/1" version="1.1" creator="flitsmeister-ios-app-test" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
<wpt lat="51.28165091" lon="5.77329012">
<datetimegps>2015-09-29T04:36:55.371</datetimegps>
<datetimeprocessed>2015-09-29T04:36:55.460</datetimeprocessed>
<course>61.5</course>
<speed>13.3</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.1</altitude>
<sequencenr>0</sequencenr>
</wpt>
<wpt lat="51.28138654" lon="5.77244497">
<datetimegps>2015-09-29T04:36:55.506</datetimegps>
<datetimeprocessed>2015-09-29T04:36:55.523</datetimeprocessed>
<course>69.3</course>
<speed>13.5</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.7</altitude>
<sequencenr>1</sequencenr>
</wpt>
<wpt lat="51.28171319" lon="5.77345935">
<datetimegps>2015-09-29T04:36:56.371</datetimegps>
<datetimeprocessed>2015-09-29T04:36:56.441</datetimeprocessed>
<course>61.2</course>
<speed>13.2</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.0</altitude>
<sequencenr>2</sequencenr>
</wpt>
<wpt lat="51.28138654" lon="5.77244497">
<datetimegps>2015-09-29T04:36:56.562</datetimegps>
<datetimeprocessed>2015-09-29T04:36:56.571</datetimeprocessed>
<course>69.3</course>
<speed>13.5</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.7</altitude>
<sequencenr>3</sequencenr>
</wpt>
<wpt lat="51.28177064" lon="5.77362548">
<datetimegps>2015-09-29T04:36:57.371</datetimegps>
<datetimeprocessed>2015-09-29T04:36:57.440</datetimeprocessed>
<course>60.1</course>
<speed>13.4</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>32.9</altitude>
<sequencenr>4</sequencenr>
</wpt>
<wpt lat="51.28138654" lon="5.77244497">
<datetimegps>2015-09-29T04:36:57.541</datetimegps>
<datetimeprocessed>2015-09-29T04:36:57.558</datetimeprocessed>
<course>69.3</course>
<speed>13.5</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.7</altitude>
<sequencenr>5</sequencenr>
</wpt>
<wpt lat="51.28182383" lon="5.77380183">
<datetimegps>2015-09-29T04:36:58.371</datetimegps>
<datetimeprocessed>2015-09-29T04:36:58.438</datetimeprocessed>
<course>61.2</course>
<speed>13.7</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.3</altitude>
<sequencenr>6</sequencenr>
</wpt>
<wpt lat="51.28138654" lon="5.77244497">
<datetimegps>2015-09-29T04:36:58.371</datetimegps>
<datetimeprocessed>2015-09-29T04:36:58.491</datetimeprocessed>
<course>69.3</course>
<speed>13.5</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.7</altitude>
<sequencenr>7</sequencenr>
</wpt>
<wpt lat="51.28188803" lon="5.77398322">
<datetimegps>2015-09-29T04:36:59.371</datetimegps>
<datetimeprocessed>2015-09-29T04:36:59.431</datetimeprocessed>
<course>61.5</course>
<speed>14.4</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.4</altitude>
<sequencenr>8</sequencenr>
</wpt>
<wpt lat="51.28202386" lon="5.77435235">
<datetimegps>2015-09-29T04:37:01.371</datetimegps>
<datetimeprocessed>2015-09-29T04:37:01.432</datetimeprocessed>
<course>61.2</course>
<speed>14.9</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.5</altitude>
<sequencenr>9</sequencenr>
</wpt>
<wpt lat="51.28188803" lon="5.77398322">
<datetimegps>2015-09-29T04:37:01.444</datetimegps>
<datetimeprocessed>2015-09-29T04:37:01.454</datetimeprocessed>
<course>61.5</course>
<speed>14.4</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.4</altitude>
<sequencenr>10</sequencenr>
</wpt>
<wpt lat="51.28208027" lon="5.77454128">
<datetimegps>2015-09-29T04:37:02.371</datetimegps>
<datetimeprocessed>2015-09-29T04:37:02.430</datetimeprocessed>
<course>61.9</course>
<speed>15.1</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.3</altitude>
<sequencenr>11</sequencenr>
</wpt>
<wpt lat="51.28188803" lon="5.77398322">
<datetimegps>2015-09-29T04:37:02.513</datetimegps>
<datetimeprocessed>2015-09-29T04:37:02.521</datetimeprocessed>
<course>61.5</course>
<speed>14.4</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.4</altitude>
<sequencenr>12</sequencenr>
</wpt>
<wpt lat="51.28217918" lon="5.77472677">
<datetimegps>2015-09-29T04:37:03.371</datetimegps>
<datetimeprocessed>2015-09-29T04:37:03.434</datetimeprocessed>
<course>61.5</course>
<speed>15.2</speed>
<accuracyhorizontal>5.0</accuracyhorizontal>
<accuracyvertical>3.0</accuracyvertical>
<altitude>33.5</altitude>
<sequencenr>13</sequencenr>
</wpt>
</gpx>
如果我在地图上打印这些位置(geoplaner.com是我朋友),我会看到:
备注:点B、D、F、H在同一位置,但为了说明问题,我将这些点放在一行相邻的位置。
正如你可以看到的,如果你遵循序列A,B,C,你会看到点B不在正确的位置。
从iOS9 build开始,几乎每个测试用户在一周内都会遇到这种情况一到两次。
下面是我们使用的一些代码:
CLLocationManager (在平均线程上):
_manager = [[CLLocationManager alloc] init];
_manager.delegate = self;
_manager.desiredAccuracy = kCLLocationAccuracyBestForNavigation;
_manager.activityType = CLActivityTypeAutomotiveNavigation;
_manager.pausesLocationUpdatesAutomatically = TRUE;
if([_manager respondsToSelector:@selector(allowsBackgroundLocationUpdates)])
_manager.allowsBackgroundLocationUpdates = TRUE;
[_manager requestAlwaysAuthorization];
在另一种方法中,我调用start (也是在应用程序启动时调用,并在应用程序终止时停止)。(主线程)
[_manager startUpdatingLocation];
用于处理位置的代码(我删除了一些代码以保持示例的整洁):
- (void)locationManager:(CLLocationManager *)manager didUpdateLocations:(NSArray *)locations
{
CLLocation *lastLocation = [locations lastObject];
// test that the horizontal accuracy does not indicate an invalid measurement
if (lastLocation.horizontalAccuracy < 0)
return;
// test the age of the location measurement to determine if the measurement is cached
// in most cases you will not want to rely on cached measurements
NSTimeInterval locationAge = -[lastLocation.timestamp timeIntervalSinceNow];
if (locationAge > 5.0)
return;
NSDate *dateLocationArrived = [NSDate date];
CLLocation *beforeLocationRealtime = [self.LastLocationRealtime copy];
CLLocation *newLocation = [lastLocation copy];
//Realtime location.
[self setSpeedForLocation:[newLocation copy] withOldRealtimeLocation:[beforeLocationRealtime copy]];
[_delegateKaart updatedRealtimeLocation:newLocation fromPreviousLocation:[self.PreviousCurrentLocation copy]];
self.BeforeLastLocationRealtime = [self.LastLocationRealtime copy];
self.LastLocationRealtime = [newLocation copy];
if([self.CurrentLocation distanceFromLocation:newLocation] < 50) //Less then 50m?
{
if([_locationEach25m distanceFromLocation:newLocation] > 25)
{
//Nieuwe last 25m.
_locationEach25m = [newLocation copy];
//Each 25m do
[_delegateDashboard updatedLocation:[newLocation copy]];
[_delegateSignalering locationUpdated:[newLocation copy]];
[self holdLast200LocationsAndAddLocation:[lastLocation copy] withLocationArray:locations AndArriveDate:dateLocationArrived AndVerwerkt:TRUE];
}
else
[self holdLast200LocationsAndAddLocation:[lastLocation copy] withLocationArray:locations AndArriveDate:dateLocationArrived AndVerwerkt:FALSE];
return;//Stop
}
//Each 50m
[self holdLast200LocationsAndAddLocation:[lastLocation copy] withLocationArray:locations AndArriveDate:dateLocationArrived AndVerwerkt:TRUE];
_locationEach25m = [newLocation copy]; //Also new last 25m .
self.PreviousCurrentLocation = [self.CurrentLocation copy];//50m back.
self.CurrentLocation = [newLocation copy];
[_delegateDashboard updatedLocation:[newLocation copy]];
[_delegateSignalering locationUpdated:[newLocation copy]];
dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0), ^{
[_delegateCountryDetector locationUpdated:[newLocation copy]];
[self setHuidigeWegForLocation:[newLocation copy]];
});
[[SignaleringController sharedInstance] runSignaleringCheckForLocation:[newLocation copy]];
}
感觉就像locationmanager中的iOS9错误,它给我提供了关于用户行踪的错误结果。如果我搜索Stackoverflow.com,似乎我是唯一的一个。
--> Example2:
<wpt lat="52.32835728" lon="5.05861943">
<datetimegps>2015-10-01T06:27:29.905</datetimegps>
<datetimearrivedincode>2015-10-01T06:27:30.196</datetimearrivedincode>
<datetimeprocessed>2015-10-01T06:27:30.205</datetimeprocessed>
<c>138.4</c>
<s>26.5</s>
<accuracyhorizontal>10.0</accuracyhorizontal>
<accuracyvertical>6.0</accuracyvertical>
<al>5.9</al>
<nr>95</nr>
</wpt>
<wpt lat="52.32813366" lon="5.05927501">
<datetimegps>2015-10-01T06:27:31.905</datetimegps>
<datetimearrivedincode>2015-10-01T06:27:32.275</datetimearrivedincode>
<datetimeprocessed>2015-10-01T06:27:32.301</datetimeprocessed>
<c>119.5</c>
<s>26.0</s>
<accuracyhorizontal>10.0</accuracyhorizontal>
<accuracyvertical>4.0</accuracyvertical>
<al>5.7</al>
<nr>96</nr>
</wpt>
<wpt lat="52.32835728" lon="5.05861943">
<datetimegps>2015-10-01T06:27:33.196</datetimegps>
<datetimearrivedincode>2015-10-01T06:27:33.203</datetimearrivedincode>
<datetimeprocessed>2015-10-01T06:27:33.275</datetimeprocessed>
<c>138.4</c>
<s>26.5</s>
<accuracyhorizontal>10.0</accuracyhorizontal>
<accuracyvertical>6.0</accuracyvertical>
<al>5.9</al>
<nr>97</nr>
</wpt>
<wpt lat="52.32802075" lon="5.05960610">
<datetimegps>2015-10-01T06:27:32.905</datetimegps>
<datetimearrivedincode>2015-10-01T06:27:33.246</datetimearrivedincode>
<datetimeprocessed>2015-10-01T06:27:33.283</datetimeprocessed>
<c>119.2</c>
<s>26.3</s>
<accuracyhorizontal>10.0</accuracyhorizontal>
<accuracyvertical>4.0</accuracyvertical>
<al>5.3</al>
<nr>98</nr>
</wpt>
在地图上:
注意:A和C在确切的位置上,我手动更改了它们,以显示A在C后面。
下面的代码很奇怪:
第3点意味着我不能仅仅通过保留最后一个GPS日期来修复它,而跳过比最后一个更早的所有事情。
-->示例3:
GPX文件总数:
放大问题:
将双精度订单点和错误订单点相邻移动:
只是用ABCD符号重新加载了我感兴趣的点。
来自上面屏幕截图的GPX文件:
<?xml version="1.0" encoding="UTF-8"?>
<gpx xmlns="http://www.topografix.com/GPX/1/1" version="1.1" creator="flitsmeister-ios-app-test" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
<wpt lat="51.89792674" lon="4.54830456">
<tgps>2015-09-29T15:23:40.999</tgps>
<tv>2015-09-29T15:23:53.850</tv>
<c>131.8</c>
<s>13.1</s>
<ah>5.0</ah>
<av>3.0</av>
<al>2.0</al>
<nr>464</nr>
</wpt>
<wpt lat="51.89745789" lon="4.54927853">
<tgps>2015-09-29T15:23:47.999</tgps>
<tv>2015-09-29T15:23:53.910</tv>
<c>125.9</c>
<s>8.6</s>
<ah>5.0</ah>
<av>6.0</av>
<al>5.4</al>
<nr>465</nr>
</wpt>
<wpt lat="51.89745789" lon="4.54927853">
<tgps>2015-09-29T15:23:47.999</tgps>
<tv>2015-09-29T15:23:53.929</tv>
<c>125.9</c>
<s>8.6</s>
<ah>5.0</ah>
<av>6.0</av>
<al>5.4</al>
<nr>466</nr>
</wpt>
<wpt lat="51.89745789" lon="4.54927853">
<tgps>2015-09-29T15:23:47.999</tgps>
<tv>2015-09-29T15:23:53.932</tv>
<c>125.9</c>
<s>8.6</s>
<ah>5.0</ah>
<av>6.0</av>
<al>5.4</al>
<nr>467</nr>
</wpt>
<wpt lat="51.89762654" lon="4.54890185">
<tgps>2015-09-29T15:23:44.999</tgps>
<tv>2015-09-29T15:23:53.933</tv>
<c>128.0</c>
<s>13.4</s>
<ah>5.0</ah>
<av>4.0</av>
<al>0.6</al>
<nr>468</nr>
</wpt>
<wpt lat="51.89745789" lon="4.54927853">
<tgps>2015-09-29T15:23:47.999</tgps>
<tv>2015-09-29T15:23:53.965</tv>
<c>125.9</c>
<s>8.6</s>
<ah>5.0</ah>
<av>6.0</av>
<al>5.4</al>
<nr>469</nr>
</wpt>
<wpt lat="51.89755810" lon="4.54904694">
<tgps>2015-09-29T15:23:45.999</tgps>
<tv>2015-09-29T15:24:02.016</tv>
<c>126.9</c>
<s>12.5</s>
<ah>5.0</ah>
<av>4.0</av>
<al>0.2</al>
<nr>470</nr>
</wpt>
<wpt lat="51.89800163" lon="4.54815385">
<tgps>2015-09-29T15:23:47.731</tgps>
<tv>2015-09-29T15:24:02.068</tv>
<c>132.9</c>
<s>12.8</s>
<ah>5.0</ah>
<av>4.0</av>
<al>2.3</al>
<nr>471</nr>
</wpt>
<wpt lat="51.89800163" lon="4.54815385">
<tgps>2015-09-29T15:23:47.999</tgps>
<tv>2015-09-29T15:24:05.832</tv>
<c>132.9</c>
<s>12.8</s>
<ah>5.0</ah>
<av>4.0</av>
<al>2.3</al>
<nr>472</nr>
</wpt>
<wpt lat="51.89749909" lon="4.54917803">
<tgps>2015-09-29T15:23:46.999</tgps>
<tv>2015-09-29T15:24:05.842</tv>
<c>126.9</c>
<s>10.8</s>
<ah>5.0</ah>
<av>4.0</av>
<al>8.4</al>
<nr>473</nr>
</wpt>
<wpt lat="51.89800163" lon="4.54815385">
<tgps>2015-09-29T15:23:47.999</tgps>
<tv>2015-09-29T15:24:06.289</tv>
<c>132.9</c>
<s>12.8</s>
<ah>5.0</ah>
<av>4.0</av>
<al>2.3</al>
<nr>474</nr>
</wpt>
<wpt lat="51.89745789" lon="4.54927853">
<tgps>2015-09-29T15:23:47.999</tgps>
<tv>2015-09-29T15:24:06.307</tv>
<c>125.9</c>
<s>8.6</s>
<ah>5.0</ah>
<av>6.0</av>
<al>5.4</al>
<nr>475</nr>
</wpt>
<wpt lat="51.89732735" lon="4.54958171">
<tgps>2015-09-29T15:23:52.999</tgps>
<tv>2015-09-29T15:24:06.339</tv>
<c>121.6</c>
<s>2.9</s>
<ah>5.0</ah>
<av>4.0</av>
<al>-2.3</al>
<nr>476</nr>
</wpt>
</gpx>
在此文件中,问题出现了几次,但似乎位于两个问题位置。在那之后,没有更多的问题,但用户在一公里后杀死了应用程序。
-->我试过了:
将位置设置为CLActivityTypeAutomotiveNavigation
-->我学到了:
CLActivityTypeAutomotiveNavigation; = _manager.desiredAccuracy = kCLLocationAccuracyBestForNavigation;_manager.activityType =kCLLocationAccuracyBestForNavigation
发布于 2015-10-12 16:43:35
我终于想通了。以下是错误的地方:
如果(TRUE respondsToSelector:@selector(allowsBackgroundLocationUpdates)) { locationManager.allowsBackgroundLocationUpdates = locationManager;}
{TRUE= TRUE;}
didUpdateLocation
中设置这些属性,您将在完全相同的毫秒内得到4个位置。_manager.desiredAccuracy = kCLLocationAccuracyBestForNavigation;
GPS = CLActivityTypeAutomotiveNavigation;
pausesLocationUpdatesAutomatically
(将其设置为false)。它默认是启用的,对于导航应用,它应该保持启用状态。禁用此功能后,您将获得更多位置,这些位置与其他位置没有什么不同。所以,是的,iOS8和iOS9之间有很大的不同。如果你遇到了奇怪的地方,请检查上面的这些点。
发布于 2015-10-09 12:27:48
我不确定这就是整个故事,但在调查了两天后,我认为是这样的。
如果在任何时候重新创建locationManager,它将执行您所描述的操作(重复位置)。这在某种程度上是有意义的,如果你创建了一个新的locationManager或重新初始化你的当前位置,它将接收到你当前位置的另一组信息。我创建了一个玩具应用程序,在每次按下按钮时重新创建locationManager,并定期单击按钮,从而获得类似的结果。
如果locationManager失去网络连接(蜂窝信号和wifi),它就无法传输位置数据。简而言之,我认为每当设备失去互联网连接时,locationManager就会被销毁,而当它在片刻之后被重新创建时,它就会使用旧的坐标。为什么它会缓存这些值,以及时间签名是如何不正确的,这对我来说仍然是一个谜。
最后,我创建了一个toy app,它使用的代码与初始化它的locationManager时使用的代码相同(去掉了用于存储前面200个位置的代码)。它所做的就是在每次收到你的位置时在地图上放置一个别针。我开着它到处转,确实看到了不一致的位置,但并不完全像你所描述的那样。事实上,我确实看到了奇怪的行为,这让我认为这是iOS 9的错误,而不是您的代码。
在这一点上,考虑到到目前为止在iOS 9中发现的所有其他错误,我认为将这个错误归因于苹果是公平的。
发布于 2015-10-15 16:57:45
无法添加评论..
仍然只有通过设置distanceFilter才能正常工作
我接受你的回答:_locationManager.activityType = CLActivityTypeFitness; _locationManager.pausesLocationUpdatesAutomatically = YES;
还可以找到一些像这样的有线位置:
第一个完全等于第三个,为什么呢?
https://stackoverflow.com/questions/32838488
复制相似问题