After experimenting a bit with SwiftUI making a new iOS app; I just got to the point where I want to put it on TestFlight to start testing with more people.
But this is where I am hitting a new problem.
After archiving, here is what I get when trying to upload the archive to iTunes Connect:
Provisioning profile failed qualification
Profile doesn't match the entitlements file's values for the application-identifier and keychain-access-groups entitlements.
As far as I can tell, I am not doing anything more or less than I always did in the past, when uploading a new app.
Here is what I can say about the app:
It is using SwiftUI. (This is the first time I upload a SwiftUI app, if that ever matters here)
It is using Core Data.
It is using MapKit.
It is using location triggered notifications.
For the environment:
I just upgraded Xcode to version 11.6 (11E708)
I am using Mac OS Catalina version 10.15.6.
Is there anyone who has faced the same situation before?
Or is there something to check knowing the information above?
I'm having the same problem since around July.
Here is what worked for me.
Archive the project on Xcode11,
Open the Organizer window on Xcode12 Beta
And as usual, you can try uploading from there,
BUT in my case, Here, I faced another issue saying failed to 'APP STORE connect operation error'.
If you face this same error like this, then here are other steps you should take.
Download 'transporter' from the Mac app store.
on the Xcode 12 Beta organizer window, instead of uploading the app, click export the app.
Then open the transporter, and add the file you just exported, then you will see 'Deliver' button. After clicking it , in my case, the app was uploaded in a couple of minutes.
Hope it works for you too.
Xcode11: Version 11.5 (for archive)
Xcode12: Version 12.0 beta (for exporting a project on organizer)
My Mac: macOS Big Sur Version 11.0 Beta
The problem is because you need to check the capabilities. The capabilities in the project needs to be equal to which you configurated in the section of "Certificates, Identifiers & Profiles" in the app. In this question you can find more info
I'm facing this issue where my .ipa file installs and runs perfectly on some physical iOS devices. It however, just remains darkened (the logo) after installing on some iOS devices. Now, I've checked the architecture and the build covers all the necessary architectures. I've checked the min sdk too and it more than covers what I need. So I for one am baffled as to why my flutter application only runs on certain iPhones (physical). It runs on all simulators tho.
Photo of darkened logo:
What happened was it became dark and started installing like any iOS app would but after installing, it just remained darkened and was not-clickable. I'm using diawi to generate the link to help the iPhones to download the ipa.
Does anyone know what might be a potential cause for this ?
You must add Device UDID in provisioning profile to get installed on it. If you are making build link via Diawi. You can see all added UDID there.
There should be few reasons where ipa file should not work on few devices where it works on other ones. Here is the listed below :
Device in which you are trying to install, UDID is not added to the provisioning profile
Link you created for ipa file installation gets corrupted
Site which are using for creating iPa installation link contains installation limits
Installation link gets expired after few days due to free version you are using
Suggestions :
If you are using http://diawi.com try it with Login. So it will give you more time before expiration of the link
Try https://www.installonair.com for making links for installation. Its damn easy to use & works well.
Hope this helps everyone.
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?
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.
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:
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.
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.
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.
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.
Restart your Mac and hold Command + R on boot up
Open Terminal
Run csrutil disable
Restart your Mac.
In Finder, go to /System/Library/CoreServices/SystemVersion.plist
Open the file so that you may edit the SystemVersion.plist
Find <key>ProductBuildVersion</key> and locate the string attached to this key. For example, mine was 16A254g.
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
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.
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.
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.
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
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!
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.
Maybe it's about your disk space check your disk space.
Try open App Loader from Xcode8.
Xcode > Open Developer Tools > Application Loader
Then you can upload app to TestFlight without the error.
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!
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! :)
I solved this problem as follows, find your archive in the Organizer, and then:
Show in finder
Show package contents
In the „Wasabi.xcarchive“ file, find the
„Products“-„Applications“-„Wasabi.app“(Wasabi 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 „El Capitan 10.11.5“ ’s version)
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);
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.
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.
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.
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.
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
I had to provide missing application name in order to fix this problem.
Go inside your Appstore and download the new version of Transporter.
this worked for me
I am trying to run ipa files on someones iPhone and I don't have access to the device. He is installing easily but when he tries to open the app then it goes blank. It may be because of permission which he needs to give, but he is not able to see the option of profile in settings. I installed on my iPhone with the help of “diawi” site very easily, which provides one link to install.
I am trying to use testflight now. Before using it I have to upload a build from archives in appStore(option in organiser of upload to appStore). Sometimes I upload it successfully but cannot see the build in iTunes. Bundle identifier is the same at both places and I think all certificates are also ok. Sometimes it also gives error like “ERROR ITMS-90534: Invalid Toolchain”. And some other errors sometimes. Thanks for reading this question.
Problem was with the xcode Version 7.3.1 (7D1012). When I upgraded my xcode to Version 8.0 (8A218a), then I am able to upload successfully. And yes, use applicationLoader.
In order to upgrade Xcode to 8.0 u need OS X El Capitan 10.11.6 atleast.
My company has an app that can be downloaded through a website using Enterprise Distribution.
In iOS 9, tapping the download link brings up the expected pop-up "(website) would like to install (App Name)". Tapping 'install' on that dialog first causes the app to get stuck "Waiting..."
App stuck waiting
Until it finally indicates: "Unable to Download App (app name) could not be downloaded at this time."
Unable to Download the App
Installing works as expected using iOS 7 and iOS 8.
How do we support Enterprise Distribution in iOS 9?
Apple has silently changed how Enterprise Distribution works several times, so knowing the answer to this question will not actually benefit you in the long run. How to find the answer to your question the next time will benefit you most.
Connect your device with the shiny new iOS version to your Mac running Xcode, and open the Devices organizer. Select the device, and optionally clear the log. Now open your app distribution page and try to install the app (clear any previous versions of the app off the device first), and keep an eye on the log output. Here you will find hints as to what you need to change.
For iOS 9.1, I saw the error: BundleValidator: Failed bundleIdentifier: com.example.appName.XXXX does not match expected bundleIdentifier: com.example.appName, which means that the bundle-identifier in the project plist file did not match the Bundle Identifier from the project. I remember adding .XXXX to the bundle identifier in the plist file last time I had to fix Enterprise Distribution, for iOS 8.0, i think. Fixing this was easy, just remove the offending .XXXX -- but then it dosen't work for iOS < 9.0
For the time being, I maintain two plist files for distributing the same ipa file, one for iOS 8.+, and another for iOS 9.+