Open
Description
Observed behavior
- Two devices on the same external network can sync and communicate
- Two devices connected on one of the device's hotspot cannot sync, but requests do succeed from the foreground process
Errors and logs
Requests like at the beginning of a sync timeout. Sync tasks will appear to stop at:
Run user program, change dir and execute entrypoint
Expected behavior
Unless this is a Android hotspot specific restraint, no difference in this behavior would be ideal.
User-facing consequences
The caveat isn't helpful in offline scenarios, because a third hotspot or wifi AP device is required to facilitate syncing
Steps to reproduce
- Install Device A with Kolibri for Android
- Set up a full facility on Device A
- Turn on Device A's hotspot
- Install Device B with Kolibri for Android
- Forget any currently available Wifi APs on Device B
- Connect Device B to Device A's hotspot
- Attempt to join Device A's facility from the setup wizard on Device B
- Observe the device is discovered
- Observe the import task stalls at 0%
Context
Kolibri for Android 0.16.1