Overview
The ticket scanner can be installed on a phone or tablet as an app, and once installed it keeps working with no network at all — it decides admissions on the device itself and sends them to the server when the connection returns.
There is one rule that makes the difference between a door that works and one that doesn’t: install it, open it once while online, and pick the event. Everything after that is automatic.
This is the offline and installation guide. For permissions, roles and day-to-day scanning, see the Ticket Scanner article.
Before you start
A secure (HTTPS) address
Offline support is refused on an insecure connection. Your normal Stageboxx address already qualifies.
A staff account with scanner access
Without it the scanner sends you to the login page.
Camera permission
Granted per app. An installed app asks again, even if the browser already had permission.
One launch while online
This is when the device downloads the event's admit-list. Offline before that, it can check nothing.
Install it on a door device
iPhone and iPad — Safari only
Open the scanner in Safari and log in. Tap Share (the square with the arrow), then choose “Lägg till på hemskärmen”. Open the new icon and it launches straight into the scanner. Chrome and Firefox on iPhone cannot install web apps — it has to be Safari.
Android — Chrome
Open the scanner and log in. Accept the install prompt when it appears, or open the browser menu and choose “Install app”.
Or from inside the scanner
There is an install row in Settings (the cog). On Android it installs directly; on iOS it shows you where the Share option is, because iOS gives web pages no way to install themselves.
The installed app starts empty
This catches people out. The installed app does not share its login, its settings, or the downloaded ticket list with the browser you installed it from. Expect to log in again and choose the event again inside the installed app — and do it while online. A device that was only ever set up in the browser has nothing stored in the app.
First launch
Log in
Enter the email address, then tap “Jag har ett lösenord” to reveal the password field. The login asks for the address first.
Choose the event
You are asked which event this device is for. It stays on that event until you change it — the scanner never guesses, not even when only one event is available, because scanning a queue into the wrong show is the mistake this prevents.
Wait a moment while online
The device downloads the ticket list for that event. Until it has, it cannot check tickets offline.
Changing event
Close the scanner and confirm the change. Two refusals are deliberate:
- Offline — the event list cannot be fetched, so the device keeps the event it already has. Losing a working door mid-queue, in exchange for nothing, is worse.
- Nothing else to change to — if the only event available is the one you are on, it says so rather than offering a choice that does nothing.
Working offline
While offline you will see one of two banners. They mean quite different things:
“Offline — beslut fattas på den här enheten”
The ticket list is on the device and it is deciding by itself. This is the good state. It also shows how old the list is.
“Offline — enheten kan inte kontrollera biljetter”
There is no list for this event, so nothing can be checked. Get online once with the event selected, then try again.
What each result means
Godkänd — approved
Valid, first use. Let them in.
Redan använd — already used
Already scanned, either on this device or on another before the list was built.
Makulerad — voided
The ticket was cancelled.
Biljett hittades inte — not found
Not on this event’s list.
Fel evenemang — wrong event
A real ticket, for a different show.
Kan inte kontrolleras — cannot be checked
Not the same as invalid. The device could not verify this one — a typed code, or a signature it cannot confirm offline. You can admit the person anyway; the decision is recorded as a human one, not the system’s, and the server is told exactly that when the connection returns.
Scans waiting to be sent
The scanner shows how many admissions are still to be sent. This is normal while offline. They send themselves when the connection returns, carrying the time the person actually walked in — not the time the network came back, so your reports stay accurate.
Do not delete and reinstall the app while that counter is above zero — those admissions have not reached the server yet.
What does not work offline
Stated plainly, so nobody discovers it at a door:
Scanning and admitting
Works. This is the whole point.
Group check-in from a scan
Not offered offline. The scanner shows how many are in the party and how many are admitted, but when offline scan each ticket individually.
The ticket list tab
Empty offline. It reads the list live from the server.
The counters (checked in / sold / remaining)
Show zero offline, even while the device is happily admitting people.
Searching by name or email
Not available offline — by design. See below.
Why there is no offline name search
What the device stores for each ticket is deliberately minimal: whether it is used or cancelled, the ticket type, and codes that cannot be read back. No names, no email addresses, no ticket numbers. A door phone that is lost or stolen therefore reveals nothing about who was attending. An offline attendee list would mean storing personal data on every staff device, which is a trade we have chosen not to make. The fallback is typing the ticket code, which works offline.
Keeping the app up to date
The scanner never changes its own code while you are working. A device three hours into a shift will not have the app shift underneath it. Updates apply when the app is launched: a new version downloads quietly in the background, and the next launch applies it.
After an update is released, fully close the app and open it twice. The first launch collects the update; the second runs it.
If a device still behaves as though nothing changed, delete it from the home screen and install it again — a fresh install has nothing old to keep. Only do this when there are no scans waiting to be sent.
What the device keeps, and for how long
The event’s ticket list
Until 24 hours after the event ends. Doors at 23:00 means the show runs past midnight and staff reconcile the next morning.
An event with no end date
Removed 7 days after the last successful sync. An event still in use keeps its list; one abandoned a week ago does not.
Admissions made on the device
Kept until the server confirms them, so force-quitting mid-event loses nothing.
If something is wrong
The camera opens but nothing scans
Make sure the device is on the current version — fully close the app and open it twice.
“Enheten kan inte kontrollera biljetter”
The device has no list for this event. Get online once with the event selected.
No offline banner at all
The device has not noticed it is offline. A network that is connected but has no route out is the usual cause — switch WiFi off so it is unambiguous.
Everything says wrong event
The device is locked to a different show. Change the event.
The camera will not start
Check camera permission for the installed app specifically — it is separate from the browser’s. Then choose the camera in Settings.
Setting up a venue
Install on each door device, while online
Do the install itself with a working connection.
Log in inside the installed app
The app does not inherit the browser’s login.
Select the event and wait for the banner to clear
This is the download that makes offline possible.
Grant camera permission and pick the camera
Rear camera, on the device that will be held at the door.
Switch the network off and scan one real ticket
The banner should say decisions are being made on this device, and the scan should be admitted.
Switch the network back on
Confirm the waiting-scans counter returns to zero.
Do not skip step five. It is the only step that proves the device will work when the network fails — and the step that has caught every offline problem so far.