Hi Kevin, Thank you for the detailed and clear answer. It confirms that our current approach, which persists CBPeer.identifier and uses it to recognize the same peripheral over the long term, is not supported. We will move away from it. Following your recommendation, we are evaluating a migration to AccessorySetupKit. Before we commit to it, I have a few follow-up questions: 1. Stability of the ASK identifierIs ASAccessory.bluetoothIdentifier expected to stay the same across device reboots and iOS updates for as long as the accessory remains authorized? Or are there known conditions under which it can change, such as resetting Bluetooth settings or reinstalling the app? 2. Identical accessories in the picker Our accessories all advertise the same service UUID and similar names. Several of them may be within range at the same time. Is there a recommended way to make sure the user picks the correct one? For example, can we limit discovery to nearby accessories, or customize the display items based on advertisement data? 3. Migrating existing users For users who already registered their accessory using the old identifier-based approach, is ASMigrationDisplayItem the intended way to move them over? Does it work even if the stored CBPeer.identifier has already changed after the iOS 27 update? Thank you again for your help. Best regards, ks-mwlk