Apple developer support could not answer my question which is the following:
How are Matter developers supposed to test accessory pairing, accessory communication and accessory discovery if the Console logs provided by Apple (iOS, MacOS, iPadOS) are encrypted, incomplete or straight up non-existent.
Current issue is mDNS-SD discovery, pairing and PAKE requests initialisation. Impossible to figure out why X or Y stopped on the Apple Device.
Chip-tool (provided by PROJECT-CHIP) acts 100% differently than iOS (Home) or iPadOS(Home).
Thank you
BigSoftwareDeveloper
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
Hello,
I've been working on a HomeKit accessory for a while now and sadly I've come across many many many issues...
One of them that I have no success solving for some time now is this one.
This is the message when I attempt to finish Pair Verify.
On my device i get: "Invalid Message Size"
and this are the logs I am able to get from Console (phone connected to mac).
As you can see, it says "Pair Verify complete" once and still do it once again.
On the second run, this happened:
Pair-verify client state 2 failed: -6727/0xFFFFE5B9 kNotFoundErr
I literally do not know where else to look and what to do, so I am turning around to these forums for help.
Thank you, I thank every response in advance.
This is the console (I could not find any other way than taking a picture):
default 23:04:56.561155+0100 homed Pair-setup client done -- server authenticated
default 23:04:56.565924+0100 homed PairStart, PairVerifyClient, 0x0 < >
default 23:04:56.566869+0100 homed Pair-verify client M1 -- start request
0x06 (State), 1 bytes, 01 |^|
0x03 (Public Key)
+0000: 6ba43809 8224736f 4fa0db8b ba5dc6a5 |k^8^^$soO^^^^]^^| (32 bytes)
+0010: 7bdb0d21 529db537 29b1dc78 b4f0e75e |{^^!R^^7)^^x^^^^|
default 23:04:56.567559+0100 homed [IP Accessory Server HomeServer bb:e6:89:6e:f4:fe] Sending POST request to '/pair-verify'
default 23:04:56.591376+0100 homed Pair-verify client M2 -- start response
0x06 (State), 1 bytes, 02 |^|
0x05 (EncryptedData)
+0000: b46ffd2d d2e9986f a38d1da3 be81688b |^o^-^^^o^^^^^^h^| (101 bytes)
+0010: abc8333e 000dd4af 1a64964c a25e38c0 |^^3>^^^^^d^L^^8^|
+0020: 8d29f979 8189d4b6 8bf950a6 7168f0d4 |^)^y^^^^^^P^qh^^|
+0030: cdb874d0 49660c34 fbe233ec 30c11db4 |^^t^If^4^^3^0^^^|
+0040: 95dbc535 5b0b36a7 6845c235 058f1978 |^^^5[^6^hE^5^^^x|
+0050: 3b276dfb ed203bad f718f8aa d11c14cb |;'m^^ ;^^^^^^^^^|
+0060: 02941df3 89 |^^^^^ |
0x03 (Public Key)
+0000: edee2194 419a6d37 f4db768e 66805123 |^^!^A^m7^^v^f^Q#| (32 bytes)
+0010: 8faf1bbf adc1ee7e c3616e63 5cd8bf47 |^^^^^^^~^anc\^^G|
default 23:04:56.598839+0100 homed Pair-verify client M3 -- finish request
0x05 (EncryptedData)
+0000: 13bfcf28 e724868b 454d631e 3b7fe909 |^^^(^$^^EMc^;^^^| (120 bytes)
+0010: 7aa0c82a acd0efc8 b066c475 965c75db |z^^*^^^^^f^u^\u^|
+0020: 82b95a4d 67f3bd46 108fc6bf 41075505 |^^ZMg^^F^^^^A^U^|
+0030: 5b7aba1d 5ff9b947 f94fb311 3626c548 |[z^^_^^G^O^^6&^H|
+0040: 5206c75f 6ce4c5cf 39046fa3 0725029c |R^^_l^^^9^o^^%^^|
+0050: c9bb1eaf f52829aa faff19f0 956b6daf |^^^^^()^^^^^^km^|
+0060: b964011d 4c8f14ec ca3d6282 6644cd30 |^d^^L^^^^=b^fD^0|
+0070: b0e90e7b 9540e613 |^^^{^@^^ |
0x06 (State), 1 bytes, 03 |^|
default 23:04:56.599023+0100 homed [IP Accessory Server HomeServer bb:e6:89:6e:f4:fe] Sending POST request to '/pair-verify'
default 23:04:56.608530+0100 homed Pair-verify client M4 -- finish response
0x06 (State), 1 bytes, 04 |^|
default 23:04:56.608678+0100 homed Pair-verify client done
default 23:04:56.633369+0100 homed PairStart, PairVerifyClient, 0x0 < >
default 23:04:56.633770+0100 homed Pair-verify client M1 -- start request
0x06 (State), 1 bytes, 01 |^|
0x03 (Public Key)
+0000: ecec4f6a cbab42ed edb1655d 6d9fc221 |^^Oj^^B^^^e]m^^!| (32 bytes)
+0010: 7f138226 7505b080 1343eb56 40ef5210 |^^^&u^^^^C^V@^R^|
default 23:04:56.634968+0100 homed [IP Accessory Server HomeServer bb:e6:89:6e:f4:fe] Sending POST request to '/pair-verify'
default 23:04:56.660928+0100 homed Pair-verify client M2 -- start response
0x06 (State), 1 bytes, 02 |^|
0x05 (EncryptedData)
+0000: 1a2bc1e9 50528654 8d83d8c8 13546716 |^+^^PR^T^^^^^Tg^| (101 bytes)
+0010: 360c6049 edea3274 e7205e7a aad7fdac |6^`I^^2t^ ^z^^^^|
+0020: ec5d72c6 0bf4b2b8 66ae05de 09271d7a |^]r^^^^^f^^^^'^z|
+0030: a7f90308 223ec79f 22f32923 a9d7f564 |^^^^">^^"^)#^^^d|
+0040: 9f51e53b a1ac7e57 aeb9cfb0 80627256 |^Q^;^^~W^^^^^brV|
+0050: 2ae1142d 617fb8aa 72e21d99 fc1bc2c5 |*^^-a^^^r^^^^^^^|
+0060: 9f09f839 9e |^^^9^ |
0x03 (Public Key)
+0000: edee2194 419a6d37 f4db768e 66805123 |^^!^A^m7^^v^f^Q#| (32 bytes)
+0010: 8faf1bbf adc1ee7e c3616e63 5cd8bf47 |^^^^^^^~^anc\^^G|
default 23:04:56.663680+0100 homed Pair-verify client state 2 failed: -6727/0xFFFFE5B9 kNotFoundErr
0x06 (State), 1 bytes, 02 |^|
0x05 (EncryptedData)
+0000: 1a2bc1e9 50528654 8d83d8c8 13546716 |^+^^PR^T^^^^^Tg^| (101 bytes)
+0010: 360c6049 edea3274 e7205e7a aad7fdac |6^`I^^2t^ ^z^^^^|
+0020: ec5d72c6 0bf4b2b8 66ae05de 09271d7a |^]r^^^^^f^^^^'^z|
+0030: a7f90308 223ec79f 22f32923 a9d7f564 |^^^^">^^"^)#^^^d|
+0040: 9f51e53b a1ac7e57 aeb9cfb0 80627256 |^Q^;^^~W^^^^^brV|
+0050: 2ae1142d 617fb8aa 72e21d99 fc1bc2c5 |*^^-a^^^r^^^^^^^|
+0060: 9f09f839 9e |^^^9^ |
0x03 (Public Key)
+0000: edee2194 419a6d37 f4db768e 66805123 |^^!^A^m7^^v^f^Q#| (32 bytes)
+0010: 8faf1bbf adc1ee7e c3616e63 5cd8bf47 |^^^^^^^~^anc\^^G|
error 23:04:56.665815+0100 homed [IP Accessory Server HomeServer bb:e6:89:6e:f4:fe] Failed to remove pairing with error Error Domain=HMErrorDomain Code=4 "Object not found" UserInfo={NSLocalizedDescription=Object not found}
Also to note: documentation is outdated...