-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Describe the bug
During scanning of IPs present on the network the web platform is connected to, the web platform will sometimes connect twice to the headset, first using port 5555, and then using the random port between 30 000 and 49 999.
To Reproduce
Note that this happens randomly during the connection phase, but to manually trigger the bug:
Steps to reproduce the behavior:
- Make sure that the IP of the headset you are trying to connect is in the HEADSETS_IP variable of the .env configuration file
- start the application
- Once the application seeks to connect to the headset, immediately manually connect it using the command adb connect, and use port 5555.
- Observe that the connection seeking process didn't stop, and the application will eventually use the random port.
Expected behavior
The port search should stop the moment the connection to the headset is successful.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
This bug does not happen on all headsets, it specifically happens on the the blue headset with identifier 101.
Metadata
Metadata
Assignees
Labels
No labels