I am trying to upload an app in the AppStore. The app is divided into two, the app and the cocoapods frameworks. I have created a bundle identifier for the app with a corresponding provisioning profile. The frameworks come with their own bundle identifier and when I tried to replace them with my app bundle identifier the app returned the following error - "An error was encountered while running (Domain = LaunchServicesError, Code = 0)". Therefore I am assuming that the bundle identifier of the cocoapods framework needs to remain as is. Therefore I created a provisioning profile for each of the three bundle identifiers assuming this would resolve the issue.
With this, both the build and archive are successful however when I am uploading the archived app into the app store, xcode is returning the following error - "iTunes Store operation failed. No suitable application records were found. Verify your bundle identifier".
I have tried to reset the bundle id and provision profile from the preference in xcode however issue persist. The build settings - code signing correspond to the respective provisioning profile.
My questions are;
1) Can I have more than one provisioning profile for an app ? (ie. am I doing it right in creating provisioning profile for the cocoapods frameworks).
2) If so, why the provisioning profile is not being recognised (ie. marked as none) once it is archived ?
Related
When I am trying to automatically manage signing for an archive with XCode 12.1. I receive an error message related to my app extension. There were no problems previously (with earlier XCode versions) and I didn't change anything. Error is the following:
Failed to register bundle identifier The app identifier 'bundle id for app extension' cannot be registered to your development team because it is not available. Change your bundle identifier to a unique string to try again.
No profiles for 'bundle id for app extension' were found
Xcode couldn't find any iOS App Store provisioning profiles matching 'bundle id for app extension'.
Bundle id for extension is correct and starts with the bundle id of the app. Something like:
id.bundle.app
id.bundle.app.extension
This is weird as profile is there and is the same as was previously.
.
As I am signing an extension, I am using a wildcard. Profiles are up to date. I also tried to recreate all profiles from scratch, it didn't help.
At the same time automatically manage signing is enabled in XCode and there is no error.
What can be the problem?
UPD.
If I sign manually and while signing select wildcard it works, but it is weird that it doesn't work for automatic signing.
I finally found the problem.
The problem was that I didn't create an identifier for my sticker extension and when I was working with signing I used a wildcard. It was working perfectly until I changed XCode to a newer version.
So, to fix the problem, I created an identifier for stickers extension, using the correct naming
id.bundle.app
id.bundle.app.extension
As the title says, I'm on Xcode 11 and trying to archive to a generic iOS device to add a new version of the app to TestFlight. It builds fine on all simulators. I don't believe I can change the bundle identifier as I'm adding an update to an app that's already on TestFlight. See below for archive errors.
Errors:
"Failed to register bundle identifier. The app identifier "com.'myappnameishere'" cannot be registered to your development team because it is not available. Change your bundle identifier to a unique string and try again."
No profiles for 'com.myappnameishere' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'com.myappnameishere'
What I've done:
A. Gotten an Apple Developer Account and registered my devices
B. Cleared the local Provisional Profiles using this method:
Xcode Error: "The app ID cannot be registered to your development team."
Apologies if this has already been posted but I couldn't find anything. Any help would be appreciated!
If the app is already on TestFlight, you cannot just use any apple developer id, you need to be logged in with the same apple dev account which was used to upload the app to TestFlight before
To archive, and upload an update to the app, you will also need the following installed in your machine
app store provisioning profile for the bundle id
certificate assigned to the app store profile
private key for the certificate's
(or you need to create these artefacts, and install / download them on your machine)
It is not clear if you already meet these criteria.
EDIT: answers to questions in your comment -
You may also face issues running the app on the device if you do not have developer profile for the bundle id, but with free provisioning / wildcard profile, you can circumvent this, and not need access to the specific dev account.
You can create and export archive (generate ipa file) ready for testflight using those artefacts, but to upload the ipa to testflight using any method, you will need credentials for the specific dev account. Alternatively, you can generate the ipa and share it with someone who has access and can upload the ipa.
I have a project that runs fine in the simulator. When I attempt to run on a device I get the following alert:
App installation failed
This application’s bundle identifier does not match its code signing identifier.
I tried the various suggestions from posts uncovered by searching on the above message text. All to no avail.
Question: How do I reveal the values that aren't matching? I know what value I'm using for the Bundle Identifier. How do I reveal the value for the Code Signing Identifier? (I know the Code Signing Identity). Exactly what values is Xcode attempting to match and how are they established?
A bit more info:
I'm using Xcode's Automatically managing signing setting. I've set the Team. The info disclosure button next to Xcode Managed Profile reveals a popover with six entrees, all which appear OK, including the first entry that the App ID matches the Bundle ID.
I've also tried various manual attempts.
UPDATE
I attempted a "start from scratch" process as outlined here:
Phase 1 - Cleanup
Xcode:
Remove all provisioning profiles from device
Clean project
Close project
Quit Xcode
KeyChain:
Remove iPhone Developer certificate
Do not remove any login keys since there are many keys with the same name and I can't distiguish between them
Apple Dev site:
Remove all iOS Certificates
Remove all Development profiles
Do not remove any devices
MBP:
Remove all provisioning profiles from ~/Library/MobileDevice/Provisioning\ Profiles
Remove all project dirs from /Library/Developer/Xcode/DerivedData
Reboot
Phase 2 - Build Project
Xcode:
Launch and open project
General->Signing->Status reports:
Your account already has a signing certificate for this machine but it is not present in your keychain. To create a new one, you must first revoke the existing certificate.
Click Revoke button.
Certificate is auto-generated
Build (success)
Inspect build log to verify the SHA1 used for codesigning steps matches Keychain SHA1 of auto-generated certificate
KeyChain:
Verify that auto-generated certificate exists in KeyChain
MBP:
Verify an auto-generated provisioning profile has been added to ~/Library/MobileDevice/Provisioning\ Profiles
Verify device UUID is include in auto-generated provisioning profile
Apple Dev site:
Verify auto-generated iOS Development certificate exists
The auto-generated provisioning profile is not listed (no profiles exists)
Phase 3 - Run Project
Xcode:
Run in simulator (success)
Run on device
App installation failed
This application’s bundle identifier does not match its code signing identifier.
I think you need to check is your project bundle id's matching in
General Tab
Info.plist(screenshot for inf.plist)
Build settings tab(screenshot for build settings.)
That might be an issue.
Let me know if it's helps.
I had a similar problem when I was trying to package a cross-compiled dylib as a framework. Looking into the device log I was able to get a more detailed description
codeSigningInfoByValidatingResources:performingOnlineAuthorization:ignoringCachedSigningInfo:checkingTrustCacheIfApplicable:error:]: 817: Code signing identifier (DYLIB_NAME) does not match bundle identifier (BUNDLE_IDENTIFIER)
My solution was to adjust the DYLIB_NAME to match the BUNDLE_IDENTIFIER. However, there was a catch: Somehow, XCode seems to be able to extract the original build-name of the dylib. Simply renaming the file thus did not help: I had to adjust the build-target of the dylib to make this solution work.
in iTunes they changed it to have a flag for each role if he will have Access to Certificates, Identifiers & Profiles. and by default its false.
All i had to do is to:
go to iTunesConnect -> Users and Access -> edit my role by checking the box of "Access to Certificates, Identifiers & Profiles"
I've run into an issue signing an update on my PhoneGap generated IPA for distribution.
I have been following the same steps I typically use by clearing the PhoneGap signing, resigning using a distribution profile, attaching Entitlements.plist, then signing using my enterprise certificate but when I use the Application Uploader I get the following error.
ERROR ITMS-9000: "Invalid Code Signing Entitlements. Your application's signature
contains code signing entitlements that are not supported on iOS. Specifically,
value "[TEAMID]. [Bundle Identifier]" for key "application-identifier" in
"Payload/Application.app/Application" is not supported. This value should
be string starting with your TEAMID, followed by a dot '.', followed by
the bundle identifier"
at SoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)
Now the Bundle ID is identical to that of the App's distribution provisioning profile and the one on iTunes Connect. My TEAMID totally matches the one provided in the provisioning profile.
This app is already in the store, I am trying to release an update.
I have installed the new profile to Xcode 4.6.3 and my certificate is also installed there.
I am using Terminal on Mavericks to unsign->resign->zip the IPA for distribution.
I have looked around for a while and have found some other issues and after following their resolutions I am still stuck on this error, which it turn generates a couple other generic errors.
Thanks in advance for any pointers/reference!
I have spent all day fussing about with this issue :(
I've resolved this issue by reissuing my certs/profiles, reinstalling them, clearing my derived data, restarting my computer, and finally completing the resigning process.
When I try to upload my iOS application to the app store using the application loader, I get the following errors:
This means that the provisioning profile is invalid. So, I deleted and re-made the provisioning profile, then archived the application using that profile, and I still got this error... I have uploaded this application to iTunesConnect before, and I got no errors, but now, even though I didn't do anything with my profiles, or change it in the application, I'm getting this error.
I have valid and non-expired certificates, and my bundle ID's are correct. The distribution provisioning profiles I have are:
This is happening for my application named SloganGen.
With the Screenshot that you have attached for errors & provisioning profile, looks like the problem is with the "Case Sensitive" name.
Profile : com.slogangen.slogangen
Error : com.slogangen.SloganGen
From apple documentation:
Typically, the bundle ID in your Xcode project is a string formatted as a reverse-domain name such as com.MyCompany.MyProductName, where you replace MyCompanyName and MyProductName with your domain and product name. However, unlike domain names, app IDs and bundle IDs are case sensitive.
Hope that helps.
Try the following:
Remove armv7s from valid architecture in build settings
Make sure you have a certificate for app store.
Check the bundle identifier to make sure that it is same as your certificates.