Feedback 2018-11-21

Today we are validating each weekday around 500 successful BoB MTB tickets (Movingo tickets, aztec code in app) in county of Västmanland (VL) and Sörmland (SR). SR was live summer of 2018 and VL was live late autumn 2018. Issues that has been discovered so far:

• Some ticket groups (sub ticket category's) had invalid end date (period pass tickets) causing them to return ”invalid expired ticket” in validation but in the app the ticket was still live as it should – issue solved, configuration.
• During ticket inspection with inspector app, some tickets show different valid zone relations – under investigation, probably also a configuration issue
• iPhones sometimes activates apple pay iWallet during ticket validation – possible solution is to disable NFC  when ticket app is in ”ticket view” displaying the Aztec code ticket
• Size of Aztec code too big? Under investigation. The optical reader sometimes shows difficulties reading big codes since some customers are using mobile phones with bigger screens, like tablets
• If a BoB subsystem is down during purchase, sub tickets can not be created since there is no successful handshake during ticket purchase – solved by making the system to ask again if sub ticket creation was not successful.

Notes & references

Regarding last feedback point best practice initiated/created within Movingo project - Ticket refresh handling