ios 18 quirks - Githubissues

ios wants to send a new kind of connection:

regular connection:

CLinkCnx-53: PairStart, PairVerifyClient, 0xC < System PerDevice >

Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-53: Pair-verify client M1 -- start request
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 53: PairVerify next (166 bytes)
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-53: Pair-verify client M2 -- start response
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-53: Pair-verify client M3 -- finish request
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 53: PairVerify next (9 bytes)
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-53: Pair-verify client M4 -- finish response
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-53: Pair-verify client done
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-53: Pairing completed
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-53: Open stream 'main'

second new connection:

CLinkCnx-54: PairStart, PairVerifyClient, 0x400004 < System HomeKit >
PV_Start: pairing data includes new field 25: bytearray(b'\x01')

mediaremoted[40] <Notice>: [MRDPPFSQS] Won't send PFSQ for ASE change

Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 54: PairVerify next (166 bytes)
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: Pair-verify client M2 -- start response
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 54: PairVerifyVerify: Not using RPI: CF 0x224 < iWiFi BTPipe OnDemand >, AF 0x0 < >
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: GetPairingIdentity finish: 0x8 < HomeKit >, 27aa61d4-3e47-4ec2-95b0-35c6b34ed624 (HomeKitLocalKey)
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Error>: CLinkCnx-54: ### Pair-verify client M2 failed: find peer failed, -25300/0xFFFF9D2C errSecItemNotFound
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: ### Pair-verify client state 2 failed: -25300/0xFFFF9D2C errSecItemNotFound
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: ### Pairing failed: -25300/0xFFFF9D2C errSecItemNotFound
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: ### Pairing failed: errSecItemNotFound
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 54: ### PairVerify client completion failed: errSecItemNotFound
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 54: Client PairSetup retry
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 54: Client state: CPVWait -> CPSStart
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 54: Client state: CPSStart -> CPSWait
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: Invalidate
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: Activate
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: PairStart, PairSetupClient, 0x1C < System PerDevice Transient >
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: Pair-setup client M1 -- start request
Jun 21 12:47:18 audiomxd(MediaExperience)[109] <Notice>: -FigRouteDiscoverer- discoverer_logAvailableRouteDetails: Available routes for clientName=mediaremoted, discovererType=Audio: [0].Speaker
Jun 21 12:47:18 audiomxd(MediaExperience)[109] <Notice>: -FigRouteDiscoverer- discoverer_logAvailableRouteDetails: There are no available routes for clientName=mediaremoted, discovererType=Control Only
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 54: PairSetup next (420 bytes)
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: Pair-setup client M2 -- start response
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54:
Jun 21 12:47:18 mediaremoted[40] <Notice>: [MRDNowPlayingOriginClient] Set: deviceInfo for <<private>>:
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: Pair-setup  client M3 -- verify request
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54:  |E/^%d;^^^^`^^^^l| <-------- what is this???
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 54: PairSetup next (12 bytes)
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: Pair-setup client M4 -- verify response
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: ### Pair-setup client wrong setup code
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: ### Pair-setup client state 0 failed: -6745/0xFFFFE5A7 kNotPreparedErr
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: ### Pairing failed: -6745/0xFFFFE5A7 kNotPreparedErr
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: CLinkCnx-54: ### Pairing failed: kNotPreparedErr
Jun 21 12:47:18 rapportd(CoreUtils)[94] <Notice>: 54: ### PairSetup client completion failed: kNotPreparedErr

I wonder what the "wrong setup code" is. We can detect this "scuffed" connection. Then I guess we can randomly try "setupcodes" until something works? In the iOS logs it is mentioned that the apple tv (in this case our fake one aswell) specifically uses a pin code length of "4" (as opposed to 8 or whatever the HAP standards actually require) .

I wonder if it is just the current 1234 code with 0s appended.

thiccaxe / CompanionGames

ios 18 quirks #11