Android: Stability Improvements to Reduce Lifecycle-Related Crashes

• What - Implemented comprehensive stability improvements addressing lifecycle timing issues and invalid context references that were contributing to random crashes, with targeted hardening across Maps (Google & Esri), WebViews, API client handling, notification services, and foreground service management.

• Why - Certain crashes were caused by components attempting to access invalid or destroyed contexts during activity and fragment lifecycle transitions, particularly during rapid navigation or background-to-foreground changes; strengthening lifecycle compliance improves overall reliability and reduces unexpected app termination.

• How

  • Use the app normally, including:

    • Navigating between screens and returning to Map

    • Interacting with Google or Esri map layers

    • Receiving notifications while the app is in the background or foreground

    • Viewing content within embedded WebViews

  • Note: Foreground services now handle lifecycle transitions more safely.

  • Note: No user action or configuration changes are required.

• Use Case - A user rapidly switches between operational screens, receives a notification while the app is backgrounded, and then returns to an active map view; previously this sequence could trigger a random crash due to lifecycle timing conflicts, but the app now maintains stability and continues functioning without interruption.Android: Fix Map Settings Persistence When Closing Map Panel

• What - Updated Android map behavior so changes to Basemap, Map Style, and Layers are saved immediately upon selection, ensuring preferences persist regardless of whether the Map Technology panel is closed using the X button or by tapping outside the panel.

• Why - Previously, map setting changes were only written to the database when the panel was closed using the X, which caused selected preferences to be lost if users dismissed the panel by tapping outside; this created inconsistent behavior and required users to reconfigure settings during active operations.

• How

  • Navigate to Map

  • Open Map Technology

  • Select your desired Basemap, adjust Map Style, or toggle Layers

  • Exit the panel using either:

    • The X button, or

    • Tapping outside the panel

  • Note: Settings now save automatically upon selection—no additional action is required.

  • Note: Behavior now aligns with iOS for consistent cross-platform performance.

• Use Case - While en route to an incident, a responder switches to a satellite basemap and enables specific operational layers; even if they quickly tap outside the settings panel to return to the map view, their selections remain saved and available the next time they access the map.

Android: Fix False “User Already Logged” Login Error

• What - Resolved an issue where users were incorrectly blocked from logging in due to a false “There is already a user from this client logged” message, improving session management to properly clear stale or cached login states without requiring an app reinstall.

• Why - Users were prevented from accessing the app despite not having an active session elsewhere, resulting in operational disruption and reliance on reinstalling the app as a workaround; strengthening session state handling restores reliable access and reduces downtime.

• How

  • Open the app

  • Select Log In

  • Enter your credentials and authenticate as normal

  • If previously affected:

    • Fully close and reopen the app before retrying login

  • Note: Reinstalling the app is no longer required to resolve this error.

  • Note: Applies whether or not multiple accounts are configured on the device.

• Use Case - A field user who was previously locked out by the false login conflict message can now reopen the app and log in successfully without uninstalling and reinstalling, allowing them to regain access quickly during a shift.

Android: Fix App-Configured Notification Sounds Not Being Respected

• What - Corrected Android notification handling so alerts now play the sound configured in the app’s Sound Settings, including sounds assigned per Incident Group and the Others fallback group, instead of defaulting to the device’s system notification tone.

• Why - Notification tones are critical for situational awareness and differentiating incident types; when the system default sound played instead of the configured tone, it reduced clarity and consistency in alert recognition.

• How

  • Navigate to Settings → Sound Settings

  • Assign notification tones for each Incident Group

  • Ensure a tone is configured for Others as a fallback

  • Receive an alert to confirm the selected tone plays

  • Note: If an alert does not include an incident type or does not match a configured group, the Others tone will be used.

  • Note: Device-level notification permissions and volume settings must allow audible alerts.

• Use Case - A user configures distinct tones for structure fires, medical calls, and a separate fallback tone under Others; when an alert is received without a mapped incident type, the app correctly plays the Others tone rather than the default device sound, ensuring the user can immediately recognize and respond appropriately.