Overview
If you opt for Offline Activation, and wish to postpone the unveiling of the QR code until closer to your event, you may adjust the actual offline activation date via the back-office.
Previously, different real activation time were visible depending on the spectators online presence :
- All spectators who accessed the app prior to the previous activation time and maintained an online connection received the updated activation.
- Conversely, those users who either did not open their app or remained offline subsequent to the update will have their tickets activated based on the earlier activation time.
New behaviour
If you enable the application setting "Enable force synchronization before activation" (force.sync.latest-activation-time), you can overcome this situation by requiring the mobile app to synchronize with the back-end before executing activation.
If the param is NOT enabled, the mobile app and the offline activation will behave as currently.
If the param is enabled, when the mobile app is opened, it will take into account : the real time, the old activation & new times, the phone connectivity status (offline or online) before activating the ticket.
If real time is BEFORE old activation time
If online, the mobile app will fetch the newest activation time (sync with back-end) => the ticket will be activated based on newest activation time
If offline, no sync with back-end => the ticket will be activated based on the old activation time
If real time is AFTER old activation time
If online, prior to activation, the mobile app will fetch the newest activation time => the ticket will be activated based on newest activation time
If offline OR weak internet (sync timeout leading to multiple failed attempts) => the ticket will be activated based on the old activation time
Limitations
We're introducing an online-check in the middle of the offline mode. Therefore, this round-trip between mobile and back-end will introduce a small delay in the actual QR code reveal. This delay will exist but is meaningless as spectators never know the configured activation time.
In case the spectator stays offline the whole time and open app, the mobile app won't get the newest activation time and the ticket will still activated with old activation time.
In case of poor internet and/or mobile is not able to sync with backend (timeout +multiple attempts failed so about 30s delay), mobile app won't get the newest activation time and the ticket will still activated with old activation time.
