BLE: always return privacy info from NRF.getSecurityStatus() #2584
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ssievert42
force-pushed
the
ble_privacy_status_fix
branch
2 times, most recently
from
803c7b4 to
522534e
Compare
ssievert42
changed the title
regardless of connection state
ssievert42
force-pushed
the
ble_privacy_status_fix
branch
from
522534e to
79965f7
Compare
Contributor
Author
|
Just rebased onto master. |
Member
|
Thanks! Sorry I missed merging this earlier. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This fixes
NRF.getSecurityStatus()only returning privacy info while connected and makes it return privacy info regardless of connection state.I somehow missed this when adding BLE private address support.