New Features

Managed App Update Banner Configuration

• What - Added managed configuration support that allows mobile device management administrators to control the application update banner presented to users. Administrators can suppress the standard update banner or customize its behavior through managed application configuration, providing greater control over how application updates are communicated on centrally managed devices.
• Why - Organizations using managed mobile devices may coordinate application deployments according to established rollout schedules. Providing administrative control over update messaging helps prevent users from receiving update prompts that conflict with centrally managed deployment processes.
• How
  • Configure the applicable app update banner settings through the organization's Mobile Device Management (MDM) solution.
  • Choose whether the application update banner should be displayed, suppressed, or customized according to the available managed configuration.
  • Deploy the configuration to managed iOS devices.
  • The application automatically applies the managed update banner behavior.
• Use Case - An organization that centrally schedules iOS application updates can suppress the standard update banner on managed devices, preventing responders from receiving unnecessary update prompts when updates are already being handled through the organization's device management process.

Forced Password Reset Handling

• What - Added application handling for accounts that require a forced password reset, allowing the iOS application to recognize the required password-change state and direct users through the appropriate authentication workflow.
• Why - Properly recognizing required password changes provides a clearer and more reliable authentication experience when a user's credentials must be updated before access can continue.
• How
  • Sign in to the application using the existing authentication workflow.
  • If the account requires a password reset, follow the displayed password reset workflow.
  • Complete the required password change.
  • Sign in using the updated credentials as prompted.
• Use Case - A responder whose account has been flagged for a required password change is directed through the appropriate reset process instead of encountering an unclear authentication failure.

Feature Enhancements

Improved WebView Loading Behavior

• What - Enhanced WebView-backed experiences with improved page readiness detection, allowing the application's loading overlay to dismiss more reliably once web content is ready for use.
• Why - More reliable loading behavior reduces situations where users may continue seeing a loading indicator after the underlying web page is already available, creating a smoother transition into web-based responder workflows.
• How
  • Open a module or workflow that uses embedded web content.
  • Allow the requested page to load normally.
  • The loading overlay now dismisses automatically when the page reports that it is ready.
  • No additional configuration is required.
• Use Case - A responder opening a web-based workflow can begin interacting with the page as soon as it is ready instead of waiting behind a loading overlay that remains visible unnecessarily.

Image Cache Memory Management Improvements 

• What - Improved image cache memory management by strengthening cache eviction behavior and reducing memory limits, helping the application release unnecessary cached image data more efficiently.
• Why - Better cache management reduces application memory pressure and supports improved stability during extended use, particularly in workflows that display significant amounts of imagery.
• How
  • Continue using the application normally.
  • Image cache management occurs automatically in the background.
  • Unnecessary cached images are released more efficiently as memory conditions change.
  • No user configuration is required.
• Use Case - A responder moving between image-heavy maps, incidents, and other application workflows during a long shift benefits from more efficient memory use and reduced resource pressure.

Incidents List Performance and Architecture Improvements 

• What - Modernized the Incidents List using SwiftUI and updated the underlying dispatch retrieval architecture to use a shared dispatch service. The change reduces reliance on older application components while improving the foundation for incident loading and future responder workflow enhancements.
• Why - Modernizing the Incidents List improves long-term reliability and maintainability while providing a stronger foundation for consistent dispatch behavior and future improvements.
• How
  • Navigate to the Incidents List.
  • Continue reviewing and selecting incidents using the existing workflow.
  • Incident retrieval and presentation now use the updated application architecture automatically.
  • No configuration changes are required.
• Use Case - A responder reviewing active incidents continues using the familiar incident workflow while benefiting from an updated technical foundation designed to improve reliability and support future enhancements.

Improved Image and Avatar Loading Performance

• What - Improved avatar and image retrieval by reducing duplicate requests, limiting simultaneous downloads, and improving caching behavior for unavailable images. These changes reduce unnecessary network and processing activity when displaying user-related imagery.
• Why - More efficient image retrieval reduces unnecessary resource consumption and helps improve application responsiveness, particularly on screens displaying multiple personnel or user images.
• How
  • Continue using workflows that display personnel or user images.
  • Image requests and caching are automatically managed by the application.
  • Duplicate and unnecessary requests are reduced without requiring user action.
• Use Case - A user opening a screen containing multiple personnel images experiences more efficient loading with fewer unnecessary network requests occurring in the background.

Improved Foreground Resume Performance

• What - Improved application responsiveness when returning from the background by coordinating foreground resume activity and deferring non-essential processing until after higher-priority application work is complete.
• Why - Reducing simultaneous processing when the application returns to the foreground helps minimize delays and provides faster access to operational information.
• How
  • Use the application normally and switch to another application when needed.
  • Return to the Responder Mobile App.
  • Essential foreground activity is prioritized while non-critical work is handled afterward.
  • No configuration changes are required.
• Use Case - A responder switching back to the application while responding to an incident can regain access to operational information with less delay caused by background processing.

Database Lifecycle Reliability Improvements

• What - Improved internal database lifecycle handling by coordinating database state changes across application startup and other database-related workflows.
• Why - More consistent database state management supports application stability and helps ensure locally stored responder information remains available during startup and application lifecycle transitions.
• How
  • Continue using the application normally.
  • Database state management occurs automatically during startup and supported lifecycle transitions.
  • No user action or configuration is required.
• Use Case - A responder launching the application benefits from more consistent management of locally stored information without needing to perform additional recovery or synchronization steps.

Fixes

Google Maps Rendering Crash 

• What - Fixed a high-priority Google Maps rendering issue that could cause the application to unexpectedly close during map operations involving graphical texture processing.
• Why - Improving map stability helps ensure responders can continuously access incident locations and other geographic information without disruptive application crashes.
• How
  • Open Responder Map and interact with map content normally.
  • Pan, zoom, and review available map information as needed.
  • The underlying rendering issue is corrected automatically.
  • No configuration changes are required.
• Use Case - A responder actively navigating the map during an incident can continue panning and zooming without encountering the previously reported rendering crash.

Incident Number Population from CAD

• What - Fixed an issue where the Incident Number provided through CAD could fail to populate within the mobile application for affected dispatch workflows.
• Why - Accurate incident numbers are important for identifying calls and maintaining consistency between CAD and responder workflows.
• How
  • Open an incident received through CAD.
  • Review the incident information within the application.
  • The Incident Number now populates correctly when supplied by CAD.
  • No user action is required.
• Use Case - A responder comparing an active incident with information communicated through CAD can reliably use the same incident number across both systems.

Missing Chat Messages for Group Members

• What - Fixed an issue where some members of a chat could be missing messages that were available to other participants.
• Why - Consistent message visibility is important for operational communication and helps ensure all participating users receive the same information during collaborative workflows.
• How
  • Open the applicable Chat conversation.
  • Review incoming and existing messages normally.
  • Messages now display consistently for applicable conversation members.
  • No additional configuration is required.
• Use Case - Multiple responders participating in the same conversation can reliably see the messages shared with the group, reducing the risk of important information being missed.

Google Maps Renderer Stability

• What - Fixed an additional Google Maps renderer issue that could cause the application to crash during internal map rendering operations.
• Why - Addressing this separate map rendering failure further improves the stability of map-based workflows during routine and extended application use.
• How
  • Continue using Responder Map normally.
  • Navigate, pan, and interact with map content as needed.
  • Rendering stability improvements operate automatically.
• Use Case - A responder using the map throughout an extended incident experiences fewer interruptions caused by unexpected map renderer failures.

Session Data Memory Allocation Crash

• What - Fixed a fatal memory allocation issue that could cause the application to unexpectedly close while receiving and processing session data.
• Why - Improving memory handling reduces disruptive crashes and provides greater reliability during application sessions.
• How
  • Continue using the application normally.
  • Session information is processed using the updated memory handling behavior.
  • No user action is required.
• Use Case - A responder working through an active session can continue accessing application features without an unexpected shutdown caused by the previously identified memory allocation condition.

Firestore Storage Stability

• What - Fixed a high-priority internal Firestore storage issue that could cause an application failure during local database input and output operations.
• Why - Reliable local data handling is important for application stability and helps prevent unexpected interruptions when the application is storing or retrieving information.
• How
  • Continue using application workflows normally.
  • Local Firestore data operations now include the corrected handling.
  • No configuration changes are required.
• Use Case - A responder moving between workflows that rely on locally synchronized information experiences improved stability without interruptions caused by the previously identified storage failure.

Group Chat Message Visibility

• What - Fixed a group chat issue where messages could fail to appear within the mobile application, restoring expected message visibility for affected conversations.
• Why - Reliable group messaging helps responders maintain a shared understanding of operational information and prevents important communications from being unintentionally hidden.
• How
  • Open a Group Chat.
  • Send and receive messages using the existing messaging workflow.
  • Messages now appear correctly for applicable participants.
  • No additional setup is required.
• Use Case - A group coordinating operational information through chat can reliably see newly shared messages, helping participants stay informed throughout the conversation.

Status Log Ordering Consistency

• What - Fixed differences in the ordering of status log entries between iOS and Android so status history is presented more consistently across mobile platforms.
• Why - Consistent status history makes it easier for users to interpret the sequence of operational status changes regardless of which mobile platform they use.
• How
  • Open the applicable Status Log.
  • Review recorded status changes.
  • Entries now follow consistent ordering behavior on iOS and Android.
  • No configuration changes are required.
• Use Case - Personnel reviewing status history from different mobile devices can interpret events in the same sequence, reducing confusion when reconstructing responder activity.