Resolved issues

• CON-3745: In previous releases, when you clicked the re-upload button for the Microsoft Intune binary, duplicate metadata was created, causing an error code 500. In this version, the upload works as expected.

• CON-3740: In previous releases, when you clicked the re-upload button for the Google Play binary, duplicate metadata was created, causing an error code 500. In this release, re-uploading works as expected.

• CON-3737: In previous releases, the Android app binary upload was rejected if the binary contained WebP or XML based icons showing the error message 'Icons not found'. Now app binaries with WebP icons are accepted and properly processed. Apps binaries with XML icons are rejected with the error message that XML icons are not supported. You must provide a binary with either PNG or WebP icons.

• CON-3720: In previous releases, email notifications could not be muted on the SSO system. In this release, email notifications on the SSO system can be muted.

• CON-3695: In previous versions, when you created an app with the App Store as the target, then tried to reupload a binary, the reupload failed with the following message: Processing of <version number> has failed. Internal error occurred. Our team has been notified. Please try again later. In this release, the reupload works as expected.

• CON-3672: In previous versions, if you create a new app with both iPhone and iPad support, uploaded both iPhone and iPad screenshots to the metadata, then created a second version of that app that only has iPad support, both types of screenshots were erroneously uploaded to the second version. Only iPad screenshots should have been uploaded. In this version, only the correct screenshots are uploaded.

• CON-3609: In previous versions, incapptic Connect allowed you to create app titles that were up to 50 characters long, which resulted in an error because Google Play Store only accepts 30 characters. Starting in this version, incapptic Connect allows only 30-character titles.

• CON-3446: In previous versions, the Ivanti EPMM target version was incorrectly displayed in the target details field. In this version, the information is displayed correctly.

• CON-3320: In previous versions, the Apple Store Targets page incorrectly displayed the status Connection Error even when you entered the correct credentials and tokens. In this version, the status displays as Connected.

• CON-3251: In previous versions, you could not rename an iOS app after creating it. The ability to rename your iOS app after you create it was reintroduced in this release. Special characters are not allowed in the app name.

• CON-3007: In previous versions, when you tried to re-sign an app configured with Sign In, that also had an Apple entitlement configured with the IPA, the re-signing failed and the system returned an entitlement error. In this version, the re-signing occurs as expected.

• CON-2620: In previous versions, when you tried to re-sign an app configured with Wi-Fi entitlement in the IPA, the re-signing failed and the system returned an error. In this version, the re-signing is working as expected.

• CON-3673: There was an issue where publishing to App Store Connect failed due to API changes at Apple. This issue has been fixed. Publishing to App Store Connect now works as expected.

• CON-3664: Previously, there was a security issue where a non-admin user with user management permission could gain access to an admin account. This issue has been fixed. Non-admin users cannot take over admin accounts. For more information, see the knowledge-based article Security Advisory for incapptic Connect SA-2022-03-10.

• CON-3654: There was an issue in which a particular set of user permissions could have potentially misused an incapptic Connect API to execute code remotely. This issue has been fixed. The potential for this misuse has been eliminated.

• CON-3601: For incapptic Connect systems with local user management, an administrator can push a button to send a link to the user to reset their password. However, for single-sign on systems (SSO), the authentication is managed by the SSO system and not incapptic Connect, but the option remained. The issue was fixed in this release by removing the Password Reset option for SSO systems.

• CON-3600: Single sign-on (SSO) systems did not have the same ability to resend or withdraw a device invitation that other systems had. With this release, SSO systems have the capability to withdraw or resend a registration invitation.

• CON-3592: There was an issue where some Android Application Package (APK) files were rejected, because an obfuscation software changed the location of the app icons inside of the file. This bug is fixed. Android apps that have been changed are now accepted by incapptic Connect.
• CON-3578: incapptic Connect reports would sometimes fail to fully download. This issue was fixed. Reports now download completely.

• CON-3562: There was an issue whereby incapptic Connect logs showed an incorrect user name when approving or rejecting an app publish request. This issue is fixed. Logs documenting these events now include the correct user name and user ID.

• CON-3553: There was an issue with uploading feature graphics or icons larger than 1 MB to Google Play store. incapptic Connect accepted the image, but the upload to Google Play store would fail, because Google does not accept files larger than 1 MB. This issue has been fixed. If a user tries to upload a feature graphic or icon to incapptic Connect that is too large, incapptic Connect prevents the upload and provides a warning to limit icon size to under 1 MB.

• CON-3546: There was an issue with incapptic Connect email notification URLs. The "deep" links to the app version did not work correctly for users authenticating through single sign-on (SSO) systems. This issue has been fixed. Users authenticating through an SSO can tap the deep link and be redirected to the correct app version URL.

• CON-3532: There was an issue in which app binary files with the same version numbers but different build numbers were allowed by incapptic Connect, but were rejected by VMWare Workspace One servers, because they require a new version number with each upload. This issue has been fixed. App binary uploads that are not allowed by the target servers are now blocked and users notified.

• CON-3517: There was an issue with re-signed Android apps not installing on client devices. This was due to occasional corruption of the zip file during the package process. This issue has been resolved. Android apps can be successfully pushed to client devices after re-signing.

• CON-3501: There was an issue where the status of an app would not sync with Apple App Store Connect if there were errors in the metadata. This issue was fixed. If an app is rejected by App Store Connect due to metadata errors, or the status otherwise changes, the app status syncs properly.

• CON-3447: There was an issue where the Microsoft Intune Settings tab was shown to users that did not have the permission to view the tab. This issue is fixed. Only users with the permission to see the Intune Settings tab now see the tab.

• CON-3443: There was an issue with failed binary uploads being reported in the global log, but not reported in the application (tab) log. This issue has been fixed. Binary upload attempts are correctly logged in both the global and application logs.

• CON-3438: Previously, Core apps with long version numbers did not display correctly in incapptic Connect Device Installation Overview page, because the number was overlapped by the chart. This issue has been fixed. The version number now displays correctly.

• CON-3375: There was an issue when attempting to automatically publish an app to one or more systems, including MobileIron Core, MobileIron Cloud, VMWare Workspace ONE, and Microsoft Intune. Instead of publishing the apps, they stayed in the Queued for code signing status. This issue has been fixed. The Auto Publish feature works as expected.

• CON-3261: There was an issue in which incapptic Connect would allow the cloning of an app binary file that did not adhere to the target requirements (for example, invalid version or build number). This issue has been fixed. Now incapptic Connect properly validates the app binaries.

• CON-3226: Previously, if an attempt to auto-publish an app to AirWatch failed, it could cause incapptic Connect to become unresponsive in the "Queued for Signing" process. This issue has been fixed. With this release, if an attempt to auto-publish an app to AirWatch fails, the console will respond appropriately with a "Publishing failed" message.

• CON-3199: There was an issue with the incapptic system becoming unresponsive for short periods when apps were being signed or published. This issue has been resolved. The incapptic system remains responsive during app signing and publishing activities.

• CON-2870: App for Kids information is now shared with App Store Connect. Before an app is published to App Store Connect, incapptic Connect asks a series of questions, including whether or not the app is appropriate for children, and the appropriate age ranges. Previously, the "Made for Kids" metadata was not transferred to the App Store. With this release, Apps for children will include all the necessary information, including the appropriate age range for the app.

• CON-3552: There was an issue within the Binary Details section, in which MI Wrapped and MI SDK version information were incorrectly displayed under Submitted Binaries, and were missing for Wrapped versions. This issue has been fixed. All entries in the Binary Details section are correct and appropriate.

• CON-3531: There was an issue with wrapped iOS apps failing to install and run in iOS 15. This issue has been fixed. With this release, both "signed" and "wrapped" iOS app files install and run correctly in iOS 15.

• CON-3530:  There was an issue with an iOS app with WatchKit extensions being unable to re-sign successfully when uploaded via the Application Programming Interface (API). This issue has been resolved. iOS apps with WatchKit extensions can now be successfully re-signed using the API.

• CON-3528: There was an issue with unsigned iOS App Store Package (IPA) files being rejected during app uploads, even when the system was set to allow the uploading of unsigned IPA files. This issue has been resolved.

• CON-3526: There was an issue where the App Reject button was visible to a user who was not the Owner for the App, but rather a Developer. This issue has been fixed. With this release, a user will only see the Reject button when viewing an app in which he or she is the owner.

• CON-3524: There was an issue with Google Play Store allowing screen shots above 8 MB to be successfully uploaded while in Draft mode, but failing during publishing due to excessive image size. This issue has been fixed. incapptic Connect will not allow you to upload an image above 8 MB to Google Play Store.

• CON-3515: There was an issue in which valid Google Play Store screen shots were rejected by incapptic Connect as "out of range." This issue has been fixed, with all valid screen captures accepted:

  • JPEG or 24-bit PNG (no alpha)
  • Minimum dimension: 320px
  • Maximum dimension: 3840px

The maximum dimension of your screen shot cannot be more than twice as long as the minimum dimension.

• CON-3484:  There was an issue with Google Play Store not updating and storing new graphics when replacing old ones. This issue has been fixed. Now graphics updates will refresh immediately, displaying the new graphics.

• CON-3481: There was an issue in which Apple Team session keepalive requests were repeating inappropriately, causing Core to send repeated incorrect SMS messages. This issue has been fixed. Apple Team sessions remain valid, and they do not generate unnecessary messages.

• CON-3473: There was an issue when some role modifications were not captured in the event logs. This issue has been fixed, and all role modifications for scoped and global role generate correct log information.

• CON-3469:  There was an issue where an Android app bundle (AAB) file for Google Play Store could not be published, if an app release with the same version and build number was already published in the Google Play Store internal track.

• Publishing as a production release does not actually publish the AAB file in incapptic Connect, but rather promotes the existing release published in the internal track to the production release track.

• CON-3465: There was an issue with log entries for the expiration of Apple developer team sessions displaying an internal ID number instead of the team name. This issue has been fixed. The log entry now includes the team name as defined in the certificate settings as well as the team ID as shown at Apple.

• CON-3456: There was an issue in which the AppConnect iOS SDK 4.8 version number was not displaying properly in the Binary Metadata sections. This issue has been fixed. With this release, the correct SDK version number displays in the appropriate metadata fields.

• CON-3415: There was an issue in which the Re-upload to App Store button was not displaying as expected when an app publish failed and App Owner approval was enabled. This issue has been fixed. If an app version fails to upload, the Re-upload to App Store button now displays as expected.

• CON-3388: There was an issue with incapptic Connect not sending an email notification to warn admins of an expiring Provisioning Profile, if app signing for one or more apps was disabled. This issue has been fixed. A soon-to-expire Provisioning Profile generates a reminder email as expected.

• CON-3376: There was an issue whereby high-resolution icons and example screen captures were not being successfully published to Google Play Store. This issue has been fixed. With this release, necessary assets are uploaded to Google Play Store as expected.

• CON-3296: There was an issue where incapptic Connect would stop responding during app signing if custom images were not in the expected folder. This issue has been fixed. With this release, incapptic will abort the app signing and notify the user of the missing images.

• CON-3266: There was an issue where an Android application package (APK) file could not be uploaded due to the app icon file residing in a non-standard folder. This issue has been fixed. This APK file can be uploaded as expected.

• CON-3215: There was an issue in which older iOS Team Distribution certificates were not being replaced with new ones when the app was cloned. This issue has been fixed. In this release, if you upload an iOS Team Distribution certificate that is newer or has a longer validation period, incapptic Connect will use the new certificate for app signing.

• CON-3197, CON-3195: There was an issue in which the Localizable Metadata command Copy from Default language to other languages did not copy the screen shots from the default languages to other selected languages. This issue has been fixed. The Copy from Default language to other languages option now works as expected.

• CON-3192: There was an issue in which incapptic Connect allowed 6.5-inch, 16-bit/color RGBA screen captures to be submitted to Apple App Store, where they would be rejected as incompatible. This issue has been fixed. With this release, if a non-supported 16-bit/color RGBA screenshot is selected to be uploaded to Apple App Store, incapptic Connect warns the user to submit a screenshot in a supported color scheme, such as 8-bit/color RGBA.

• CON-3159: There was an issue in which Google Play Store app publications were failing because incapptic Connect could not validate the screen captures, although they were in the expected folders. This issue has been fixed. With this release, publishing an app to Google Play Store with attached screen shots works as expected.

• CON-2665: There was a reporting issue in the Extended App report, which listed incorrect versions of the MobileIron SDK and MobileIron wrapper. This issue has been fixed. With this release, the Extended App report displays only the wrapper version for all wrapped apps, and displays only the SDK version for all SDK apps.

• CON-2471: There was an issue with log files displaying the wrong user name when one user (User A) rejected an app from another user (User B). The log file would list User B as the rejecting user. This issue has been fixed. Log files now display the correct user when an app is rejected.

• CON-2264: There was an issue where the Alternate Price Tier value was neither stored nor transmitted to App Store Connect. This issue has been fixed. All Price Tier values are now correctly stored and transmitted.

MobileIron Cloud resolved issues

• 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.

Ivanti EPMM Core resolved issues

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

iOS resolved issues

• 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.

Apple App Store resolved issues

• 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.

Google Play Store resolved issues

• 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."

Microsoft Intune resolved issues

• 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.

User Interface resolved issues

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

Other resolved issues

• 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-Ivanti EPMM(Undefined variable: Primary.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.