Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Misleading error message when phone is out of Bluetooth range of mesh device

Open
#3,629 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
53/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
mobile

Research direction

The report identifies the Bluetooth connection failure and shows the generic error text, but it does not name a source file or test. Start by locating where discoverServices failures are translated into the displayed connection message, then check whether the failure details can distinguish an out-of-range device. Done when that case shows specific guidance and existing connection errors remain accurate.

Written by the indexing model from the issue text.

Description

what happens

When my phone is out of bluetooth range from a meshcore device, I receive the following error message:

Image
Failed to connect!
- The PIN you entered may be wrong.
- Otherwise, try rebooting your MeshCore device and forgetting it from your Bluetooth settings.
FlutterBluePlusException | discoverServices | fbp-code: 6 | Device is disconnected
suggestion

Error message should be specific to bluetooth being out of range, not generic pin or reboot message. Example wording:

"Weak bluetooth signal. Please try bluetooth connection again when closer to your meshcore device."

details

iOS 26.6 13 mini MeshCore v1.50.0
WisMesh Pocket V2 x MeshCore v1.18.0 build 81dbae5
RAK4630 x RAK19003 x MeshCore v1.18.0 build 81dbae5

Dominant language
C
Stars
3.9k
Forks
1.5k
Avg merge
1d 1h
Merged PRs (30d)
26

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from meshcore-dev/MeshCore

All issues in meshcore-dev/MeshCore

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.