New Features

Expanded Medications Module Navigation

• What - Expanded the Medications module by adding three new web page links that integrate with the existing navigation experience. The new links respect existing user permissions and provide users with additional medication-related resources without changing established workflows.
• Why - This enhancement improves access to medication resources while maintaining a familiar navigation experience and ensuring users only see resources appropriate for their permissions.
• How
  • Navigate to Medications.
  • Select one of the available web page links.
  • The linked page opens within the existing application navigation.
  • Access is automatically controlled by user permissions.
• Use Case - A responder reviewing medication information can quickly access additional reference material without leaving the application workflow.

Feature Enhancements

• No feature enhancements are included in this release.

Fixes

Improved Google Maps Rendering Stability

• What - Fixed an issue that could cause the application to crash while interacting with Google Maps after certain application lifecycle events, resulting in a more stable mapping experience.
• Why - Responders rely on mapping throughout emergency operations, and improving map stability helps reduce interruptions during navigation and incident management.
• How
  • Open the Responder Map.
  • Interact with Google Maps normally.
  • Map rendering now remains stable after the application resumes from background or other lifecycle transitions.
• Use Case - A responder returning to the application after temporarily switching to another app can continue using the map without experiencing unexpected crashes.

Reduced Memory Allocation Crashes

• What - Fixed a memory allocation issue that could cause the application to unexpectedly terminate during memory-intensive operations.
• Why - Improving memory management increases overall application reliability and reduces unexpected interruptions during active response workflows.
• How
  • Continue using the application normally.
  • Memory allocation is now managed more efficiently during high-demand operations.
  • No user action is required.
• Use Case - Responders working between incidents, maps, and other resource-intensive workflows experience improved stability during extended use.

Improved Main Thread Performance

• What - Reduced application pauses caused by image processing occurring on the main thread, resulting in a more responsive user interface during normal operation.
• Why - Keeping processing off the main thread improves application responsiveness and reduces visible interface delays.
• How
  • Continue using the application normally.
  • Image processing is now handled more efficiently.
  • No configuration changes are required.
• Use Case - A responder navigating between screens experiences smoother transitions without temporary interface freezes.

Improved Dispatch Processing Performance

• What - Optimized dispatch alert retrieval and dispatch database processing by moving resource-intensive operations off the main thread and improving batching behavior.
• Why - This improves responsiveness during live dispatch processing while reducing delays caused by background data processing.
• How
  • Continue using dispatch workflows normally.
  • Dispatch processing occurs automatically using the updated background processing logic.
  • No user configuration is required.
• Use Case - Responders monitoring active incidents receive improved application responsiveness while dispatch information continues updating in the background.

Improved Expired Session Handling

• What - Fixed an issue where authenticated requests could continue after an access token had already expired. The application now prevents requests from being sent when a session is no longer valid.
• Why - Preventing invalid requests provides a more secure and predictable authentication experience while reducing unnecessary server communication.
• How
  • Continue using the application normally.
  • If a session expires, the application automatically requires users to authenticate again before sending additional requests.
  • No user action is required beyond signing back in when prompted.
• Use Case - A responder returning after an extended period is prompted to sign in again instead of encountering unexpected authorization errors.

Consistent Unauthorized Session Management

• What - Standardized how the application responds to unauthorized API requests by introducing a consistent session management workflow that automatically returns users to the sign-in screen when authorization is no longer valid.
• Why - This improvement eliminates inconsistent session behavior and ensures users always operate with a valid authenticated session.
• How
  • Continue using the application normally.
  • Unauthorized sessions automatically return users to Sign In.
  • Sign in again to continue working.
• Use Case - Users whose sessions expire receive a consistent authentication experience regardless of which feature generated the unauthorized response.

Improved Retry Behavior for Authentication Failures

• What - Updated network retry behavior to prevent repeated retries after authorization failures while continuing to retry eligible temporary network errors.
• Why - This reduces unnecessary network traffic and provides faster recovery from authentication issues.
• How
  • Continue using the application normally.
  • Authentication failures are handled immediately.
  • Temporary network interruptions continue using automatic retry behavior where appropriate.
• Use Case - A responder with an expired session is returned directly to authentication instead of waiting through repeated failed network requests.

Improved Multi-Account Switching Reliability

• What - Fixed an issue that could prevent certain multi-account switching operations from completing successfully after authorization failures.
• Why - This improves reliability for users who regularly switch between multiple organizational accounts.
• How
  • Switch between configured accounts using the existing account management workflow.
  • Account changes now complete more reliably.
  • No additional configuration is required.
• Use Case - A user managing multiple agencies can switch accounts without experiencing stalled account transition workflows.

Per-Account WebView Data Isolation

• What - Improved privacy and account separation by storing WebView website data independently for each configured account.
• Why - This reduces the possibility of web content or session information carrying over between accounts while improving operational consistency.
• How
  • Continue using multi-account functionality normally.
  • Each account now maintains its own web session data automatically.
  • No user action is required.
• Use Case - Users switching between agencies can be confident each account maintains its own independent web session and cached data.

Improved SwiftUI Diagnostic Reporting

• What - Enhanced application diagnostics by providing more meaningful screen names for SwiftUI-based workflows within crash and performance reporting.
• Why - Better diagnostic information helps support teams more quickly identify where issues occurred within the application.
• How
  • Continue using the application normally.
  • Diagnostic improvements operate automatically in the background.
  • No configuration changes are required.
• Use Case - Support personnel investigating an issue can more accurately identify the screen where a problem occurred.

Custom ArcGIS Basemap Loading on iPad

• What - Fixed an issue preventing custom ArcGIS basemaps from loading correctly on iPad devices.
• Why - Reliable map loading ensures responders have access to the correct geographic information during incident response.
• How
  • Open the responder map on an iPad.
  • Select a custom ArcGIS basemap.
  • Basemaps now load correctly without additional user intervention.
• Use Case - An Incident Commander using an iPad can reliably view department-specific ArcGIS basemaps while managing an incident.

Improved Incident Icon Visibility

• What - Fixed an issue where incident icons could disappear or become hidden behind preplan icons on the responder map.
• Why - Maintaining clear visibility of incident locations improves situational awareness during active operations.
• How
  • Open the responder map.
  • View incidents alongside preplans.
  • Incident icons now remain clearly visible above surrounding map elements.
• Use Case - Responders monitoring multiple incidents can easily distinguish incident locations without icons becoming obscured by nearby preplans.

Scrollable Settings Lists on iPad

• What - Fixed an issue preventing users from scrolling long selection lists within settings dialogs on iPad devices.
• Why - This improvement restores full access to all available settings options regardless of list length.
• How
  • Open a settings dialog containing a long selection list.
  • Scroll through the available options normally.
  • All items are now accessible using touch scrolling.
• Use Case - Users configuring application preferences on an iPad can review and select any available option without interface limitations.

Reduced User Preference Synchronization During Map Startup

• What - Reduced unnecessary user preference synchronization during map initialization to improve startup efficiency and reduce background processing.
• Why - Eliminating redundant synchronization improves overall application responsiveness during map loading.
• How
  • Open the responder map.
  • User preferences are synchronized more efficiently during startup.
  • No user action is required.
• Use Case - A responder opening the map immediately after launching the application experiences faster map availability with fewer unnecessary background operations.