LE Audio: CAP Initiator cannot handle any unexpected state changes #73083
Labels
area: Bluetooth Audio
area: Bluetooth
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
Describe the bug
The CAP initiator is very rigid in the way it works: It assumes that only the initiator is modifying the states, but if the unicast server e.g. modifies the metadata during the start procedure, i.e. it sends unexpected state changes (e.g. enabled -> enabled).
To Reproduce
Steps to reproduce the behavior:
tests/bsim/bluetooth/audio/src/cap_acceptor_test.c:unicast_stream_enabled_cb
to dobt_bap_stream_metadata
Expected behavior
Expect that the CAP initiator can at least handle trivial changes such as the metadata update. Other, actual, state changes are harder to handle.
Impact
Annoyance, as the procedure can likely be retried.
Logs and console output
Environment (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: