tree 0a03406a197f372ce47ccb562b43d1f159a526e1
parent 24279121f2afcdc24ba750d6dc81ecbf42c27609
author Boris Zbarsky <bzbarsky@apple.com> 1685068201 -0400
committer GitHub <noreply@github.com> 1685068201 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkcBmpCRBK7hj4Ov3rIwAAAlkIAJgbpwlP88bjQH8jTsS253zq
 BaeFUtlFyVWRkFDEWs/Mw/Q5Gcv0XekEQ3Z7maL1YMnZxBmvBgFJxssjfuRAgGTD
 xDi3r4XiTX1NHeVKuSoDnRdV8PoInHcstHDZn6Ez7xtwv3ilg6abhdWse0MDFk/k
 +LD+6wFHnCZfyL/cQHdn2/BRaSJRyT3hpHn9MTUaKvstC445r7bJuld7mnWYyKyI
 WuEfHwHwpdcnq2dZzsZg/zgCd/tdoNLadzsNY+TZSyH6XWt2psnE3IbfDSCa1fGO
 /pKwveQlsnSMZQNyhprqSLvkXVP07FVTdy9sUBt66R5ZWIIMgGD9lTRWdx1dh/g=
 =C1ch
 -----END PGP SIGNATURE-----
 

Fix ordering issue with subscribeToAttributesWithEndpointID over XPC. (#26850)

We had an extra queue hop for reports compared with the subscriptionEstablished
notification, so the API consumer could get subscriptionEstablished before
getting all the priming reports.

The fix is to just ensure that the code flows the same way, in terms of queue
dispatch, for both priming reports and subscriptionEstablished.