beaconManager:didDetermineState:forRegion: returns CLBeaconRegion instead of ESTBeaconRegion

Archive
1

I've found (thus far) that didDetermineState: ... is the only ESTBeaconManagerDelegate methods that's signature is ESTBeaconRegion but in fact returns a CLBeaconRegion object.

I maintain a dictionary keyed on ESTBeaconRegion which value equates to the ESTBeacon for the given region. Getting back a CLBeaconRegion causes my dictionary query to fail on objectForKey:. I can work around this by converting the incoming CLBeaconRegion to a ESTBeaconRegion, but thought you all would appreciate knowing in order to fix for future releases.

2

Eric, thanks for pointing this out! We'll look into changing that.

3

FYI, found that didStartMonitoringRegion: returns CLBeaconRegion * as well.

4

Noted, thanks again!