Gatt Disconnect Action
Describes how to tear down a GATT when the platform or Rust core requests a disconnect.
Inheritors
Types
Link copied to clipboard
The GATT is still connecting (never reached STATE_CONNECTED). Clean up and close directly — do NOT call disconnectGatt(), because gatt.disconnect() on a never-connected GATT won't produce a STATE_DISCONNECTED callback, leaving the disconnect watchdog timer stuck and eventually triggering an unnecessary platform reset.
Link copied to clipboard
The GATT has an established connection. Go through the normal disconnectGatt() flow which calls gatt.disconnect() and relies on the STATE_DISCONNECTED callback for cleanup.