Strange kCLErrorDomain

Archive
1

Hey there,

Clem from France here,
I come here to ask you if you have ever find a The operation couldn’t be completed. (kCLErrorDomain error 5.) declaring and start monitoring regions.

It's completely weird, coz' I have 16 regions, 12 works very well but 4 doesn't...

I read few topics on Stack Overflow, and on other blog but didn't find any solution to solve my problem. Really annoying !

Thanks a lot for your help !

-- C.

2

Code part :
Ow, and for the code part, simply :

`ESTBeaconRegion *sochersHautPrincipal = [[ESTBeaconRegion alloc]initWithProximityUUID:self.projectUUID
major:self.beaconsMajor
minor:XXXX
identifier:@"Sochers Haut Principal"];

ESTBeaconRegion *sochersHautBis = [[ESTBeaconRegion alloc]initWithProximityUUID:self.projectUUID
major:self.beaconsMajor
minor:XXXX
identifier:@"Sochers Haut Secondaire"];

[self.beaconManager startMonitoringForRegion:sochersBasPrincipal];
[self.beaconManager startMonitoringForRegion:sochersBasBis];`

3

Hi Clem (:

My bet is, your app is still monitoring for some old regions that you've never stopped monitoring for, as these persist between app deployments. That's why you're hitting the 20 limit region (aka the kCLErrorDomain error 5).

Two solutions:
* delete the app from your device and re-deploy it, IIRC this should reset the list of monitored regions
* use CLLocationManager's "monitoredRegions" property to stop monitoring for these old regions

Let me know if this helps!