RE: Cancel of pairing causes app_error_handler to be called

Robert Blasutig — Tue, 12 May 2015 07:48:26 GMT

Gotcha. I have modified this code like so:

switch (event_result)
	{
		case BLE_GAP_SEC_STATUS_PASSKEY_ENTRY_FAILED:
		{
			err_code = sd_ble_gap_disconnect(m_conn_handle , BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
			APP_ERROR_CHECK(err_code);
			return NRF_SUCCESS;
		}
		default:
			APP_ERROR_CHECK(event_result);
	}

And it is behaving as desired.

RE: Cancel of pairing causes app_error_handler to be called

Susheel Nuguru — Mon, 11 May 2015 11:29:36 GMT

Hi,

When you say cancel while pairing, then it is a failure of the authentication procedure. in the application you are using, the event callback function assumes that there will be no error in the paring sequence. This is just an example and does not handle all possible errors that could happen. If you can handle the error at line APP_ERROR_CHECK(event_result); then this app would know about this failure and handle accordingly.

static uint32_t device_manager_evt_handler(dm_handle_t const    * p_handle,
                                           dm_event_t const     * p_event,
                                           ret_code_t        event_result)
{
    uint32_t err_code = NRF_SUCCESS;

    m_dm_handle = *p_handle;
    APP_ERROR_CHECK(event_result); //handle this
 ...
}