This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

iOS 6 update break my app.

There are two issues that I experienced after upgrading to iOS 6. 

1. For some devices, when a peripheral was discovered, the UUID of the CBPeripheral is still nil. I didn't experience  this problem in iOS5

2. Another problem is that when I call cancelPeriphralConnection, my bluetooth board doesn't go back advertising right away. It waits for a certain period of time before it starts advertising again. It seems to me that I am not the only that has experienced this problem. 

Does anyone know a workaround for this? in my use scenario, I need the board to start advertising right away after it was disconnected. 
  • Hi Xin,

    1. We have noticed the same thing, and it seems to be a bug with iOS6s device-UUID generation. It happens with some IEEE-addresses. For now, try to change the address of the device using Flash Programmer (secondary address)

    2. This we have not observed, but we have not looked for it. Will get back to you if we figure it out. A workaround (albeit perhaps a nasty one) is to implement a char property on the BLE device that will terminate the connection from the peripheral side.

    Best regards,
    Aslak 

  • After upgrade my 4s to ios6, I have also noticed some usual problems that have been occurring. I started to document them in this thread: http://e2e.ti.com/support/low_power_rf/f/538/p/215903/761793.aspx#761793 but then I found this.

    The problems I noticed were:

    • Device name was Null after connecting to the keyfob
    • characteristic string descriptions were coming in corrupted when scanning for all descriptors in a characteristic.
    I'd like to not downgrade my device to ios 6 because it doesnt seem like an easy thing to do.  
  • can you be more specific about what address should we change? Is there a known range of address which is effected by this iOS6 bug?