I had the same problem before and the answer was: I just forgot to call:
[self.locationManager startMonitoringForRegion:beaconRegion]
At first, I mistakenly suggested that if you start to hesitate:
[self.locationManager startRangingBeaconsInRegion:beaconRegion]
... and getting data for rssi, accuracy and UUID in the method locationManager:didRangeBeacons:inRegion:, CLLocationManager should be able to find out that the phone is in this region, but apparently not. Therefore, when querying the state using:
[self.locationManager requestStateForRegion:beaconRegion]
I got CLRegionStateUnknownfor this area in locationManager:didDetermineState:forRegion:, like you.
source
share