Account and event wrap-up3 min read

Troubleshoot by version and symptom

Start diagnosis from the symptom and keep enough evidence. App version, device model and connection path help distinguish configuration, compatibility and service problems.

Version reference: Android 3.0.3 · iOS/iPadOS 1.2.1

Follow the section for your platform. Screenshots show native UI with demo data; menus depend on version, plan and device. Test-build features may not yet be in the public release.

Content reviewed: 2026-10-18

Before you begin

Record version/build, platform, device model, incident time and the last step. Do not include passwords, JWTs, Secret Keys or guest QRs in public reports.

Move devices safely — Workflow diagram. Optional steps depend on event configuration.

Android steps

1Camera: check permission, source, cable/power and model. Test a simple still before motion/filters.
2Printing: check method/driver, media, queue and physical output. QR/upload: check connectivity, session status and access period.
3Sign-in/devices: check the account and active-device list. Payment: record the same transaction reference before retrying.
4Use available help/diagnostics and share the report through official support. Preserve unuploaded media.

Android Settings. Native UI on a physical Android tablet with demo data.

iPhone and iPad steps

1Check version/build and whether the installation is from App Store or TestFlight. Test-build features may not be in the public release.
2Camera/printer: check iOS permissions, source/connection path and model guidance. Test real equipment; the simulator does not establish hardware compatibility.
3QR/upload: check Offline Mode, saving, connectivity and output status. Sign-in: use the offered verification/revoke flow.
4Keep the error message and available diagnostics. Do not begin by uninstalling when results are still local.

iPad Settings. Native SwiftUI UI on iPad Simulator with demo data.

Check the result

Operator check

The report includes reproduction steps and relevant evidence while preserving user results.

If something goes wrong

Symptom	Next step
Guide steps do not match the app	Choose the correct platform and compare the guide version reference with the installed build. Update through the distribution channel in use.
Only one model fails	Include model, firmware, cable/hub and failure stage. Do not change every setting at once.

Android steps

1Camera: check permission, source, cable/power and model. Test a simple still before motion/filters.

2Printing: check method/driver, media, queue and physical output. QR/upload: check connectivity, session status and access period.

3Sign-in/devices: check the account and active-device list. Payment: record the same transaction reference before retrying.

4Use available help/diagnostics and share the report through official support. Preserve unuploaded media.

Android Settings. Native UI on a physical Android tablet with demo data.

iPhone and iPad steps

1Check version/build and whether the installation is from App Store or TestFlight. Test-build features may not be in the public release.

2Camera/printer: check iOS permissions, source/connection path and model guidance. Test real equipment; the simulator does not establish hardware compatibility.

3QR/upload: check Offline Mode, saving, connectivity and output status. Sign-in: use the offered verification/revoke flow.

4Keep the error message and available diagnostics. Do not begin by uninstalling when results are still local.

iPad Settings. Native SwiftUI UI on iPad Simulator with demo data.

Symptom

Next step

Guide steps do not match the app

Choose the correct platform and compare the guide version reference with the installed build. Update through the distribution channel in use.

Only one model fails

Include model, firmware, cable/hub and failure stage. Do not change every setting at once.