Describe the bug
Bug report. After updating to MeshCore One 1.4.0, newly discovered repeaters no longer auto-resolve friendly names. They only display partial ID/hash. This worked in 1.3.x. Environment. MeshCore One 1.4.0 on iOS, firmware 1.17, RAK 1W V2 5V. Auto-Add Max Hop Limit is set to No Limit. Actual behavior. Discovered repeaters show only hashes unless manually resolved via the official app’s Request Name. Expected behavior, friendly names auto-populate as in previous versions. Steps to reproduce. Open MeshCore One 1.4.0, discover a new repeater, observe only hash shown with no automatic name resolution. Additional notes, repeaters respond to manual name requests in the official MeshCore iOS app, suggesting a client-side change in 1.4.
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):
- Device: [e.g. iPhone 14 Pro]
- OS: [e.g. iOS 26.2]
- Version [e.g. 0.1.0]
- Build [e.g. 18]
Additional context
Add any other context about the problem here.
Describe the bug
Bug report. After updating to MeshCore One 1.4.0, newly discovered repeaters no longer auto-resolve friendly names. They only display partial ID/hash. This worked in 1.3.x. Environment. MeshCore One 1.4.0 on iOS, firmware 1.17, RAK 1W V2 5V. Auto-Add Max Hop Limit is set to No Limit. Actual behavior. Discovered repeaters show only hashes unless manually resolved via the official app’s Request Name. Expected behavior, friendly names auto-populate as in previous versions. Steps to reproduce. Open MeshCore One 1.4.0, discover a new repeater, observe only hash shown with no automatic name resolution. Additional notes, repeaters respond to manual name requests in the official MeshCore iOS app, suggesting a client-side change in 1.4.
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):
Additional context
Add any other context about the problem here.