ERROR ITMS - 90167 No. app bundles found in the package

Question

Before I start writing about the error, I\'m running on macOS Sierra and using Xcode 7.3.1.

So I\'m creating an Archive from my App, I validate the App and it passes

Answer 1

Try This, it worked like a charm for me,

We also facing same issues at time of updated macOS Sierra.

At time of upload build by using Xcode7.3.1 we get an error message

 "ERROR ITMS-90167:"No.app bundles found in the package"

To Solve Error And Upload IPA file On App Store Follow Below Steps

• We export build by using Xcode7.3.1.

-For upload build we use Application Loader V3.6 of Xcode8.

Xcode -> Open Developer Tools -> Application Loader

Follow Below Steps

1) Open Application Loader

2) Choose Build(IPA)

3)Uploading IPA file To app store

4)Successfully Submit Build(IPA)To App store

Your App will uploaded on Appstore,

Hope this is help for some one.

Answer 2

I solved this problem as follows, find your archive in the Organizer, and then:

1. Show in finder

2. Show package contents

3. In the „Wasabi.xcarchive“ file, find the „Products“-„Applications“-„Wasabi.app“(Wasabi is your app’s name), „Show package contents“ again

4. Finally, you can see there has a file named“Info.plist“, open it

5. Edit the value with a key named „BuildMachineOSBuild“, I just change it to „15F34″(it’s „El Capitan 10.11.5“ ’s version)

Answer 3

Problem:

• Issue with the current macOS Sierra build.

Workaround

• Build with Xcode 7.3.1 then upload using Xcode 8 [Beta]. (Thanks to @JollyRoger)
• Currently, this workaround ONLY works for TestFlight and NOT for App Store submissions.

No need for fix [UPDATE]

• So it seems that this bug has lasted for the whole beta period and it might not be worth for Apple to fix it anymore as the final version of iOS 10.0 is releasing in a few days and the final macOS Sierra is releasing a few days after that.
• If you are still getting this issue with the final build of macOS Sierra, make sure you are using Xcode 8.x and not anything earlier than that.

Possible errors:

1. ERROR ITMS-90635

   ERROR ITMS-90635: "Invalid Mach-O Format. The Mach-O in bundle "....framework" isn’t consistent with the Mach-O in the main bundle. The main bundle Mach-O contains armv7(machine code) and arm64(machine code), while the nested bundle Mach-O contains armv7(bitcode) and arm64(bitcode). Verify that all of the targets for a platform have a consistent value for the ENABLE_BITCODE build setting."

   Fix: Uncheck the Include Bitcode option before uploading.

2. INFO ITMS-90111

   INFO ITMS-90111: "Beta Toolchain. This app has been built using beta toolchains. Apps built with beta toolchains are acceptable for TestFlight submission. Note that you will not be able to submit these builds for sale on the App Store."

   Note: This will allow you to upload the build and use it for TestFlight but when trying to submit to the store you will be faced with this error message:

   New apps and app updates must be built with the public (GM) versions of Xcode 6 or later, OS X, and tvOS SDK. Don't submit apps built with beta software including beta OS X builds.

Answer 4

In case this helps, I had the same error code "ERROR ITMS - 90167 No. app bundles found in the package" using mac OS 10.14.4 with Xcode 10.2.

(As a note, I was able to successfully submit builds some weeks ago with the same configuration, but this seems to be something in the iTunes Connect side)

Had to update to mac os 10.14.6 and Xcode 10.3 to successfully submit my build.

Answer 5

These are all fabulous answers above... follow Nicholas's 9 step process above and also Tobeiosdev if you don't have write access to the SystemVersion.plist file.

However be very careful about how you read the step by step guide. DO NOT do as I did and restart your device after editing that plist file, as you will render most applications on your mac useless, including Terminal & TextEdit (which are required to edit it back). Reopen terminal inside Sierra (or the beta OS you are running) not inside the command line.

---

I unfortunately found out the hard way and then could not edit the plist file again in the command line. So I then had to reboot several times before finding the solution which was to go into single user mode (Command-S on restart), all of which scared me senseless that I had ruined the build of my mac. Eventually got everything running again but was somewhat delayed too by having to reinstall Xcode 8... leading to a sleepless night as my first ever submission to the AppStore.

All in all, the above is a perfect solution that works all around, IF you follow the directions correctly. Lesson learnt!

Answer 6

I would first like to thank @xemacobra for his solution, it worked for me until I needed to submit an application for Review.

If you need to submit an application for the App Store, and the build says You may not submit builds using beta software... here is the solution:

The problem is Xcode is sending the build information along with the version of you Mac OS. To fix that, you just need to change your Mac OS build to an older, acceptable, version.

1. Restart your Mac and hold Command + R on boot up
2. Open Terminal
3. Run csrutil disable
4. Restart your Mac.
5. In Finder, go to /System/Library/CoreServices/SystemVersion.plist
6. Open the file so that you may edit the SystemVersion.plist
7. Find <key>ProductBuildVersion</key> and locate the string attached to this key. For example, mine was 16A254g.
8. Change this string to a version of Mac OS that is currently supported for public release. At the time of this solution this one will fine: 15G31
9. Restart Xcode. Re-Archive your application. Re-Submit the application.

I did not try submitting the application through Xcode 7.3.1, but I do know this still works if you submit the .ipa through Xcode 8 beta 3.

Once you have submitted your build, revert the SystemVersion.plist to the original string, and repeat steps 1-4 replacing csrutil disable with csrutil enable.