ChromeOS / Android App: Zero-delay "Try Again" error during Lego Boost BLE discovery (Nearby Devices permission mismatch?)

Abierto
#703 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, javascript

Línea de trabajo

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”.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

  1. Install Scratch Android app on a Chromebook running a recent ChromeOS version.
  2. Ensure Location Access is enabled for the system. Ensure Bluetooth is enabled.
  3. Grant "Nearby Devices" permissions to the app as requested by the system.
  4. Open a project, add the Lego Boost extension, and click "Start Searching".
  5. 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

Lenguaje dominante
JavaScript
Estrellas
310
Forks
299
Merge medio
19 h 41 min
PR fusionados (30 d)
14

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de scratchfoundation/scratch-editor

Todos los issues de scratchfoundation/scratch-editor

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.