I recently updated to Xcode 13.2.1, I want to release an app to the app store but when I do Product => Archive, it shows Distribute Content instead of Distribute App. I checked my build settings, it has skip install to No. Any idea how to fix it.
Here is the screenshot of the build settings.
Related
I am working on a Flutter application. I am able to build the release version of my app without any issue, but for iOS when I use DIAWI to give a link to any other user with Enterprise distribution the installation will not complete. We have an unfocused icon on the device and clicking it will do nothing.
Thanks for the help Krish. I was able resolve the issue. the Runner.app generated through flutter build ios cant be used for this purpose.You have to use Product > Archive which will use the Scheme select in Xcode. So before using this you have change the scheme or generate a new scheme with release mode selected. This will allow the system to use Enterprise Distribution Profile and give you .ipa file generated automatically at iso>Runner>"selected folder" Using this .ipa there was no issue installing the app on any IOS device.
I have been uploading versions of my app for a while, and suddenly, after an update of mac os, I cannot upload my app anymore, I've upgraded my mac os version, xcode and still nothing....
UPDATE
Its important to note that this is a react native application that i am generating using expo by running expo build ios
these are the errors that i am getting...
ERROR ITMS-90163: "Invalid Code Signing Entitlements. The entitlements
in your app bundle signature do not match the ones that are contained
in the provisioning profile. The bundle contains a key that is not
included in the provisioning profile:
'com.apple.developer.icloud-services' in
'Payload/ExpoKitApp.app/ExpoKitApp'."
WARNING ITMS-90725: "SDK Version Issue. This app was built with the
iOS 11.4 SDK. Starting March 2019, all iOS apps submitted to the App
Store must be built with the iOS 12.1 SDK or later, included in Xcode
10.1 or later."
Does anyone have an idea?
The first part, ITMS-90163, is an error -- basically stating that your app is trying to use iCloud but the provisioning profile (that you set up at developer.apple.com) doesn't have iCloud enabled. This is what's blocking your upload.
Since you say this just started happening, probably this means the iCloud switch in Xcode got flipped on accidentally (if your app is not a actually using iCloud).
In Xcode 10.1, be sure your project is selected in the upper left and your target is selected, then click on the Capabilities tab and scroll down until you see iCloud, and click it OFF. Important: This is only a reasonable choice if your app does not use iCloud.
If your app does use iCloud, you instead need to generate a new provisioning profile. You can do this manually by going to developer.apple.com, and click on Account in the upper right. Click "Certificates, IDs, & Profiles", and follow Apple's instructions. However, you can have Xcode managing provisioning profiles for you automatically, by clicking on the General tab and then checking the box "Automatically Manage Signing".
The second part, ITMS-90725, is just a warning, so it's not blocking you from uploading (though it will be a problem in March). To resolve this, first, be sure you are on Xcode 10.1 or later. (While in Xcode, go up to the menu bar and click Xcode -> About Xcode to check.). It's possible that you could be using Xcode 10.1 and still not using the latest SDK for some reason. Under Build Settings, check Base SDK. It should just say "iOS".
Previously with Xcode 7.3.1 I was able to build directly over my app store app on my iPad and test the upgrade scenario, which worked perfectly fine. This week I upgraded to Xcode 8 and when I try the exact same approach, I keep getting this upgrade error
"This application's application-identifier entitlement does not match that of the installed application. These values must match for an upgrade to be allowed."
I tried multiple solutions posted on this thread and none of them worked. I also don't have a watch app. Just a simple iOS app target.
App installation failed due to application-identifier entitlement
I deleted my certs and provisioning profiles and recreated them and still the same problem. I then went and downloaded Xcode 7.3.1 and tried it again with the exact same problem.
Now I am stuck without being able to fully test my upgrade scenario.
PLEASE HELP !!
I had the same issue while trying to upgrade application.
And here what I've found:
I checked application-identifier entitlements of old app and new app. You can do that by running codesign -d --entitlements :- path/to/AppName.app/AppName or open file "archived-expanded-entitlements.xcent" at path "AppName.app/AppName".
Application-identifier of old app was "1234XXX5X6.com.mycompany.myapp" but in new app it was "1234XXX5X6.com.mycompany.myapp.develop".
Usually I set "Bundle Identifier" directly in Info.plist.
But I didn't know that there is also a "Product Bundle Identifier" property in project Build Settings.
The previous version of app was built with Xcode 7.3.1 and it had following settings:
Info.plist: com.mycompany.myapp
Build Settings: com.mycompany.myapp.develop
application-identifier: 1234XXX5X6.com.mycompany.myapp
The new version was built with Xcode 8.2.1 and it had following settings:
Info.plist: com.mycompany.myapp
Build Settings: com.mycompany.myapp.develop
application-identifier: 1234XXX5X6.com.mycompany.myapp.develop
Seems like new Xcode have different source for application-identifier.
So I just corrected "Product Bundle Identifier" and my problem was solved.
Remove the existing application from the device and Run again.
To fix this just enable "Automatic manage signing" from general tab of project settings.
I had also problem for running app on my device directly from xcode 8. Deleting and generation profile and certificate did not worked for me. But enabling "Automatic manage signing" worked for me.
Hope this helps!
Check this question of mine:
Xcode 8 shows error that provisioning profile doesn't include signing certificate
Here is one solution if you want to upgrade over your existing App Store app without deleting it but your application-identifier entitlement does not match. Upload an archive of your new build to the App Store and then use TestFlight to download it to your device. This is not as quick as building to the device, but it will overwrite your old app with your new build while keeping your old data in place. For (relatively) quicker turn-around testing of your upgrade process once you have a new build available on TestFlight:
Delete your app off of your device (assuming it was a recent build)
Download your app store build and generate some data
Download your TestFlight build, but don't run it
Build your newest build directly to the device
The TestFlight build overwrites the entitlement without deleting the old data, so Xcode happily will install your new build over the TestFlight build, but you are still testing your upgrade process as if you were building directly on top of the App Store version of your app.
I got this from an .ipa generated as a Jenkins artefact. The problem for me was that Jenkins was using a different provisioning profile.
I manually set Jenkins to use the same profile as the updated version that I was trying to install, and it started working.
Select the App Target and click on General, if you select or ticked checkbox automatically manage signing.
Untick this automatically manage signing and select appropriate signing provisioning profile and #Build and run again.
See the below photo.
Solved!! Short answer - delete old app from your iPhone
I went to my iPhone storage and used the search bar to find the offending app(because it wasn’t showing on the app list) and found an old version hidden, deleted it and now it works.
What worked for me was to go (within Xcode) to Window > Devices and Simulators, then select my iOS device and delete the app there. This is detailed in this Medium article.
My project was initially build with the early version of Xcode.
Even with Xcode 6 I was able to export the app (Ad Hoc, ipa file).
After that we started to use continuous integration & upload of builds to iTunes.
Also, I have deleted my working copy.
Recently, I have to make fixes in the project.I checked out the source code, updated my Xcode to the latest version - Xcode 7, updated the project.
But now when I am archiving the app, it goes under unknown app in Organizer, I can't create ipa ( Validate button is not active).
For some reasons the app, in the Organizer doesn't have a valid identifier
I tried to use a new
PRODUCT_BUNDLE_IDENTIFIER
and directly to set correct bundle ID, but I still have 2 items, instead of one app.
In build setting under build option Disable bitcode.
In build setting under deployment set false to skip install.
I created a brand new project in the latest version of Xcode and have been building and running it fine in both Simulator and on Devices plugged into my Mac.
Recently I needed to archive & export an .ipa for someone else to install (still using my developer profile and one of my developer devices), but was unable to do so because when I click on the "Distribute" button on the "Archive" tab of the Organizer window, the top choice is "Submit to Mac App store" instead of the iOS store.
Nothing in my project settings indicates Mac OS instead of iOS, so I'm baffled as to why this is happening. I've tried duplicating the Target/Product, but the results are the same. I've also had someone else build the project on a different Mac and they experience the same problem.
Is this a known bug in Xcode and is there some way to get past it?
Thanks,
BT
Check if you have accidentally made your Info.plist part of your target. It shouldn't be. Uncheck it in the Target Membership pane or remove it from the Copy Bundle Resources build phase.
(Found answer via this question: My iPhone app is being archived as "Mac App Archive" and not "iOS app archive".)