tree 65a2ca42e88181ea95be90aa446ef8c45a6057a4
parent 9f1a470e7c368d4d25fbd0e2bb27a7f901827738
author Sharad Binjola <31142146+sharadb-amazon@users.noreply.github.com> 1685048493 -0700
committer GitHub <noreply@github.com> 1685048493 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkb8ytCRBK7hj4Ov3rIwAAXQ8IAEM3GFtPykHxDxoJOVml/egU
 r2Mi9mstsD5+JGMOw0Z7pJgvazNIjUWfFK/6cD5NqPMevphni3MM7yY4RkRmcQwZ
 W4HD+V5TgWYFMalI0fpnwpYLpHuRwpEqoOSrDKPmkq4ML4+E15UVP3Cl27oMnuCr
 iFO78P0VTw+lJ1YVGLVEkW2iXHIM28IN3yRQG4OXGnhIhrsnWEmBiiQ5ZnZV7WF3
 7/RXhshuiaqHY+tfqq3e/3oV6KK7A8EzsA5XFvlwP8KjtrwrV0ND+mg3IwIjglHw
 JkSL6Z/H0URnzbFM/DhAooDGb2s84UGEvfXoQ86scu1QjPPSj1f0j7d+Yx9xVV0=
 =lfMa
 -----END PGP SIGNATURE-----
 

iOS tv-casting-app: Apply StackLocks and sequence callbacks (#26817)

* V1.0.0 branch 25023 fix (#110)

* Lock the SDK before interacting with it.

[Problem]

The Matter SDK assumes that the client will take a lock on the SDK prior to
interacting with any APIs. There is 1 Android function and several iOS functions
that do not take the lock prior to interacting with the SDK APIs.

There are also some functions that invoke the Matter SDK in a way that may
result in out-of-order callback invocation (e.g. the conceptual "started"
callback may be invoked after the conceptual "ended" callback).

[Solution]

Create utility functions that help ensure that the Matter SDK is invoked safely
and that callbacks are delivered in the correct order.

[Testing]

Performed local, manual testing with the 'tv-casting-app' example on iOS against
a Raspberry Pi running the 'tv-app'. Ran the certification test in the
'tv-casting-app' on iOS against the same Raspberry Pi.

* * Updating naming and parameter order for new CastingServerBridge APIs
* Refactored the Certification Tests to more fully exercise threading behavior

* * Updating the documentation for modified APIs

* Restyling

---------

Co-authored-by: Michael Douglas <125094815+domichae-amazon@users.noreply.github.com>