sb -iOS 7 iBeacon Bugreport

bugreport

Hello my fellow iBeacon enthusiast,

We´re writing you because we have identified a bug within iOS 7.1 that affects the bases functionality of all iBeacon related features. If you are not the iOS developer for this sensorberg account, please forward this email to him/her. 

To highlight the urgency of the bug we would like to ask you to file a bug report at https://bugreport.apple.com/ All you need is a developer Account with Apple.

We have filed a bugreport ourselves, the openrdar version can be found at http://openradar.appspot.com/radar?id=5822481810063360. Just recently we were also able to tape the bug in action: https://www.youtube.com/watch?v=6a6IJzaxxJg

Apple recommends to file bugs to highlight the urgency on certain bugs. We would like you to participate in this process so we get this bug solved as soon as possible, so we all can continue to build awesome iBeacon related apps!!!

Please fill the fields on bugreport.apple.com with these texts:
############################
New Bug->iOS

Classification:
     Serious Bug
Reproduceability:
    Always
Title:
    iBeacon detection stops after several days of uptime of the device
Description:
After using apps that rely on iBeacon ranging and monitoring and keeping the device turned on for several days, the iBeacon detection suddenly stops and no iBeacon beacons are beeing found by all apps on the device.

Steps to reproduce:
* Get an iBeacon beacon.
* Install the Airlocate Apple sample application and install it on your device. If neccesary configure it to range your specific proximity UUID.
* Do not restart the device for several days, keep coming back to Airlocate app. You can also use Apps downloaded from the App Store that provide ranging functionality such as Locate iB (https://itunes.apple.com/us/app/locate-for-ibeacon/id738709014?mt=8)
* keep bluetooth turned on
* keep the device turned on, do not reboot it

If you debug the Airlocate sample application, you will that - (void)locationManager:(CLLocationManager *)manager didRangeBeacons:(NSArray *)beacons inRegion:(CLBeaconRegion *)region is called every second, when a beacon is nearbly

Expected Results:
* Ranging should continuously provide the same output for a given beacon. It should display the beacon and show an aproximate distance.
* Underlying callbacks should be called as

Actual Results:
* after several days of uptime, ranging stops to function.
* If a computer and XCode is available, debugging the Airlocate sample app shows, that the - (void)locationManager:(CLLocationManager *)manager didRangeBeacons:(NSArray *)beacons inRegion:(CLBeaconRegion *)region callback is actually never called.
* Apps like Locate iB do not show any error, they simply do not show any beacons.

Configuration
We were able to gather reports of this behaviour in our company on iPad Air, iPhone 5, iPhone 5s, iPhone 5c, iPad 4

iOS Version/Build
iOS7.1

Additional Notes
Since restarting the device will be no solution we can offer to the customers of our application, this bug threads all plans to integrate iBeacon functionality in our application.
############################

We would like to thank you for taking the time, or giving your developer the time to file this bug report.

If you want, support the openrdar movement and copy your bugreport as well to http://openradar.appspot.com/. This will give other developers the chance to verify any bugs they find agains a public database.

We would appreciate any feedback. Please send us the IDs of your reported bugs so we can continue to get some direct response from Apple.