Where Does Omio Store Tickets and Bookings?
Omio keeps bookings in your account with tickets cached in a private sandbox and Wallet passes for travel day.
Last updated
Omio bookings live server-side across trains, buses, flights, and ferries. The app sandbox caches upcoming trips, tickets, and login state. Live status renders from the same backend.
Multi-leg trips deserve an offline check before travel day. Open every segment once so each caches. Family bookings show under the purchaser account, so fellow travelers need the email copies.
Where Omio stores this, by platform
/data/data/com.goeuro.rosie
Private sandbox for cached tickets and session, under the legacy GoEuro package name. Bookings are account-side. Wallet passes cover offline gates.
/var/mobile/Containers/Data/Application/<guid>/Documents
Sandboxed container with the same account archive. Live updates need signal; cached tickets do not. Email confirmations backstop the app.
Frequently asked questions
Do Omio tickets work offline?
Tickets cache after first open, and Wallet passes work offline. Open each leg on Wi-Fi before departure. Confirmation emails carry PDF fallback when the app struggles.
How do I move Omio bookings to a new phone?
Log in and bookings return. The sandbox held cached tickets and session that rebuild on first view. Re-add Wallet passes on the new phone.
Notice an outdated path? Let us know.