Resolved issues

This section describes the following resolved issues fixed in the current release of incapptic Connect.

MobileIron Cloud

CON-3463: There was an issue when publishing a version of a Public Store app to MobileIron Cloud when the Version field was left blank. The app publication failed, because Cloud could not resolve the version number.
CON-3458: There was an issue with MobileIron Cloud apps that were republished after an initial failure. The error message from the failed publication attempt did not go away after the app was successfully republished.

CON-2581: There was an issue where a feature not supported for Android apps was appearing in Managed App Settings.

Con-2645: There was an issue with Wildcard Provisioning Profile (WPP) signing failing when its certificate was renewed.
CON-2256: There was an issue where a certificate import would fail if the certificate name contained any spaces. This issue has been resolved.
CON-2434: There was an issue where inappropriate "Provisioning Profile expiration" or "Push Certificate expiration" notifications were emailed when an app was retired.

CON-3439: There was an issue when a new app version for App Store Connect was published, the App Status changes to Binary Error (Check Apple Feedback).
CON-3436: There was an issue with App Store apps not being successfully published. The binary file was not being properly uploaded to the App Store.
CON-3207: There was an issue with screenshots for App Store apps. JPG files that were just renamed PNG were accepted.

CON-3445: There was an issue where unsupported screenshots (webP format) were not being flagged in Google Chrome.
CON-3400: There was an issue when publishing a Google Play Store app, where the publish failed with the error "Publishing failed due to an internal error" when all information was valid.
Con-3116: There was an issue when auto-publishing VMware AirWatch (now Workspace ONE Unified Endpoint Management) apps together with other apps. The Android app would stop responding with the status "Waiting for Provisioning Profile."

CON-3254: There was an issue when publishing an app to Microsoft Intune, where sometimes the app publication would fail, and sometimes a publish that was called successful would not display the latest app version in Intune. Publishing apps to Microsoft Intune now works as expected.
CON-3462: There was an issue with iOS apps having a minimum iOS version lower than iOS 8 failing registration to Microsoft Intune.
CON-3104: There was an issue with iOS and Android apps published to Microsoft Intune when the apps had more than 1024 characters in the Notes field. This violation did not generate the expected error message and the publication failed.

CON-3419: There was an issue regarding the display size of the app name for App Owner accounts.

CON-3452: There was an issue with log entries when a user was assigned as a Developer for an app. The log entry erroneously displayed the name of the user in the App Role Assignment field, instead of the User ID of the user.
CON-3221: There was an issue in which the Create new test label and apply button erroneously displayed in the Settings > App level of non-MobileIron Core apps, such as Microsoft Intune and VMware AirWatch (now Workspace ONE UEM).
CON-3204: There was an issue in which the Periodical Target Connection status check did not work as expected, and did not start a connection status check immediately after unlocking the keychain.
CON-2672: There was an issue in the Rejection History page. When the Reply button was clicked multiple times, it would submit the reply multiple times, as well. Even if Reply is clicked several times in rapid succession, the system now blocks extra clicks from sending duplicate emails.
CON-2563: There was an issue in the Clone current version to new version window. The first field was erroneously labeled Version Name (CFBundleShortVersionString). The label now reads Version Number (CFBundleShortVersionString).
CON-3367: There was an issue when a user requested a new app that was already registered under a different name. The option Import with different name failed to correctly register the app under the new name. The Import with different name option now works as expected.