Support Article

iOS mobile binary ITMS errors, rejected by Apple App Store

SA-38136

Summary



Attempts to upload a Pega Mobile app for iOS trigger ITMS errors. The Apple App Store rejected the submission. Some of the errors are straightforward: For example, the version number must be set to 1.2 because 1.1.1 is the current version of the Pega Mobile app on the App Store. Other errors indicate that a few icons are missing. The errors related to the framework signing may be related to the Pega 7.2.2 Platform.


Error Messages



ERROR ITMS-90032: "Invalid Image Path - No image found at the path referenced under key 'CFBundleIcons': 'AppIcon20x20'"
ERROR ITMS-90032: "Invalid Image Path - No image found at the path referenced under key 'CFBundleIcons': 'AppIcon83.5x83.5'"

Steps to Reproduce



Submit .the IPA to the Apple App Store.


Root Cause



The default assets branding has a "common_assets" folder with a SVG icon in size 2048x2048. This is used by MobileBuildServer to create all necessary icon sizes automatically. User had migrated an earlier assets branding ZIP file with only the "ios" and "android" folders and without the "common_assets" folder. As a result MobileBuildServer was not able to generate all the required icons; this caused the the problem problem during IPA submission.

Resolution



Perform the following local change:
  1. Corrected the folder structure.
  2. Rebuild the application.
Be sure that you follow these best practices:
  • Allow greater than two weeks for an Apple App Store submission. One to two months is recommended.
  • After the mobile app binary is approved, you can hold the binary in "pending developer release" status indefinitely.
  • After the server URL and log-in credentials are available, submit the mobile app binary to the Apple App Store: there is no reason to wait.
  • It is best to build your binary using the Pega Mobile Build Server with a distribution certificate.
  • The latest Pega Mobile app binaries are built using the latest Swift technology, which requires that all frameworks (libraries) be dynamically linked.
    This is the Apple recommended way and the only way for Swift-based iOS binaries.
    This requires that all frameworks and the Swift folder inside the IPA be re-signed.
  • When updating an existing application, always use the latest assets ZIP file and follow the latest set of instructions.
Important Instructions are likely to change outside of Pega Platform release cycles because they are controlled by Apple and Google.

See the PDN Article, https://pdn.pega.com/troubleshooting-itms-errors-when-submitting-ios-mobile-app-binary-app-store/troubleshooting-itms, which explains how to avoid Apple iTunes errors and submit a valid Pega Mobile app for iOS to the App Store.

Published May 17, 2017 - Updated June 27, 2017


100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.