- The app versions remain the same:
iOS: Native: 2.1.0, JS: 2.2.0
Android: Native: 2.1.0, JS: 2.2.0
No changes have been made to the app in the last two weeks.
The process for Android app deployment has been improved, to make release more efficient in future.
The following items were released during the last 2 weeks:
Not all trip data was passed to Quicksight as expected due to timeouts. Work is now completed to prevent timeouts occurring in future and previously missing data is now available in Quicksight.
Not all routes shown to book in app:
It was found that, if a contract only had default rules set-up, any change to the 'searchable by' field didn’t update all of the trips set-up under the contract.
This has been resolved and all trips are now updated where the 'searchable by' status changes for a contract that uses only default rules. As with contracts with override rules, if the status is set to 'none' no trips under the contract will be shown as available to book. if the status is set to 'observers' all trips under the contract will show as available to book.
Unexpected Journey Events where Passengers are Scheduled:
There were cases identified where passengers were scheduled on a trip but registered as boarding and disembarking a vehicle as unexpected on journey. Trip projections, that are used to determine if a passenger is expected on board a vehicle or not, have been re-run to correct all future trip occurrences.
The following items have been resolved and will be included in the next release:
Journey Notification Cache Clear:
When a notification was sent from a journey screen (Trips->View Trip->View Journey->Send Notification), the message text entered wasn't cleared once the message was sent or if cancel was selected. Any message text entered will now be cleared where the message is sent or the request is cancelled.
Not Boarded Notification:
A not boarded notification would be sent to an observer where a passenger boarded at an earlier stop to that scheduled. This has been resolved, and observers won't be sent not boarded notifications where their passenger is already on board the vehicle.
Trip Map - Long and Lat:
When searching for a waypoint during route creation, if a lat or long was entered incorrectly into the map, for example, too many digits were entered such as a long of -0.74406 and a lat of 519.51084, a screen would show with a something went wrong error and the route information added to that point would be lost. The lat and long fields have now been changed so that it isn't possible to add a lat or long with too many characters, either manually or by pasting a value.
The following items are in progress:
Ongoing - Logging Improvements:
Logging of system errors has been improved to allow for effective identification and alerting of issues.
Ongoing - System Restore from Backup:
The process to back-up and restore Kura systems has been improved to allow for a quicker recovery in the event of a system failure. There are a couple of system areas where back-ups are being enabled.
Ongoing - Alarms Prevented From Closing:
There have been a number of alarms that show an error when attempting to action or close. This is caused by a sort key for journey, that occasionally creates duplicates and causes conflicts. The sort key uses event timestamp and has been extended to include nano-seconds, to avoid duplications that prevent alarm action or closure or the over-writing of journey information. Database transfer is complete on UAT. The next steps are to point the APIs to the new database and to transfer historical data. Once complete data will be removed from the old database.