Resolved issues

The following resolved issues were fixed in the incapptic Connect 1.39 release:

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.