This is a follow-up to Bug ID# 16647123. Behavior is as per design, i.e, feature. Per iBeacon spec, beacons are non-connectable and use all 30 bytes in adv payload. We consider this issue closed. If you have any questions or concern regarding this issue, please update your report directly (http://bugreport.apple.com/). Thank you for taking the time to notify us of this issue. Best Regards, Apple Developer Support Worldwide Developer Relations ************************************************************************** THE INFORMATION CONTAINED IN THIS MESSAGE IS UNDER NON-DISCLOSURE ************************************************************************** ------------------------------------------------------- Bug ID #: 16647123 Bug Title: Coexistence of iBeacon and connectable BLE peripheral‏ ------------------------------------------------------- <GMT17-Apr-2014 16:50:26GMT> qinghui tang: Summary: We want to develop a BLE device that can be used both as a connectable BLE peripheral and iBeacon device. To be able to connect with iOS device, BLE device needs to respond scan request from iOS devices with response data(such as TX power, name, etc). Meanwhile our BLE device periodically broadcasts iBeacon packets. But here comes the conflict part between the two. 1) If we disable scan response function of BLE device, then iOS App can find the iBeacon signal correct (distance, accuracy, etc), but our BLE device will not respond SCAN req from iOS device. 2) If we enable scan response function of BLE device, but the CoreLocation function locationManager:didRangeBeacons:inRegion show no beacon signal can be found. The difference between 1) and 2) is just commenting or uncommenting a single line in our BLE firmware source code, iOS App side is untouched: GAP_LE_Set_Scan_Response_Data (a function from Stonestreeone Bluetooth stack) It seems Apple designed iBeacon in a way to disallow a BLE device to be used as a BLE peripheral that can respond to BLE scan request _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com