Resolved issues
These are cumulative release notes. If a release does not appear in this section, then there were no associated resolved issues.
- APIM-7773, SET-22222: Previously, the Email+ Android Enterprise app was unable to open .PDF file attachments with the Docs@Work app. This issue has been fixed.
- APIM-7727: Previously, the Email+ app stopped responding when a new event was created or an existent event was opened on a Samsung S8 device with Android 7. The issue has been fixed.
-
APIM-7664: Previously, when the Email+ app was configured with Modern Authentication and the value for the email_exchange_host key-value pair was changed from "exchange server" to "sentry", the following issues were observed:
-
Notes and tasks failed to sync
-
The account icon and display name were not displayed
These issues have been fixed.
-
-
APIM-7601: Previously, the Email+ app did not display an error message when there was no supported app available to open an attachment when the download notification was tapped. This issue has been fixed.
-
APIM-7544, SET-21747: Previously the Email+ app would display deleted mails in the inbox. The issue has been fixed.
-
APIM-7224, SET-20927: Previously, the Email+ AppConnect app would stop responding on the Huawei AGS2-L09 device. This issue has been fixed, use Secure Apps Manager 9.4.0.0 with the Email+ app.
-
APIM-7107, SET-20939: Previously, the Email+ app would resync when the LDAP email address case was changed. The issue has been fixed.
- APIM-7762, SET-22149: Previously, the Email+ AppConnect app would stop responding after receiving two or more mail notifications when the allow_detailed_notifications key-value pair was set to true. This issue has been fixed.
- APIM-7742, SET-22081: Previously, the mails were getting stuck in the Outbox folder and were sent in an incorrect order. This issue has been fixed.
-
APIM-7301: Email+ for Android now sends auto encrypted replies for encrypted messages.
-
APIM-7104: Previously, the users were unable to login to the Email+ app with certificates after the first launch. This issue has been fixed.