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

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.

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.

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.