ERROR ITMS-90283: Invalid Provisioning Profile error for macCatalyst with Universal Purchase - swift

I am trying to submit a new app developed by macCatalyst and by using the same universal purchase option in the appstoreconnect.
I enabled the new option use IOS Bundle identifier in XCode 11.4
So, my IOS and Mac version of apps use the same bundle identifier
I enabled the mac platform in appstore connect
I can build, run and archive my project successfully but when I try to upload or validate it I get the following error at the end of the upload:
ERROR ITMS-90283: "Invalid Provisioning Profile. The provisioning profile included in the bundle com.XXX.XXX [com.XXX.XXX.pkg/Payload/XXX.app] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer Portal."
I get this error only when I upload macCatalyst version of my app. There's no problem about uplading and/or validating the IOS version.
I've already tried, deleting and redownloading of all profiles, refreshing automatic signing, refreshing entitlement file but none of them worked.
Thanks in advance.

Double check that the items enabled under "Signing and Capabilities" in Xcode is the same as in Certificates, Identifiers & Profiles
Xcode 11.4.1 added some extra when I added macOS as target, after removing the ones the app didn't use the ERROR ITMS-90283 error went away.

Related

Unable to install ipa file using testflight or diwali in xcode 4.5.1 and ios 5.1

Hy.
I have developed an IOS app in version 5.1 and xcode 4.5.1. After completing the app when I try to run it in the device using ad hoc distribution, the app is unable to install on device.
It shows popup "Unable to download application. ' could not be downloaded at this time'".
I have added distribution and developer certificate and it does not give any such alert when installing directly from the xcode but the problem occurs only when installing app from the testflight.
Could someone tell me where I m making a mistake.
You must Archive the application using your AdHoc Distribution Cert, then from the Archives tab of the Organizer click Distribute and again select your AdHoc cert. The .ipa that this produces is what must be uploaded to TestFlight and you must authorize your device through TestFlight. Here's some tutorials that will help:
Create and Upload an IPA to TestFlight
Setting up Permissions for Distribution on TestFlight
If your IPA and permissions are all correct then according to this article the error could be related to one of many other factors:
Device storage is full
The provisioning profile is a developer provisioning profile
The ad hoc distribution provisioning profile is corrupted and the device is having an issue with it.
The device was restored from a backup and is causing a conflict for over-the-air distribution
There was a network timeout
See the referenced article for details on how to get a console log on the device. If you still are unable to resolve the issue then edit your question and include the relevant parts of the console log from the device.
Go to Product -> Edit Schema -> Build Configuration
Change Debug to Release and try it.

XCode 4 valid signing identity not found

I have installed XCode 4 for iOS 5 and when I open the organizer I see the error for my developer provisioning profile: "valid signing identity not found"
But I also have the XCode 3 in the same machine and when I open the Xcode 3 organizer, I do not see any warning.
Do I need to do anything extra to make provisioning profile valid in XCode 4?
This happened to me, too. It works pretty fine on my own Mac Mini, while I got the error on the other Mac Mini. I exported the profiles and imported them in the other Mac, and then updated it in organizer, and it worked!
I had the same problem but it turns out that the problem wasn't the signing identity. The provisioning profile I was trying to use didn't actually cover the new device. Once I updated the provisioning profile and then downloaded and installed the updated profile all the errors disappeared.

Unable to build Apple's example project core data book

I opened the core data book example directly from Xcode's documentation window. The project won't build. It says the Iphone OS 4.0 is missing. Since I used Xcode 3 with SDK of iOS 4.2, I changed the build SDK to iOS4.2 (latest), but it then says:
Code Sign error: a valid provisioning profile matching the application's Identifier 'com.yourcompany.CoreDataBooks' could not be found
If I change the code signing identity to "don't code sign", it says:
CodeSign error: code signing is required for product type 'Application' in SDK 'iOS 4.2'
I am not sure whether the $99 developer fee is required to run the example. Would that be the problem?
Thanks in advance.
Leo,
Code signing error will occur only when you try to make device build and either dont have provisioning profile or you are giving wrong information.
Following error occurs when you provide wrong identifier, If you have provisioning profile (check in organizer of XCode, under windows menu)then you should provide its app identifier starting from com. and so on.
Code Sign error: a valid provisioning profile matching the application's Identifier 'com.yourcompany.CoreDataBooks' could not be found
The second error you are getting is because you are trying to build, device build without having any profile. CodeSign error: code signing is required for product type 'Application' in SDK 'iOS 4.2'
If you want to make that application's device build you should have right provisioning profile, else you would not be able to make it.
If you only wants to run it on simulator then you can do it easily.
On the LeftMost corner top you will fine a dropdown menu. In that you will need to select Simulator and Debug. And after that clean all targets and "Build and Run" application.
Thanks

provision profile

I have an application, it worked on the iPhone OS 3.0 with SDK 3.0.
with iPhone OS 3.0.1 I did the update and it seems o.k.:
ln -s /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0\ (7A341) /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0.1
But when I want to install my application on the device I get:
"Code Sign error: Provisioning profile '...' can't be found"
In XCode/Window/Organizer: "A valid signing identity matching this profile could not be found in your keychain"
Should I change the provision profile somehow? It was created for iPhone OS 3.0.
Should I change smth. in my keychain?
Thank you so much for your help!
Alexandra
you can try to edit the project file in project.xcodeproj/project.pbxproj find all CODE_SIGN_IDENTITY and remove them, then re-open the project and re-set the mobile provisioning.
Your signing identity/Provisioning file may have gotten deleted or expired. Check your provisioning profile in the Organizer window of Xcode to see what its status is.
1) I have deleted and added the profile in Organizer.
2) In the "build" of the current Project "Code Signing Identity" for Developer with the profile number "C44211F-..." can be choosed. So I choose it.
3) By starting the application as "Device-3.0-Release" - error: Provisioning profile "C44211F-...." can't be found

provision file error in iPhone OS 2.2

I created an AppID "MyApp", DeviceID "MyDevice" in Program Portal and I downloaded the provision file and drag it to Organizer, downloaded the .cer file and install it on Mac.
All these works fine, but when I build my app, an error pops up saying "CodeSign error: a valid provisioning profile is required for product type 'Application' in SDK 'Device-iPhone OS 2.2'".
I tried to find PROVISIONING_PROFILE in project.pbxproj in myApp.xcodeproj, but it returns "Not Found". What might be the problem? Do I need to modifiy the info.plist and what should I modify?
The provisioning process for developing iPhone apps can be very confusing, and your error could be due to any of a number of issues. Here is a very thorough walkthrough:
http://www.24100.net/2009/02/iphone-sdk-mobile-provisioning-0xe800003a-0xe8000001/
I would suggest totally scrapping whatever provisioning profiles you have, erase them from XCode, and start over using this tutorial. That seems to work the best in most of my cases.