Repository navigation
v3.0.8
PinkCollab v3.0.8: preserve Android connections on foreground resume
Fixes
- Returning to the foreground keeps a running host WebSocket and its session subscriptions instead of replacing them. An in-progress connection or retry cycle keeps its current attempt count. Stopped connections restart, except hosts requiring authentication or a protocol upgrade.
- Default-network availability still replaces host connections, and explicit refresh or retry still reconnects. The existing WebSocket heartbeat remains responsible for detecting stale sockets.
- System-bar insets stay consistent when navigating between Tasks, Workspaces, and the directory browser. The shared app shell handles status-bar and navigation-bar padding without route-specific inset overrides.
Compatibility and upgrade
- Protocol 4 and the Gateway database schema are unchanged. Build or upgrade Android and the Gateway from the same release.
- Install the signed Android APK over the existing app to preserve pairings and app data; do not uninstall the production app.
- This does not provide indefinite Android background execution: Doze, process termination, and vendor battery restrictions can still interrupt connections.
- The npm launcher and all five platform packages use version 3.0.8. Update with
npm install -g pinkcollab@3.0.8.