Handle legacy process event first on connection complete #11718
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is a proposed fix for mbed-os-example-ble issue 257.
SM control block doesn't get ready when calling user-defined on_connection_complete process event, so I move the legacy process event forward.
Tested with BLE_SM/BLE_GAP/BLE_Battery/BLE_GattServer on NRF52840_DK.
Updated:
This PR only fix
Error during SM::setLinkSecurity 4.
To make BLE SM example work,
onAdvertisingEnd()
should care if the connection is established, like this mbed-os-example-ble#265 does.Reviewers
Release Notes