ChromeOS / Android App: Zero-delay "Try Again" error during Lego Boost BLE discovery (Nearby Devices permission mismatch?)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- android, javascript
- Domain
- embedded-iot, mobile-dev
Research direction
Start by reproducing the failure in the downloaded Scratch Android app on ChromeOS with the Lego Boost extension, using the listed ChromeOS and app versions. Check the Nearby Devices, location, and Bluetooth permission behavior during discovery; done means the app can scan for and connect to the Lego Boost Move Hub without immediately showing “Try Again”.
Written by the indexing model from the issue text.
Description
Expected Behavior
Successful connection to the Lego Boost Move Hub, using the Lego Boost extension.
Actual Behavior
When using the downloaded Scratch Android app on ChromeOS, attempting to scan for the Lego Boost Move Hub fails instantly. Clicking "Start Searching" immediately displays the "Try Again" screen with zero delay, suggesting a runtime sandbox block rather than an actual Bluetooth timeout.
Steps to Reproduce
- Install Scratch Android app on a Chromebook running a recent ChromeOS version.
- Ensure Location Access is enabled for the system. Ensure Bluetooth is enabled.
- Grant "Nearby Devices" permissions to the app as requested by the system.
- Open a project, add the Lego Boost extension, and click "Start Searching".
- The screen instantly defaults to "Try Again".
System Details
Scratch app version: 3.0.66-minSdk23
ChromeOS Version 152.0.7977.129 (Official Build) (64-bit)
on HP Elite c1030 Chromebook
- Dominant language
- JavaScript
- Stars
- 310
- Forks
- 299
- Avg merge
- 19h 41m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 scratchfoundation/scratch-editor
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
scratchfoundation/scratch-editor#754 ·
Maintainers usually reply within 1 day
-
spork
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
scratchfoundation/scratch-editor#646 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
scratchfoundation/scratch-editor#406 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
scratchfoundation/scratch-editor#750 · 1 comment ·
Maintainers usually reply within 1 day
-
Monitor context menus shrink the EditorPossibly taken @mxmou claimed this 3 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 50/100
scratchfoundation/scratch-editor#744 · 6 comments · 1 reaction ·
Maintainers usually reply within 1 day
All issues in scratchfoundation/scratch-editor
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 96/100
google/site-kit-wp#14102 ·
Maintainers usually reply within 2 days
-
area:growth priority:P1 type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
tecnologiasantos/bogoboom#66 ·
Maintainers usually reply within 1 day
-
desktop docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
npm/write-file-atomic#245 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ktwu01/benchmark-radar#1181 ·
Maintainers usually reply within 1 day