New Features

In-App Bug Reporting

• What - Added in-app bug reporting capabilities powered by Luciq, allowing users to submit issues directly from the mobile application. Bug reports now include valuable diagnostic information to help support and engineering teams better understand reported issues and accelerate troubleshooting efforts.
• Why - This enhancement simplifies the process of reporting issues while improving the quality of information available during investigations. By capturing diagnostic context directly from the device, support teams can more efficiently identify root causes and reduce the time required to resolve reported problems.
• How
  • Navigate to the application's bug reporting option.
  • Select Report a Bug.
  • Enter details describing the issue.
  • Submit the report directly from within the application.
  • Relevant diagnostic information is automatically included to assist with troubleshooting.
• Use Case - A responder experiencing an issue while using the application can immediately submit a bug report without leaving the app, providing support teams with the information needed to investigate and resolve the problem more quickly.

Selectable Offline Map Expansion

• What - Introduced support for user-selectable offline map expansion, allowing users to extend offline map coverage beyond the default response area. This enhancement provides greater flexibility when preparing for operations in larger response zones or areas with limited network connectivity.
• Why - This enhancement improves offline readiness by allowing responders to download and retain a broader geographic area, ensuring critical mapping information remains available when operating outside standard coverage zones.
• How
  • Navigate to offline map management settings.
  • Select the desired offline map coverage area.
  • Download the expanded offline map region.
  • Access downloaded map data when operating without network connectivity.
  • Available functionality may vary based on deployment configuration.
• Use Case - A responder preparing for a large regional event or mutual aid assignment can download a larger map area in advance, ensuring access to mapping information even when operating outside the normal response boundary.

Feature Enhancements

Place Name Display on Incidents

• What - Enhanced the incident workflow by adding Place Name visibility on the Incidents tab when Place Name information is available through client configuration. This provides additional context alongside traditional address information and helps users identify familiar locations more quickly.
• Why - This enhancement improves situational awareness by surfacing recognizable facility names, landmarks, or commonly used location identifiers directly within the incident workflow.
• How
  • Open the Incidents tab.
  • View incident information as normal.
  • Place Name information automatically appears when enabled by configuration and available from the incident data source.
  • No additional user action is required.
• Use Case - A responder receiving a dispatch to a well-known facility can immediately identify the location by its Place Name rather than relying solely on the street address.

Configurable Dispatch Map Zoom Preference

• What - Added a configurable map zoom preference for dispatch centering, allowing users to control the level of detail displayed when the application centers the map on a dispatched incident. Users can choose between broader situational context or a more detailed incident-focused view.
• Why - This enhancement provides greater flexibility for responders with different operational preferences and map usage needs, improving navigation and situational awareness workflows.
• How
  • Navigate to Preferences.
  • Locate the Dispatch Centering Zoom setting.
  • Select the desired zoom level preference.
  • Open a dispatched incident.
  • The map automatically centers using the selected zoom level.
• Use Case - A company officer who prefers a broader operational overview can select a wider zoom level, while a responder focused on navigation can choose a closer zoom level for more detailed location information.

Client Logo Loading Improvements

• What - Modernized client logo loading by introducing a new SwiftUI-based loading service with disk caching support. The enhancement reduces unnecessary network requests, improves loading performance, and provides a more responsive experience when displaying client branding throughout the application.
• Why - This enhancement improves application responsiveness and reduces repeated downloads, helping screens load more efficiently while minimizing network usage.
• How
  • Continue using the application normally.
  • Client logos are automatically cached and loaded through the updated service.
  • Previously downloaded logos are retrieved from local storage when appropriate.
  • No user configuration is required.
• Use Case - Users opening the application or navigating between branded screens experience faster loading times because client logos can be loaded from local cache rather than repeatedly downloaded.

Enhanced Crash, Hang, and Diagnostic Reporting

• What - Expanded Luciq observability and diagnostic capabilities by enriching crash and hang reports with additional context, including user and client information. These enhancements provide improved visibility into application health and support more efficient issue triage.
• Why - Better diagnostic information helps support and engineering teams more quickly identify affected users, determine issue scope, and prioritize resolutions for operationally significant problems.
• How
  • Continue using the application normally.
  • Diagnostic information is automatically collected when supported crashes or performance issues occur.
  • Reporting enhancements operate in the background without requiring user interaction.
  • No configuration changes are required.
• Use Case - When an application issue occurs, support teams can more rapidly identify the affected environment and user context, reducing investigation time and accelerating resolution efforts.

Fixes

Startup Crash and Launch Reliability Improvements

• What - Fixed a startup crash that could occur during application launch and introduced additional recovery mechanisms to improve cold-launch reliability. The application now handles scenarios involving protected data access or temporary database availability issues more gracefully, reducing the likelihood of launch failures and preventing forced application termination during startup.
• Why - These fixes improve overall application reliability and help ensure responders can access the application when needed, even during challenging device startup conditions.
• How
  • Launch the application normally.
  • Startup recovery processes now automatically handle temporary data availability issues.
  • The application recovers gracefully rather than terminating unexpectedly.
  • No user action is required.
• Use Case - A responder opening the application immediately after device startup can access operational information more reliably without encountering launch failures caused by temporary system conditions.

Application Responsiveness and Memory Management Improvements

• What - Addressed a reported main-thread hang that could leave the application temporarily unresponsive and added structured memory-pressure monitoring with proactive cleanup behavior. Additional logging and diagnostic improvements help identify memory-intensive workflows while reducing the likelihood of performance degradation.
• Why - These fixes improve responsiveness and stability during active use by reducing situations where the application may become sluggish or unresponsive under heavy workloads.
• How
  • Continue using the application normally.
  • Memory cleanup and performance optimizations operate automatically in the background.
  • No configuration changes are required.
• Use Case - A responder actively switching between incidents, maps, and reporting workflows experiences a smoother and more responsive application with fewer interruptions caused by resource contention.

WebView Cache Management and Content Freshness Improvements

• What - Enhanced WebView cache management by improving website data clearing during logout and application upgrade workflows. Additional refinements introduce more targeted cache-clearing behavior and cache-bypass refresh handling, helping ensure users receive the latest available web content while preserving performance.
• Why - These improvements reduce the likelihood of stale content appearing in web-based workflows such as EMS and ePCR while improving consistency after upgrades, deployments, and account transitions.
• How
  • Continue using web-based modules normally.
  • Log out and back into the application when required.
  • After upgrades, the application automatically performs targeted cache management.
  • Use the native refresh action to retrieve updated content using cache-bypass behavior.
  • No additional configuration is required.
• Use Case - A responder accessing an updated ePCR workflow after an application upgrade receives the latest forms and content without needing to reinstall the application or manually clear data.

EMS Report Printing Restoration

• What - Fixed an issue that prevented EMS reports from printing correctly following recent application updates. Printing workflows now function as expected across supported devices and report formats.
• Why - This fix restores a critical operational workflow for EMS personnel who rely on printed reports for documentation, compliance, and information sharing.
• How
  • Open a completed EMS report.
  • Select the Print option.
  • Proceed through the normal printing workflow.
  • Reports now generate and print correctly on supported devices.
• Use Case - EMS personnel completing patient care documentation can successfully print reports for operational, administrative, or compliance purposes without encountering failures introduced by previous application updates.

Improved Logout Messaging for Offline Data Protection

• What - Updated logout messaging to provide clearer warnings regarding unsynchronized offline data when users sign out of the application. The enhanced messaging helps users better understand the impact logout actions may have on locally stored information.
• Why - This improvement reduces the risk of unintended data loss by providing clearer guidance before users perform actions that could affect unsynchronized offline content.
• How
  • Select Logout from the application.
  • Review the updated warning message if unsynchronized offline data may be affected.
  • Confirm or cancel the logout action as appropriate.
  • Existing logout workflows remain unchanged.
• Use Case - A responder working offline is alerted that locally stored information may not yet be synchronized, allowing them to reconnect and sync data before logging out and potentially losing unsaved work.

Chat Framework Migration

• What - Completed the migration to the Exyte Chat framework, modernizing the underlying chat architecture and establishing a stronger foundation for future messaging enhancements and reliability improvements.
• Why - This update improves maintainability, supports future feature development, and strengthens the long-term reliability of real-time messaging workflows.
• How
  • Continue using messaging features normally.
  • Existing chat conversations and workflows remain available.
  • The updated framework operates transparently in the background.
  • No user action is required.
• Use Case - Responders using real-time messaging during active incidents benefit from a more modern messaging foundation that supports future enhancements while maintaining current communication workflows.