Make pairing BroadcastReceiver optional#641
Merged
philips77 merged 2 commits intoNordicSemiconductor:mainfrom Feb 5, 2026
Merged
Make pairing BroadcastReceiver optional#641philips77 merged 2 commits intoNordicSemiconductor:mainfrom
philips77 merged 2 commits intoNordicSemiconductor:mainfrom
Conversation
Member
|
Interesting approach. Indeed, by eliminating registering the receiver, you eliminate the issue. One thing - I think it would be better to always unregister the receiver and ignore an error, so that method is called only once per connection. |
Contributor
Author
|
Sure, that makes sense. Done! |
Contributor
Author
|
Hi @philips77 just checking in to see if you're willing to merge this. |
Member
|
Hi, sorry, I was busy with something else. Let's merge. |
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
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.
I wonder if you would be open to this PR?
This is ultimately just a workaround for #616, but that issue is very hard to debug. My use case is making repeated connections to many different devices (fetching time series data from a fleet of sensors) without any pairing. This will fix the problem for me and anyone who has a similar setup, but should be totally transparent to anyone else.