didDetermineState doesn't work with Secure UUID beacons

[benjaminhallock]

So I've tried to set this up, nothing is working.

1. Put appID and token in AppDelegate.
2. Enabled "Secured" in init method for Beacon Region.
3. Secure my Estimote, then start ranging.

What works is when you manual startRanging, then I get my secure Estimote.

What doesn't is when I notifyOnEntry or Display. didDeterminateState doesn't get called as usual. Secure UUID is what is stopping this.

[martinklimek]

Hi @benjaminhallock ,

Can you paste code when you start monitoring for secured beacons?

[benjaminhallock]

//This is called in the the viewDidLoad method.
-(void)setUpBeaconManagerAndRegions {
        self.beaconManager = [[ESTBeaconManager alloc] init];
        self.beaconManager.delegate = self;
        self.beaconRegion = [[ESTBeaconRegion alloc]initWithProximityUUID:ESTIMOTE_PROXIMITY_UUID identifier:@"Estimote" secured:YES];
        self.beaconRegion.notifyOnExit = YES;
        if ([_userDefaults boolForKey:sendNotifications]) {
            self.beaconRegion.notifyOnEntry = YES;
            self.beaconRegion.notifyEntryStateOnDisplay = NO;
        } else {
            self.beaconRegion.notifyOnEntry = NO;
            self.beaconRegion.notifyEntryStateOnDisplay = YES;
        }
        [self.beaconManager startMonitoringForRegion:self.beaconRegion];
}

[martinklimek]

Thanks for code @benjaminhallock, it looks fine at first glance. Can you tell me what device and iOS version you are using?

[benjaminhallock]

The biggest iPhone on the latest iOS.

[benjaminhallock]

This issue seems to be happening no matter what I do on 2.2.1.

Rolling back fixes the issue. I turn on display, didDetermineState is called.

[heypiotr]

We're aware of a bug in the didDetermineState method that prevents it from working correctly with Secure UUID beacons. That's the root cause of the issue here. Stay tuned for the fix.

[heypiotr]

Fixed in 3.0.