You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lab: the iOS connect path verifies what it started, and both Android branches explain themselves
iOS: connect_phone launched the app with its own copy of the devicectl
line and returned success if the LAUNCH returned 0 - which says the app
started and nothing more, so a phone that never loaded an experiment was
reported as connected and failed later on "no data". It now goes through
device.py's launcher (which also carries the fallback for phones
devicectl cannot talk to) and then waits for the remote API, exactly as
Android does. The failure names where to look: the app's own
"-phyphoxBleConnect: no device advertising as X turned up within 60 s"
line in the device console, the Bluetooth permission, and whether the
installed build has the seam. Worth saying in the message because
-phyphoxBleConnect opens NO dialog by design - the app scans headlessly,
so "nothing visible happened" is not evidence of anything.
Android: the two failure branches had drifted. The hold branch reports
the first exception and keeps the whole output; the API branch still
tailed 300 characters, which is why the single failure of today's last
pass came back as "...within the connect timeout:
de.rwth_aachen.phyphox.BleCompatConnectTest:" and nothing else. Both go
through one explainer now.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments