No longer getting a list of beacons since switching to ESTSecureBeaconManager

Hello, since switching to ESTSecureBeaconManager I no longer get a list of beacons in - (void)beaconManager:(id)manager didRangeBeacons:(NSArray *)beacons inRegion:(CLBeaconRegion *)region. I have enabled the secure UUID on all of my beacons.

I do have a CLLocationManager created for handling a geo-fence but not beacons. That shouldn’t interfere right?

Hi James,

Please try restarting your phone and let me know if it helped. Also, it would be great if you could let us know which version of the SDK you’re using.

Keep in touch.

The CLLocationManager shouldn’t interfere.

Just checking: did you set up your app token via the ESTCloudManager's setupAppId:andAppToken:?

Estimote SDK 3.2.6 via CocoaPods
Restarting my phone doesn’t help

I’ve searched the SDK codebase on github for ESTCloudManager and it’s not mentioned anywhere that it’s required if I want to use secure beacons. In my case I was converting a CLLocation-based app to the Estimote SDK so I read your migration guide. It should mention there and in the API page for ESTSecureBeaconManager that authenticating to ESTCloudManager is required.

My app is working as expected now :+1:

1 Like

Yup, great feedback about the documentation, we’ll work on that. Thanks for sharing!

Hello, I’m getting the same kinds of errors by switching ESTBeaconManager to ESTSecureBeaconManager. However I’m using [ESTConfig setupAppID:@“XXX” andAppToken:@“XXXX”]; to connect to EstimoteCloud. Did I miss something?

What errors exactly do you have in mind? Have you enabled Secure UUID on your beacons?

Yes, Secure UUID is enabled on my beacons and I don’t receive any list of beacons in -(void)beaconManager:(id)manager didEnterRegion:(CLBeaconRegion *)region. But everything works with ESTBeaconManager.

So you’re using monitoring? Can you implement the “monitoringDidFail” delegate and see if it throws anything? Can you also try completely removing your app from your device, and redeploying?

Thanks for your help, it’s seems that remove the app and restart the phone was the solution. :grin:

1 Like

Hello, I’m facing with similar issue in version 3.8.1. Since I’ve turned on Secure UUID, and changed ESTBeaconManager to ESTSecureBeaconManager, my app has stoped recognazing when it enters the region and stoped receiving list of beacons.

I’m providing appId and appToken with ESTConfig, I was trying to restart and redeploy app. But these actions didn’t help me. Also, I’ve tried with all fail methods but none of them was used by delegate. Only method ‘beaconManager(manager:, didStartMonitoringForRegion:’) was used.

It’s all seams to work fine since I don’t use scure UUID. Any suggestions?

Have you enabled Secure UUID on your beacons?

yes I did, I’ve also generated new UUID

Can you PM me your Estimote Account login? I’ll check our logs to see if there’s anything suspicious going on.