Resolved issues
The following issues were listed in past release notes as known issues and have been resolved in Release 4.2.
JIRA ID | Platform | Summary | Workaround |
|---|---|---|---|
MBL-5360 | iOS | If the device battery is low (20%) and in sleep mode, and you publish a high severity alert, the push notification delivery is delayed by 5 to 30 minutes. The app does not light upon receiving a new alert and a push notification is received for a alert that was ended 30 minutes before. This is specific to iOS version 11.3. | — |
MBL-5242 | Both | During Region Migration, an application upgrade from 3.3 or earlier to 4.1 does not end Alert and Accountability events immediately. | — |
MBL-3047 | Android | An unknown error is displayed while changing the orientation of a captured image from the Samsung Tablet device | — |
MBL-2156 | Android | The app may not register correctly for push notifications, with or without an error message. | If push notifications are not received, disconnect and then reconnect to your organization. |
MBL-1097 | Both | When the user taps the Emergency button while viewing the Inbox Alerts or the Map view, the app displays the last received message. However, if the user goes back to the All list, the Emergency shows in the messages list and can be modified with additional information or media. | Users should verify that the Emergency has been sent by viewing the All list. |
MBL-1087 | iOS | On iPad, when sending a report in portrait mode, the user cannot select a location on the map because the map is cut off at the bottom of the screen. | Change to landscape and then back to portrait mode. |
MBL-804 | iOS | When publishing an alert from the mobile app, the user can enter more than 100 characters in the title field and more than 2000 characters in the body field. | — |
MBL-736 | iOS | Alerts over 2000 characters get truncated when viewed by the mobile user. | Use no more than 1800 characters. |