MBL-17339

Android, iOS

Tapping the location pin in a received alert did not open the location or pass coordinates to the device's default navigation app.

MBL-17390

Android

On Android devices, the BlackBerry AtHoc mobile app failed to load any alert template whose name started with a digit (for example, "00. Test Alert Template"). This issue did not occur on iOS. The root cause was an inability to parse the TargetOrganizations.TargetOrg field when it was formatted as a JSON array.

The mobile app now correctly parses the TargetOrganizations.TargetOrg field when formatted as a JSON array, allowing alert templates starting with a digit to load as expected on Android devices.

MBL-17005

Android

The "No Status" count for an accountability event differs between Android and iOS. On Android, the count includes all targeted users and dependents for the event, while on iOS it includes only the users the accountability officer is authorized to respond on behalf of. This discrepancy can cause accountability officers on Android to misinterpret the scope of users they must account for.

MBL-16737

iOS

In mobile release 4.17, a newly added privacy policy and data management statement on the Home screen was not localized into French, causing it to display in English regardless of the user's selected language.

MBL-17339

Android, iOS

The mobile app's automatic link-detection logic was incorrectly processing certain character patterns and numeric strings within alert content, causing two issues.

• By design, text surrounded by exactly three asterisks (for example, ***123 Main Street***) is rendered as a clickable address link that opens the device's native map application. However, text surrounded by any other number of asterisks was also being incorrectly rendered as a clickable link. With this fix, only text surrounded by exactly three asterisks will render as a clickable address link. Any other asterisk count (for example, ****123 Main Street****) will render as plain, non-interactive text as expected.
• When an alert body contained an address, the numeric portion was incorrectly detected as a phone number on Android devices, causing the device dialer to open when tapped. Address strings are no longer misidentified as phone numbers.

MBL-16737

iOS

In mobile release 4.17, a newly added privacy policy and data management statement on the Home screen was not localized into French, causing it to display in English regardless of the user's selected language.

MBL-16736

Android

The mobile app's automatic link-detection logic was incorrectly processing certain character patterns and numeric strings within alert content, causing two issues.

• By design, text surrounded by exactly three asterisks (for example, ***123 Main Street***) is rendered as a clickable address link that opens the device's native map application. However, text surrounded by any other number of asterisks was also being incorrectly rendered as a clickable link. With this fix, only text surrounded by exactly three asterisks will render as a clickable address link. Any other asterisk count (for example, ****123 Main Street****) will render as plain, non-interactive text as expected.
• When an alert body contained an address, the numeric portion was incorrectly detected as a phone number on Android devices, causing the device dialer to open when tapped. Address strings are no longer misidentified as phone numbers.