We’ve written before about why Triponaut is offline-first: your itinerary lives on your device, works in a plane and in a foreign airport with no roaming, and syncs when the connection comes back.
We’ve improved the cases - however unlikely they may be - where something goes wrong here.
The bug: a token that expired in silence
Sign-in sessions expire. That’s normal and correct. The queue now handles an expired session properly and recovers when you sign back in, and the queued changes go up when it does.
The principle: state you can see
Triponaut now surfaces three things:
Your session state — signed in, or needing to sign in again.
Upload trouble — changes waiting to go up, and whether something is wrong with getting them there. Queued changes remain on the device.
Changes the server refused. The rare case, and the one that most needs surfacing and offer a resolution option.
Bon voyage :)
Triponaut is offline-first and free to start. Get the app.