Release Notes - Roamer X - 3.9.X

Written By Natalia Povrozniak (Administrator)

Updated at June 26th, 2026

Table of Contents

For app versions:

  • Android 3.9.0 & 3.9.1
  • iOS 3.9.2
 

What's new

  • (iOS version) We have increased the minimum supported version of iOS to Version 17. 
  • We've migrated the Start Now booking feature from Roamer. The start time default to now + 5 minutes or what nearest time start is allowed by a booking policy. Once the booking is confirmed, the booking is auto-checked-in for the user.
  • We have introduced BLE based indoor positioning for the maps in Roamer. Please note to use this feature IBSS will need to be a minimum version of R2026.01 or greater.

What's changed

  • Users of Android devices enrolled into Microsoft Intune with App Protection Policies enabled reported slow response times and a degraded mobile user experience when using Roamer X:
    • We have upgraded the Intune libraries used by Roamer X, to ensure we have included the latest security and performance improvements provided by Microsoft.
    • We've adjusted how encrypted information is now batched and written more efficiently, improving performance for organisations using Roamer X with Intune app protection policies.
  • We've added indication on the KPI tiles (Dynamic Space Search links) about when the space count was last updated. The count is refreshed with the label “Just now” when the user opens the app, pulls home page down, or navigates back to the home page.
  • When an upcoming booking is available for auto check-in, the booking card now has a corresponding Auto check-in label indicating this.
  • We've removed the time selection page when searching for an unbookable amenity.
  • Capacity filtering is skipped for amenity since they have zero capacity.
  • Users are unable to select a date that has been set as Excluded on the Floor booking policy. Users with the API.Bookings.BookOutsideOfficeHours permission can override this limitation.
  • We've added a guidance message for users when they are changing room temperature to indicate the energy impact from medium to high and very high.
  • Roamer X is now using GET /v2/<node_id>/announcements/active endpoint to get building announcements.

What's fixed

  • After catering order has been added to the booking, and user navigates back to the booking edit page, the Pre-Order Catering page is now updated with the catering order that has been just added.
  • Also, when creating catering orders, the app now checks if the approval is needed on the building level.
  • We've resolved an issue where users were being shown the option to create multiple catering orders for a booking, even if their user did not have the correct right. This would lead to an error message at the end of trying to add the additional catering order
  • Scanning a spaces QR code successfully loads the space details page with the make a booking card.
    It defaults the date and time to now, and allows the user to edit to define the time they want.
  • When searching for a space and selecting either Work Type or Space Type filter, the other selector switches to Any. Users can only search by one of the options: Work Type or Space Type.
  • Creating a linked space booking no longer throws an error, despite being created.
  • When booking nearby for others, the app is correctly picking up the users name and is no longer displaying their name as 'null null'.
  • If the booking gets cancelled, the Your Bookings section on the home page is now automatically updated and the cancelled booking is removed from it.
  • We've fixed app picking up translations for several labels.
  • Certain temperature controls in specific configurations were incorrectly showing all negative setting a +1.
  • When adding a service request, the page is scrollable on all devices fixing the issue that the description field would sometimes appear off page, depending on the device.
  • The look of different types of a Building KPI has been fixed, and the Text and Slider type doesn't include the space count any more.
  • Resolved a crash when related to spaces having a specific repeating start interval implemented as part of a booking policy.