CBConnectPeripheralOptionEnableAutoReconnect option VS connect

In iOS17 this new option has been added in the peripheral connection option CBConnectPeripheralOptionEnableAutoReconnect The documentation states:

After a peripheral device connects, this setting enables the system to initiate a connection to the peer device automatically when the link drops. The system uses centralManager(_:didDisconnectPeripheral:timestamp:isReconnecting:error:) to notify the caller about the disconnection.

To get the same behavior I used to schedule a new connection after a disconnection depending on the error type. I'm trying to understands if the are more benefits using that flag instead the of "old" way.

Can someone clarify that?

Best,

Andrea

Hi Andrea, curious if you had any luck or a play around with this option? I've just discovered it myself, I'm scheduling a new connection in a similar way to you but also wondering if this is a better option!

All the best, Simon

Any learnings from this @DrAma78 ? Also curious to see if you have seen any impact from this boolean.

CBConnectPeripheralOptionEnableAutoReconnect option VS connect
 
 
Q