Xcode 6 and IOS 8

If I compile my app with Xcode 5.1.1 and run on IOS 8 device, everything works fine as expected, but if I use Xcode 6, I can't detect or monitor iBeacons.
If I deploy in Xcode 5 the app asks for permission to use Location, but if I use Xcode 6 it doesn't ask anything.
Is anyone experiencing the same problem?

Hi Marco,

Are you using the latest Estimote SDK, 2.1.1?


Yes, I'm using 2.1.1

Hi I have the same problem. My own app and the Example app does both not work after upgrading the phone to iOS8 Also using the latest SDK

Hi Again. In case you have not already figured it out, you have to allow the app to access the location services in iOS 8. Like here: https://community.estimote.com/hc/en-us/articles/203393036-Estimote-SDK-and-iOS-8-Location-Services
Then it works as before. You will also have to do it in the examples project since Estimote seem to have forgotten this :-)

Marco - Lars is right, in iOS 8 you need to perform some additional steps to be able to use beacon ranging and monitoring.

Lars - thanks for pointing out that we need to update the Examples app, it's long overdue! (:

@Piotr Krawiec Just a wish: If you could do them in Swift as well it would be a great help.

Thanks to all!

Just updated the Examples on GitHub, should work fine on iOS 8 now.

@Lars - sure, definitely looking forward to making a Swift version! Luckily, the usage of the Estimote SDK doesn't differ much between Obj-C and Swift. In the meantime, if you have any Swift-specific questions, just ping me: piotr(at)estimote.com

I'm using the latest iOS SDK post iOS8 update, but i have a problem when Authorizing in the Example App.

To reproduce, I tap Authorize in navBar, complete app id and token text fields in ESTCloudAuthVC

After hitting "Done" on the keyboard and returning to the ESTViewController, I get an *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull integerValue]: unrecognized selector sent to instance 0x10c565cb0'

Hey Steve - we've just released an updated version of the SDK that fixes this bug. Feel free to check it out!