Version - 7.0.8 

New Features

1. No New Features.

Feature Enhancements

• No new Features Enhancements.

Fixes

• Critical Production Crashes: WebView, Glide, HashMap Concurrency, and Location OOM Issues 

  • What - Resolved multiple critical Android crash scenarios by improving fragment lifecycle safety, correcting WebView inflation/initialization, and preventing callbacks from executing after a fragment has been destroyed. These changes reduce occurrences of Resources$NotFoundException, FragmentManager transaction conflicts, and other lifecycle-related failures that could happen during navigation, background operations, or when returning to the app.

  • Why - These crashes were occurring when app components outlived their expected lifecycle (such as callbacks firing after a screen was closed) or when UI elements were created in an unsafe state (such as WebView being inflated incorrectly). Fixing these issues improves reliability in the field by preventing unexpected app exits during common workflows like switching screens, multitasking, or operating with location services enabled.

  • How

    • Navigate and use the app as normal—this fix is automatically included in the updated Android build.

      • Notes

        • If your organization manages mobile deployments, ensure users are updated to the latest Android version to receive these stability improvements.

        • If you continue to see unexpected exits after updating, capture the approximate time and workflow steps leading up to the issue and share logs through your standard support process.

  • Use Case - A responder opens a map view, switches to another screen, and then returns while the app is processing background updates (such as location or image loading). Previously, delayed callbacks could attempt to update a screen that was already closed, triggering a crash; now, lifecycle-safe handling ensures those background operations are ignored or safely completed without interrupting the user’s workflow.