You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PurgeReadClientContainers in MTRBaseDevice.mm. Might be able to track the MTRBaseDevice and hence the controller in the MTRReadClientContainer to use that to make things safe.
CauseReadClientFailure in MTRBaseDevice.mm (might be OK because unit-test-only).
The readAttribute*WithClusterStateCache APIs on MTRBaseClusters (indirectly, via the callback bridge constructor it uses). We might be able to use the controller of the MTRBaseDevice to make these safe.
readAttributePathWithEndpointID on MTRClusterStateCacheContainer. We might be able to make this safe by having it store the controller or MTRBaseDevice it's associated with.
We've had issues where things get queued to the Matter dispatch queue while it's
not running, and then when we start it up again those things run too early in
startup and break in interesting ways.
The fix is to make sure we only queue things to the Matter dispatch queue when
they're associated with a currently-running controller.
Fixesproject-chip#22847
…g. (#23859)
We've had issues where things get queued to the Matter dispatch queue while it's
not running, and then when we start it up again those things run too early in
startup and break in interesting ways.
The fix is to make sure we only queue things to the Matter dispatch queue when
they're associated with a currently-running controller.
Fixes#22847
Reproduction steps
We should be going through a controller and checking isRunning; otherwise we have no idea whether the queue is even enabled.
Platform
darwin
Platform Version(s)
No response
Type
Manually tested with SDK
(Optional) If manually tested please explain why this is only manually tested
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: