Table of Contents

maxLevel	3

June 25, 2024

Standardizing mobile logs about Spectator

...

Previous Action	NEW Action	NEW Message
user.authenticated	spectator.authenticated	Spectator authenticated
user.signed-in	spectator.login	Spectator successfully logged in
user.signed.out	spectator.logout	Spectator successfully logged out
system.force-log-out	spectator.logout.forced	Spectator has been automatically logged out from the device (expired session or maximum number of session reached)
user.password.reminder	spectator.password.reminder	Spectator requested password reset
user.max-active-session.reached	spectator.devices.maximum.active.reached	Spectator reached the maximum number of active devices
user.max-devices.reached	spectator.devices.maximum.allowed.reached	Spectator reached the maximum number of allowed devices
spectator.screen.recording	spectator.screen.recording	Spectator recorded a video
user.screenshot.taken	spectator.screen.screenshot	Spectator took a screenshot

...

TIXNGO now collects and categorizes the origin of each spectator. The possible origins include:

REGISTRATION: Spectator registered independently.
TICKET_INJECTION or PRIVILEGE_INJECTION: Spectator was acquired through injection.
TICKET_TRANSFER: Spectator was acquired through a ticket transfer.

Additionally, for spectators acquired through TICKET_TRANSFER, TIXNGO will also store the referring spectator's information.

Spectator origin and referral data are available in the Spectators export.

Changes to the Spectators List screen:

The creation date field is now replaced by the first login date. The creation date is still available in the export file.
The first login date will be null if the spectator has never logged into the ticket app.
Once a spectator logs into the ticket app, the first login date will be recorded and remain unchanged regardless of subsequent operations such as logout, forced logout, or account locking.

Image Added

...