bug: v/79667 When deleting a GATTC instance, the Advanced API identifies clients based on their device address. If an application creates two GATTC instances with the same device address, and attempts to delete the second instance before the server has returned the asynchronous callback for the first deletion, both deletion operations will effectively target the same underlying GATTC instance due to the identical device address. Signed-off-by: jialu <jialu@xiaomi.com> |
||
|---|---|---|
| .. | ||
| feature_async | ||
| include | ||
| jidl | ||
| src | ||