Known issues
The following tables list known issues based on the release version that first had the issue.
4.17
|
Jira ID |
Platform |
Summary |
Workaround |
|---|---|---|---|
|
MBL-16579 |
Android |
Automatic registration may fail for users on iOS when using super enterprise organization codes through MDM deployment. Users may experience a registration error screen despite having their organization code and email pre-populated correctly. |
If automatic registration fails, manually re-enter the same organization code on the registration screen to successfully complete the registration process. |
4.16
|
Jira ID |
Platform |
Summary |
Workaround |
|---|---|---|---|
|
MBL-16291 |
Android |
Published alerts containing location information display different location details on Android and iOS mobile devices, even when published from the same source. |
— |
|
MBL-16029 |
iOS |
Push notification sounds for high severity alerts are truncated. |
— |
|
MBL-15932 |
iOS |
When using the Chat feature, when an undelivered message is sent after the network becomes available, it appears twice on the chat screen. This issue occurs only when the Chat feature is enabled. |
— |
4.13.1
|
Jira ID |
Platform |
Summary |
Workaround |
|---|---|---|---|
|
MBL-12853 |
iOS, Android |
The "Exercise" alert type displays the "Other" alert type icon. |
Update to mobile release 4.14. |
|
MBL-12862 |
iOS, Android |
The "Exercise" alert type string is not localized for all supported languages. |
Update to mobile release 4.14. |
4.13
|
Jira ID |
Platform |
Summary |
Workaround |
|---|---|---|---|
|
MBL-12432 |
iOS |
Users on iOS 17 may receive multiple alert push notifications if they receive an alert within 4-5 minutes after upgrading to mobile app release 4.13. |
— |
4.12.1
|
Jira ID |
Platform |
Summary |
Workaround |
|---|---|---|---|
|
MBL-12253 |
iOS |
Users on iOS 17 receive multiple alert push notifications. |
Upgrade to mobile app release 4.13. Open the app after the upgrade. |
|
MBL-12387 |
iOS |
Users on iOS 17 see alert push notifications reappear even after viewing an alert. |
Upgrade to mobile app release 4.13. Open the app after the upgrade. |
4.11
|
Jira ID |
Platform |
Summary |
Workaround |
|---|---|---|---|
|
MBL-10456 |
Android |
The approximate location is not updated when sending an emergency using a blue tooth button when the mobile app is in the background or in a 'killed' state. |
— |
4.6
|
Jira ID |
Platform |
Summary |
Workaround |
|---|---|---|---|
|
MBL-7573 |
iOS |
On the collaboration screen, the footer at the bottom appears blank, which makes the chat look like it is clipped. |
— |
|
MBL-7584 |
iOS |
On the collaboration screen, the header scrolls. |
— |
4.4
|
Jira ID |
Platform |
Summary |
Workaround |
|---|---|---|---|
|
MBL-6864 |
Android |
The file name of an attachment is different in the alert details screen than the file name when the attachment is opened. |
— |
4.2
|
Jira ID |
Platform |
Summary |
Workaround |
|---|---|---|---|
|
MBL-2070 |
Android |
Unable to do a manual refresh to view the latest information in the Delivery Summary section. |
— |
|
MBL-3433 |
Android |
Device is connected to the internet but the "No network connectivity" banner is still displayed. |
— |
|
MBL-5581 |
Android |
When the user is switching organization and sends an emergency using the 3D Touch app short cut, the emergency is not sent successfully. |
— |
|
MBL-6862 |
Both |
Video recorded from a phone device while sending an emergency is blurry when the video is added as an attachment. |
— |