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 validation, but when uploading to App Store, I get the error "ERROR ITMS - 90167 No. app bundles found in the package".

I've checked all my documentation and I have everything.

• I have all my provisioning profiles.
• I have Release as "iOS Distribution".

This error just started appearing after I installed macOS Sierra.

Anyone has an idea of why I'm getting this error?

Answer 1

Maybe it's about your disk space check your disk space.

Answer 2

Go inside your Appstore and download the new version of Transporter. this worked for me

Answer 3

I had to provide missing application name in order to fix this problem.

Answer 4

I faced the same problem . what worked for me was ->

go to target-> signing & capabilities -> signing certificate -> I had to revoke one certificate. Always revoke the Certificate by the name of admin's iMac . It is created by default while making your certification and profiles.

**Picture is attached for the reference.

PS:- always make sure the bundle id is same on App store connect and Xcode before archiving.

Answer 5

Unable to process application at this time due to the following error: No .app bundles found in the package. This issues appear when your pc's space is less. So clear you trash or some useless document from you pc. Then let's try again! It's work for me!

Answer 6

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 7

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 8

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 9

I was having this issue with Xcode 8 GM and trying to submit an app for release though Application Loader.

You have to use the version of Application Loader that comes with Xcode 8, which should be 3.6

I still have Xcode 7 installed, and was using Application Loader 3.5

Update

• My apps submit okay now and go into processing, then soon after disappear completely. I think this might be a separate issue though.

Update 2

• You still can't use Sierra to submit your apps. At least not until they release the GM.

Update 3

• This issue is still occurring with this particular project. All other new ones (sticker apps) that I have created since public launch have been submitted to iTunes Connect with no issues.

I worked on this project during the betas, so it's possible something has been corrupted along the way and is causing issues. Might require starting a new project in Xcode 8.

There's a thread on the developer forums addressing this issue. https://forums.developer.apple.com/thread/62703

Solution

Turns out the fix for us was to add the "NSCameraUsageDescription" key to the info.plist with a description of what the camera does in the app.

Not sure if that solution will help in all cases though.

Answer 10

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 11

I was getting this error with Xcode 7.2.1 and Application Loader 3.4 on macOS 10.12.1.

But for some reason, it worked if I used the command-line "altool" to do the upload instead:

'/Applications/Xcode-7.2.1.app/Contents/Applications/Application Loader.app/Contents/Frameworks/ITunesSoftwareService.framework/Versions/A/Support/altool' \
  --upload-app -f your-app.ipa \
  -u your-apple-id -p your-apple-id-password \
  --output-format xml

Answer 12

I accidentally opened an old version of the Application Loader Version 3.5 (921) and got the error ITMS-90167 no app bundles found. Be sure you open the Application Loader over the menu of Xcode (Xcode->Open Developer Tool). Version 3.6 (1020) works like a charm! :)

Answer 13

I recently upgraded to macOS Sierra and also received this error message. After uploading through the application loader failed.I downloaded Xcode 8 (kept my 7.3.1 copy). Closed Xcode 7.3.1. Opened Xcode 8-> Organizer-> proceeded to validate and upload my build. It worked. Hope this helps someone in a similar situation.

Answer 14

The privacy settings are changed for iOS 10, more on this could be read here

I had previous described issues, which had to be solved as described, but after successful upload application wasn't visible on iTunes connect.

I had to add Privacy - Bluetooth Peripheral Usage Description key in a plist in order to solve the last one. Other missing keys will make the same problem.

Answer 15

If you are uploading from Xcode7(less than Xcode8) and macOS Sierra(V10.12), So this issue "ERROR ITMS-90167: "No .app bundles found in the package"" will come and will not allow to upload build to AppStore.

So use "Application Loader V3.6" or "Xcode8" to upload the build.

Answer 16

Try open App Loader from Xcode8. Xcode > Open Developer Tools > Application Loader

Then you can upload app to TestFlight without the error.

Answer 17

I have also experienced the same. This is the simple way to solve your problem. Archive your app using Xcode 7.3.1 and export the ipa file of your app into a directory by selecting the option Save for iOS App Store deployment.

After that open Xcode 8.0 and open Application Loader from Xcode -> Developer Tools. Sign in to your team, and upload the ipa file using Xcode 8.0.

I have uploaded two apps to iTunesConnect, it will work for sure.

Answer 18

With me, my application writing by Swift 2.2. And must use Xcode 7.3.1 to archive and upload to Apple testflight but got the same error(I run on macOS Sierra-10.12). The follow solution fix it for me, hope another who face the same problem can find somethings helpful:

1> Use Xcode 7.3.1 to archive
2> Export to file .ipa
3> Quit Xcode 7.3.1 then open Xcode 8, and then open Application Loader, use Application Loader to upload file .ipa to itunes connect.

Answer 19

I submit an app built using LibGDX and had the same issue after upgrading to Sierra. I solved it by:

• Upgrading Xcode (8.x), as explained above
• Use the latest version of appLoader (3.6). To do that, use the AppLoader available within Xcode. I was using a standalone version of the appLoader: that's incorrect. Open Xcode and go to Xcode->Open Developer Tool->Application Loader

Answer 20

According to @Fan Zhang answer follow these steps and you can upload this archive use Xcode or Application Loader, whatever you want!

When you archived your app, find your archive in the Organizer, and then:

-->"Show in finder";
-->"Show package contents";
-->In the "xx.xcarchive" file, find the "Products"->"Applications"->"xx.app"(xx is your app's name), "Show package contents" again;
-->Finally, you can see there has a file named"Info.plist", open it;
Edit the value with a key named "BuildMachineOSBuild", I just change it to "15F34"(it's "EI Capitan 10.11.5" 's version);

Answer 21

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 22

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.

Answer 23

After chatting with folks at WWDC in both the Xcode lab and the App Store lab, they were able to dig up information that this is a known issue in the current Sierra seed that is fixed in the next release. You can either revert, or wait. Not the most satisfying answer, I admit.