We are developing devices that communicate with iOS using Bluetooth LE. Since there is a limit to the number of bonding information that can be stored on the device side, the device deletes the bonding information when the limit is reached. Then, there is an operational situation where the bonding information is deleted on the device side and remains on the iOS side. When this situation occurs, an Encryption Failure occurs at the time of reconnection, and the connection is immediately disconnected from iOS. Since there is no API to delete the remaining bonding information on the iOS side, it is not convenient for the user to delete the bonding information on the iOS setting screen. I would like to improve the usability for re-pairing. With the bonding information of the device remaining on the iOS side, is it possible for iOS to prompt "re-pairing" by taking the following action from the device? (It is possible to change the device side) ・Change the Bluetooth parameter setting value of the device side ・Change the response value to iOS Also, is it possible for iOS to "re-pair" with CoreBluetooth API when the bonding information of the device remains in iOS side? Also, in case of HOGP, when the bonding information of the device remains in iOS side, iOS always tries to connect and fails repeatedly when the device sends advertisement. When this situation occurs, is it possible to set up iOS not to connect with CoreBluetooth API or iOS setting?