iBeacon changes from 7.0 to 7.1.1
iBeacon changes from 7.0 to 7.1.1
- Subject: iBeacon changes from 7.0 to 7.1.1
- From: Spero Koulouras <email@hidden>
- Date: Wed, 30 Apr 2014 09:33:15 -0700
We've built a custom peripheral and had iBeacons working with iOS 7.0. With the update to 7.1.1 something appears to be broken and we have filed bug report 16769559 with the details.
It seems that the inclusion of Manufacturic Specific data in the scan response which the peripheral sends in response to a Scan Request from iOS blocks the iOS device from recognizing our beacon.
Our peripheral sends an ADV packet which contains the beacon proximity uuid, major and minor correctly. This is seen by the iOS device and we can correctly go in/out of range, distance can be discovered, etc. The iBeacon functionality will allow our app to get launched whenever we come in range of our periperal. That's great.
Unfortunately, our app relies on a MANUFACTURER SPECIFIC element which we embed in a Scan Response packet. In iOS 7.0 this did not cause any problems, however in 7.1.1 our devices are no longer detected as beacons. Removing the mfg specific element from the scan response allows iBeacons to work, but causes problems for our app.
Anyone else dealing with this?
Spero Koulouras (408) 874-6331
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden