DE← Home

Support

Legal noticePrivacyTerms of useApp support

Support

EntryCheck Mobile support

Help with mobile KORONA Entry admission checks on iPhone and iPad. EntryCheck Mobile requires iOS or iPadOS 17 or later, supports German and English, and is being prepared for the App Store. The app has not been released yet.

Translation notice

This English translation is provided for convenience. If there are any discrepancies, the German version is authoritative.

Contact

AmoSystems · Fabian Amos, Christburger Str. 15/2, 10405 Berlin, Germany. For questions about the app, contact info@fabianamos.com.

Please include the version and build from Settings → EntryCheck Mobile, your device model, iOS or iPadOS version, and the steps leading to the problem. Do not send passwords, configuration files or complete ticket lists. Use sample data and remove personal information from screenshots.

What do I need for real tickets?

You need your own authorised KORONA Entry API access and a network connection to your HTTPS ticket server. KORONA services, API access, server operation and any KORONA charges are separate from the app purchase. EntryCheck Mobile is an independent AmoSystems app.

The planned one-time price in the German App Store is €2.99. The app has not been released and is not yet available to download. There is no app subscription or in-app purchase. Local sample tickets let you explore the workflow without KORONA credentials.

How do I set up the connection?

Open Settings → Set up connection. Enter the server address, API username, password and a client identifier for this entrance device. You can optionally provide an entrance or organisational unit and a connection name. You can also import credentials from an ENV, JSON or CSV file you choose. The preview masks the password; Apply to form initially changes only the draft.

Check connection makes a real authenticated read request, even with demo mode enabled. It does not confirm permission to record entries. Save at the bottom of the connection form stores the validated settings in the iOS Keychain. Demo mode stays unchanged: turn off Demo with sample tickets in the settings overview to use real tickets. Mac credentials are not imported automatically.

How is an entry recorded?

Scan the code or choose Enter ticket number. Entry allowed confirms only the preliminary check. Your deliberate tap on Record entry (+1) requests an entry after a fresh server check. Wait for Entry recorded, then choose Next ticket.

The preliminary check expires after 60 seconds and when you leave the app. Offline, the app grants no new entry and does not queue automatic bookings. A displayed ticket number or scanned barcode alone does not prove admission validity.

What does an unconfirmed entry mean?

When the app warns that an entry may have been recorded, the change may have reached the server even though its reply is missing. The app does not automatically retry. The pending activity survives an app restart and prevents further changes to the same ticket on the same server.

Check the activity outside the app, for example in the server log. An increased usage counter alone is not sufficient when several devices are in use. Only then mark the externally checked activity as resolved under Activity. This manual resolution is not proof of a server booking.

How do I import ticket types?

Under Settings → Assign ticket types, edit item numbers and names manually or choose Import item CSV and select a file in Files. The preview initially selects every recognised item. Selected items are saved; deselected items from the same CSV are removed from existing mappings. Items outside the file are preserved. Existing names are replaced only when you enable the update option.

Save in the preview stores only the item mappings, including previous item edits, and closes settings. Credentials and demo mode stay unchanged. Cancel changes nothing. A CSV may contain up to 500 unique items and be no larger than 4 MiB. Item mappings are display labels only; API categories take priority and admission validity is unaffected.

The camera is unavailable or does not recognise the code

Allow camera access in system settings. Use sufficient light and hold the complete code steady in view. Enter ticket number is available whenever the scanner is ready. Leading zeros are preserved. The camera pauses when the app moves to the background.

The same code remaining in view does not immediately start another check. Move it clearly out of view or use Scan the same ticket again. This only enables scanning again; it does not record an entry.

Locks, activity and local data

More actions offers locking and unlocking with confirmation. Locking is intended only for tickets that are clearly unused. Unlocking does not reset usage counters or confirm admission validity. Payments and refunds take place outside the app.

Completed activities are removed after 30 days or can be deliberately deleted under Activity. Unconfirmed activities remain. If the log is damaged or saving fails, new bookings and administrative changes are blocked. Check device lock and free storage; do not uninstall the app to resolve pending bookings. The app does not provide a delete-all button for stored credentials.

Related information

EntryCheck Mobile · App privacy · Legal notice · Website privacy

Last updated: 11 November 2026