b2310b69bb
When the BT Tester gets the write response, it should not send the state change event, as the write response may come before the notifications, and in which case the state may not have changed. The BT Tester should always wait for the state change notification before sending the event. Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| addr | ||
| adv | ||
| at | ||
| audio | ||
| bluetooth | ||
| bt_crypto | ||
| bt_crypto_ccm | ||
| buf | ||
| common/testlib | ||
| controller | ||
| df | ||
| gap | ||
| gatt | ||
| hci | ||
| hci_codecs_info | ||
| hci_prop_evt | ||
| hci_uart_async | ||
| host | ||
| host_config_variants | ||
| host_long_adv_recv | ||
| init | ||
| l2cap | ||
| mesh | ||
| mesh_shell | ||
| qualification | ||
| shell | ||
| smp | ||
| tester | ||
| uuid | ||