- The app versions have been updated as below:
iOS: Native: 1.8.0, JS: 1.8.0
Android: Native: 1.8.0, JS: 1.8.0
The latest version has been released to the Android and iOS app stores and is now available to download.
Phones provided by Kura should automatically update to the new version. Tablets provided by Kura need to be scheduled for update.
To ensure that the app is using the latest versions of all services, the app has been updated to the latest versions of the below:
- BG location
- One Signal
- React navigation
NFC reading has been enabled for iOS.
In the driver app there is a scan function that can be enabled from the passenger list. When this is selected a screen will open showing that scanning is enabled.
Once a scan has been registered the usual sounds will be made and a confirmation will be shown.
The scan icon can be cancelled, for example, to manually board a passenger, and re-enabled when needed. The scan icon will only be shown on Apple devices.
Tracking has been fully implemented for iOS, so that organisations can choose to use either Apple or Android devices for journey tracking.
Driver App - Board confirmation for passengers not expected on trip:
There is an additional confirmation screen shown when passengers that are not expected on a trip are selected to manually board. This will prompt drivers to confirm the action, to prevent occurrences where they are manually boarding a number of passengers in quick succession and don't notice that they have reached the passengers that aren't expected on the trip.
Driver App - Trip Name:
Long trip names were not always shown in full on the Driver Schedule, Journey or Passenger screens when using a phone. Trip names that are too long to be accommodated in full are now animated, so that they continually scroll on screen.
Driver App - Distinguish stop name and address:
Some organisations are using stop names that are a location address, however, the waypoint location address is slightly different. Stop names and addresses have now been separated in the Journey screen so that drivers can see the distinction.
Driver App - I'm here pop-up:
A pop-up will now be shown when a vehicle is in a scheduled geo-fence that is not the expected geo-fence. This asks the driver if they would like to advance the journey to the current point. They are shown the stops that have been missed and are asked to provide the reason for skipping the stop(s).
If they submit the request the app will discard the missed stops and advance the journey to the current location.
If they cancel the request the app will expect the stops to be visited in order.
If the vehicle moves out of the geo-fence the pop-up will automatically disappear.
On Route Board or Disembark:
When a passenger boarded or disembarked outside of a geo-fence the event was previously attributed to a stop name. If a passenger boards or disembarks outside of a geo-fence the Route Point Name will now display as 'on route', so that cases of this can be easily identified.
If a contract uses the Unexpected Board/Unexpected Disembark notifications observers will see 'on route' as the stop name.
Alarm Screen Refresh:
The alarm screen was refreshing for all users when an alarm was handled. Now the screen will stay at the location a user is viewing rather than refreshing to the top of the screen.
Create Trip Spinner:
When a new trip is created, a spinner will be shown until the the trip name is visible and can be selected in the trips summary screen. You will see a message that the trip schedule calendar may take a few minutes to populate as the trip schedule is created.
External ID in Bookings:
The Bookings table and export now include a passenger External ID, where this is available for a passenger profile. You will see this in a new column called external ID. If there is no unique ID for a passenger the column will be blank. This will potentially allow organisations to import the data into their own system.
Driver Login Performance in Quicksight:
There is a report available in Quicksight that shows expected login vs. actual login to the app, to monitor if drivers are logging in to perform their trips.
Code has been optimised to allow passengers to be added or removed from trips created over a long period, with a 3 year schedule limit. You will now be shown an error if you try to create a schedule that is over 3 years in duration.
Late alarms generated:
The notification issue experienced two weeks ago was causing alarms to occasionally trigger later than expected. The alarms are generated from the same part of the system and were being impacted by the notification load. This hasn't occurred since the notification micro service was implemented.
The notification system has been upgraded, to prevent any limits being reached that may result in notifications being delayed.
In the last release work was completed to slow down the building of the code, to resolve an issue where a person's schedule calendar occasionally wouldn't display a trip that they were scheduled on.
The projection rebuild will be applied to trips that already exist, to update any trips that were not shown correctly in a person's schedule in the website or in the app.
Update Supplier without completing mandatory fields:
Users were able to update a supplier without completing all mandatory fields. Users will now be shown an error to prompt them to complete all fields before they are able to save.