New Features

• No new features are included in this release.

Feature Enhancements

Pull-to-Refresh Support on the Incidents Page

• What - Added native pull-to-refresh functionality to the Incidents page, allowing users to refresh incident information using a familiar iOS swipe-down gesture. The refresh action reloads incident data, map information, and call notes, providing a faster and more intuitive way to obtain the latest information while remaining within the current workflow.
• Why - This enhancement improves usability by providing a standard iOS refresh experience that allows responders to quickly retrieve updated incident information without navigating away from the page or relying solely on automatic updates.
• How
  • Navigate to the Incidents page.
  • Pull down from the top of the screen to initiate a refresh.
  • Wait for the refresh indicator to complete.
  • Incident information, map data, and call notes are automatically reloaded.
  • The refresh action can be performed whenever updated information is needed.
• Use Case - A responder monitoring an active incident can quickly refresh the page after receiving a radio update to ensure the latest notes, dispatch information, and map details are displayed without interrupting ongoing operations.

Position Updated Timestamp in Unit List

• What - Added a Position Updated timestamp to the Unit List when location update information is available. The timestamp provides additional visibility into the freshness of unit location data, helping users better understand when a unit's position was last reported.
• Why - This enhancement improves situational awareness by providing greater transparency into location tracking data. Users can more easily determine whether a displayed unit location represents a recent update or older information.
• How
  • Open the Unit List within the application.
  • Review unit location information.
  • When available, a Position Updated timestamp displays alongside the unit information.
  • The timestamp updates automatically as new location data is received.
• Use Case - Command staff monitoring apparatus movement can quickly verify whether a displayed unit location was updated recently before making operational decisions based on that information.

Critical Alert Sound Support in Foreground

• What - Enhanced notification handling to support critical alert sounds while the application is actively in use when Always Play Sound is enabled. Critical notifications can now trigger audio alerts even when the application remains in the foreground.
• Why - This enhancement helps ensure important notifications receive immediate attention during active application usage. Responders can remain focused on operational workflows while still receiving audible alerts for high-priority events.
• How
  • Navigate to application notification settings.
  • Enable Always Play Sound.
  • Continue using the application normally.
  • Critical alerts automatically play notification sounds while the application is active.
  • Existing notification behavior remains unchanged when the setting is disabled.
• Use Case - A responder actively reviewing incident details can still receive an audible alert for a critical notification without needing to leave the application or rely solely on visual indicators.

Fixes

WebView Stability and Lifecycle Performance Improvements

• What - Improved WebView lifecycle management to reduce unnecessary view hierarchy recreation during application lifecycle events. The update minimizes avoidable reloads, reduces the likelihood of CPU-intensive refresh loops, and improves the overall stability and responsiveness of web-based workflows throughout the application.
• Why - This fix improves performance and reliability for web-based modules by reducing unnecessary processing during application transitions, helping users maintain continuity while working in embedded web experiences.
• How
  • Continue using web-based modules normally.
  • WebView content is now managed more efficiently during application lifecycle events.
  • Existing functionality and workflows remain unchanged.
  • No user action is required.
• Use Case - A user working within a web-based report or form can switch between applications and return without triggering unnecessary reload activity that could negatively impact performance.

Map Stability, Rendering, and Performance Improvements

• What - Delivered a broad set of map-related stability and performance improvements across responder workflows. Updates address crashes that could occur while navigating dense map layers, improve offline map reliability after downloading offline data, restore visibility for affected ArcGIS layers, improve pre-plan loading performance, optimize pre-plan marker rendering and caching, enhance annotation layer stability, and improve overall responsiveness during map interactions. Additional improvements reduce accidental navigation behavior while interacting with incident maps.
• Why - These fixes improve map reliability and responsiveness during critical operations where responders depend on accurate geographic information, pre-plans, hydrants, and other operational layers. Improved stability reduces interruptions while navigating maps under demanding conditions.
• How
  • Open the responder map as normal.
  • Navigate through incidents, pre-plans, and map layers.
  • Map rendering, offline functionality, layer visibility, and pre-plan loading now operate more efficiently.
  • Gesture interactions have been refined to reduce accidental navigation actions.
  • No configuration changes are required.
• Use Case - A responder navigating a large incident area containing multiple regional layers and pre-plans can pan, zoom, and interact with map content more reliably without experiencing delayed rendering, missing layers, or unexpected application instability.

Offline Data Reliability Improvements

• What - Fixed an intermittent issue that could cause instability after downloading offline map data and operating in offline mode. Offline workflows now behave more reliably following data downloads and subsequent map usage.
• Why - This fix improves confidence in offline operations for responders working in areas with limited or unreliable network connectivity.
• How
  • Download supported offline map data.
  • Continue operating in offline mode as needed.
  • Offline map workflows now function more consistently after data downloads.
  • No additional user action is required.
• Use Case - A responder operating in a remote area can rely on downloaded offline map content without experiencing interruptions after refreshing or updating offline datasets.

Application Startup and Resume Performance Improvements

• What - Improved application startup and lifecycle behavior by resolving a scenario where the application could remain indefinitely on the loading screen during a cold launch. Additional optimizations defer non-essential work during foreground resume events to improve responsiveness and reduce main-thread contention.
• Why - These fixes improve reliability and reduce delays when launching or returning to the application, ensuring responders can access information more quickly during critical situations.
• How
  • Launch the application normally.
  • Return to the application from the background as needed.
  • Startup and resume operations now complete more efficiently.
  • No user action or configuration changes are required.
• Use Case - A responder opening the application during an active incident can access operational information more quickly without encountering prolonged loading screens or delayed responsiveness.

Default Station Preference Visibility Correction

• What - Fixed an issue where the Default Station setting within Preferences did not always update correctly based on the client's response status configuration. The setting now appears and updates appropriately according to the applicable configuration.
• Why - This fix improves configuration accuracy and prevents confusion by ensuring preference options correctly reflect the organization's response workflow settings.
• How
  • Navigate to Preferences.
  • Review the Default Station setting.
  • The setting now displays correctly based on applicable response status configurations.
  • No additional setup is required.
• Use Case - A user updating application preferences can accurately view and configure their default station settings without encountering inconsistent visibility behavior.

Monitoring, Diagnostics, and Observability Improvements

• What - Enhanced monitoring and diagnostics capabilities by separating Luciq telemetry environments for Stage and Production, improving dSYM upload handling, and adding additional tracking around dispatch notification delivery timing and related notification settings. Google Maps iOS SDK dependencies were also modernized through migration to Swift Package Manager.
• Why - These improvements strengthen application monitoring, troubleshooting, and deployment reliability while providing more accurate operational insights into notification delivery and application behavior.
• How
  • Continue using Stage and Production environments normally.
  • Monitoring and diagnostic improvements operate automatically in the background.
  • Notification timing metrics and environment-specific telemetry are collected without user intervention.
  • No configuration changes are required.
• Use Case - Support and engineering teams can more effectively monitor production behavior, investigate notification delivery issues, and maintain application stability using more accurate environment-specific telemetry and diagnostic data.