Mobile Response (Android): Release Notes August 2026 (iOS Version 7.2.3)
New Features
In-App Bug Reporting (New Feature)
What - Added Luciq-powered in-app bug reporting, allowing users to report application issues directly from the Android app. Submitted reports can include supporting diagnostic context such as screenshots, device details, operating system version, application version, logs, diagnostics, session history, timestamps, and environment or build information to provide additional context for troubleshooting.
Why - This feature makes it easier for users to report problems when they occur while also providing support teams with more useful diagnostic information. Capturing relevant application and device context with the report can reduce follow-up questions and help accelerate issue investigation and resolution.
How
Open the application's Report a Bug option.
Provide information describing the issue encountered.
Include supporting information, such as a screenshot, when appropriate.
Submit the report directly from within the application.
Available diagnostic and application context is automatically included with the report to assist with troubleshooting.
Use Case - A responder encounters unexpected behavior while using the application and can immediately submit a bug report from their device. Support teams receive the report along with relevant diagnostic context, making it easier to understand what occurred and investigate the issue.
Log Training Submenu (New Feature)
What - Added a new Log Training submenu to the mobile application's main navigation for users with the appropriate Training permissions. Users with full create permissions can access the mobile-optimized training logging workflow for the available crew roster, while users with self-log permissions are limited to logging training for themselves.
Why - Providing direct access to training logging from the mobile application makes it easier for authorized personnel to document training activities from the field while ensuring attendee availability remains consistent with assigned permissions.
How
Open the application's Main Menu.
Navigate to Training → Log Training.
Users with full create permissions can select applicable attendees from the available crew roster.
Users with self-log permissions can log training with attendee visibility limited to themselves.
Complete the mobile-optimized training logging workflow as normal.
The Log Training option is only available to users with the applicable permissions.
Use Case - After completing a field training exercise, an authorized officer can open Log Training from the mobile application and document the activity for participating personnel. A responder with self-log access can use the same mobile workflow to document their own training without being given access to other attendees.
Feature Enhancements
Responder Status Ordering (Feature Enhancement)
What - Improved the presentation of responder statuses so configured priority determines the primary display order, with remaining statuses organized alphabetically. Responders sharing the same status are now also grouped together regardless of differences in user type, providing a more consistent view of responder activity.
Why - Consistent status organization makes it easier to quickly understand responder availability and activity during an incident. Grouping personnel by their shared operational status reduces unnecessary separation and makes high-priority statuses easier to identify.
How
Open Incident Details and review responder status information.
Status groups automatically appear according to their configured priority.
Remaining statuses are displayed alphabetically.
Responders with the same status are grouped together regardless of user type.
No additional user configuration is required.
Use Case - During an active incident, command personnel can quickly review responders according to operational status, with higher-priority statuses presented first and personnel performing the same status grouped together for easier accountability.
Status Log Layout Improvements (Feature Enhancement)
What - Improved the Status Log within Incident Details so the container dynamically adjusts to the amount of information displayed up to an appropriate maximum height. Row spacing has also been reduced to display more responders at once while preventing partially clipped rows and preserving existing typography and status color conventions.
Why - This enhancement improves readability and makes better use of available screen space when reviewing responder status activity. Displaying complete rows and more responders within the available area reduces unnecessary scrolling and makes status information easier to review during active operations.
How
Open an active incident.
Navigate to Incident Details and locate the Status Log.
The Status Log automatically expands based on the amount of displayed content.
When the maximum display height is reached, use the existing scrolling behavior to review additional entries.
No configuration changes are required.
Use Case - An Incident Commander reviewing responder activity can see more personnel within the Status Log at once, with complete rows and compact spacing making it easier to assess current activity without excessive scrolling.
What - Enhanced authentication handling to recognize when an account requires a mandatory password reset. When a password reset is required during login, the application directs the user to the provided password reset workflow before granting access. Existing authenticated sessions remain available until the user logs out or the session expires.
Why - This enhancement supports password security requirements while providing predictable behavior for users who are already signed in. Required password changes are enforced when authentication occurs without unnecessarily interrupting an existing valid session.
How
Sign in using the normal application login workflow.
If a password reset is required, the application automatically directs you to the applicable Password Reset workflow.
Complete the required password change before continuing into the application.
Users with an existing valid session can continue working until they log out or that session expires.
The new password requirement is enforced the next time authentication is required.
Use Case - A responder whose account has been marked for a required password change can finish work during an existing valid session. When authentication is required again, the application directs the responder through the required password reset before allowing access.
Fixes
Improved Pre-Plan Camera Photo Quality on Google Pixel Devices (Bug Fix)
What - Fixed an Android issue affecting Google Pixel devices where photos captured directly from the device camera could be noticeably reduced in quality when uploaded to a Pre-Plan unit. Camera images now retain their expected quality more consistently when they are captured and attached through the Pre-Planning workflow.
Why - Clear photographs can provide important visual context for pre-incident planning, including building features and other location-specific information. Preserving image quality helps ensure responders can clearly review the visual information attached to a Pre-Plan when preparing for or responding to an incident.
How
Open the applicable Pre-Plan.
Navigate to the area where a photo can be added to the Pre-Plan unit.
Choose the option to capture a new image using the device Camera.
Take the photograph and attach it to the Pre-Plan.
Photos captured on affected Google Pixel devices now retain the expected image quality more consistently.
Use Case - A user documenting a building feature with a Google Pixel device can capture and attach a photograph directly to the Pre-Plan without the image becoming noticeably degraded, allowing responders to review clearer visual information later.