Geek Answers Handbook

Can't send ios app to view after installing osx security update

I installed the latest osx security update ( https://support.apple.com/en-ca/HT207130 ) and tried to archive the update for my ios application. The archive was successful. However, after loading the assembly in itunes to connect to the application loader, I received the following email:

enter image description here

When I tried to send my application for viewing, I received the following error message:

enter image description here

I obviously do not launch the beta of macos or xcode. Here is my setup: OSX El Capitan 10.11.6, Xcode 7.3 (7D175)

Does anyone have the same problem? How did you get around this?

+5
source share
3 answers

Since there were many errors in iTunes Connect that Apple still cannot solve on macOS Sierra (10.12) when downloading the archives (assemblies) of our applications,

You should use Xcode 8 no matter what on macOS Sierra

These are common errors that occur when downloading our archive from Xcode 7.3.1 to macOS Sierra (10.12)

  • ITMS ERROR - 90163 (Pack.App detected)
  • Now your problem

Changing the build version or Xcode version from info.plist does not work. Believe me, I tried many alternative hacking methods. Finally I gave up. Instead, install Xcode 8 and Xcode 7.3.1 in parallel on my mac because I'm not ready for migration.

Archive your build with Xcode 7.3.1 and export its ipa from the version of the App Store. Then use the Application Loader for Xcode 8 to load your assembly into the App Store.

I hope for this help.

+1
source

From this thread , try the following:

I was able to send without warning or error, breaking into .xcarchive and changing the info.plist of the application. Key change
<key>BuildMachineOSBuild</key> <string>15G1004</string>
value for the original 10.11.6

<key>BuildMachineOSBuild</key> <string>15G31</string>

Then export the IPA or send it to the application store as usual.

I did not test, so it could not fix your problem.

+1
source

From the same thread , this seems to be a recurring issue when releasing security updates.

If the @ marco-santarossa method does not work, you can wait for Apple to update iTunes Connect to accept the new version of the OS build, or contact support, hoping they can speed it up.

I did, and after a few hours, the same assembly that I downloaded was sent for review.

0
source

More articles:


All Articles