BluetoothLE - Device Unavailable, Pairs but cant connect on some machines
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- desktop, operating-systems
Research direction
Start with the BluetoothLE SDK sample and reproduce the paired-but-unavailable condition on the machines described. Inspect the sample's connection path and reported device status, then document a confirmed cause or actionable debugging steps; the issue provides no file or test name.
Written by the indexing model from the issue text.
Description
Using your BluetoothLE example from the SDK, I was able to write a great UWP app for the Microchip RN4870 BT device and talk to it. Job done, right?
I sideloaded my app on another machine and it Paired, but would not Connect. I went back to your original BluetoothLE SDK app. Same issue. Paired, no connect. My development machine has 5.0 version BT, so I tried in on another 5.0 machine, a 4.xx machine.. all the same. Checked permissions, privacy, all that.
Argh..
How do I debug this condition using the SDK sample? I installed VS on a Surface Pro with a BT 4.xx modem and it fails there. Do you have any suggestions about what I can check in the code sample for why it gets thrown by cannot Connect, Status: Device Unavailable.
Thanks
- Dominant language
- JavaScript
- Stars
- 9.7k
- Forks
- 7.8k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/Windows-universal-samples
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
microsoft/Windows-universal-samples#1442 · 6 comments ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
microsoft/Windows-universal-samples#1440 · 3 comments · 1 reaction ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/Windows-universal-samples#1437 · 3 comments ·
All issues in microsoft/Windows-universal-samples
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100