As described in this SO entry, I am getting errors in iOS app Application Uploader.
These are the values I have:
in KeyChain I have this certificate:
iPhone Distribution: ExampleCompany (DistCertificateID)
In my developer.apple.com account I have defined app:
Name: LongReadableName
Prefix: DistCertificateID
ID: com.example.*
Name: Xcode iOS Wildcard App ID
Prefix: DistCertificateID
ID: *
These are the errors I am getting:
This bundle is invalid. The application-identifier entitlement is not
formatted correctly; it should contain your 10-character App ID Seed,
followed by a dot, followed by your bundle identifier:
0000000000.appname
and
The Bundle ID DistCertificateID.appname defined in your Xcode Project
does not match the Bundle ID that you entered for this app in iTunes
Connect appname.
Above has let me to conclude I possible submitted the app incorrectly (?) to iTunesConnect since that is the only conclusion that makes any sense to me.
(For reference, and if I understood everything correctly, I believe both the specific and wildcard app ID is appropriate for me since I do not need to use inapp-purchases or anything like that.)
When submiting an app in iTunesConnect I can choose between
Xcode iOS Wildcard App ID - *****
LongReadableName - com.example.*
I am completely lost on how I can ever choose a BundleID / BundleID Suffix that obeys both what is written in iTunesConnect (?) and the errors I am getting in Application Uploader right now. Could anyone point me to values I could use that would not collide with Application Uploader requirements?
...
Newest update #1
I decided to drop using wildcard app IDs since I can see that has caused other people problems. Hence I chose the other option in iTunesConnect resulting it in showing me BundleID as being com.example.appname. I then made sure 1) my provisioning for distribution used DistCertificateID.com.example.* 2) to set CFBunldeIdentifier (in Delphi) as same shown in iTunesConnect. I then built and deployed followed by submitting it to Application Loader. That resulted in error message:
The Bundle ID com.example.appname defined in your Xcode Project
does not match the Bundle ID that you entered for this app in iTunes
Connect com.example.appname.
As you can see, the bundle ID is now the same, but still it complains. I do not understand why :(
Newest update #2
I actually made a small typo error last night when I tried above. Guess I was too tired. Above solution works! (I will make it an answer.)
Ditching the wildcard app ID worked for me. Hence I chose the other option in iTunesConnect resulting it in showing me BundleID as being com.example.appname. I then made sure 1) my provisioning for distribution used DistCertificateID.com.example.* 2) to set CFBunldeIdentifier (in Delphi) as same shown in iTunesConnect. I then built and deployed followed by submitting it to Application Loader.
Related
I have cloned a project and tried to run my app on a device(iPhone 7), but it showing the build failure with the below-mentioned error.
Note: If I create a new project in Xcode then, I can able to run the app on my device.
How can I solve this?
Error:
Failed to create provisioning profile.
The app ID "org.reactjs.native.example.app" cannot be registered to your development team. Change your bundle identifier to a unique string to try again.
No profiles for 'org.reactjs.native.example.app' were found
Xcode couldn't find any iOS App Development provisioning profiles matching 'org.reactjs.native.example.app'.
Assuming you have a valid iTunes Connect developer account:
App IDs are unique per all App Store accounts. Therefore if someone had registered an appId of org.reactjs.native.example.app as it is in your case, you cannot use it. That was clearly used by react.js guys and is now part of their profile(s). You need to change the appId of the cloned project to something unique. Most common notation used is com.my_organization_name.my_project_name. You can also go for prefixing the original id with lets say com.my_organization.tests.org.reactjs.native.example.app or something similar
I'm having a problem whereas I cannot submit my archive for beta testing due to this problem (keep in mind I've already got a build out for testing, uploaded a while ago):
Xcode attempted to locate or generate matching signing assets and failed to do so because of the following issues.
An App ID with identifier '' is not available. Please enter a different string
According to this question, it seems that I should change my bundle ID from the format I am currently using: com.my.app, to the preferred format: com.my.app.XXX.
However, how can this be achieved? I'm using Firebase version 3 from Google as my backend provider, and I cannot seem to change the Bundle ID there, even if I would take the big step to create a whole new app in iTunes Connect due to not being able to changing the bundle ID.
My limitations (it seems):
Can't change bundle ID at Firebase
Can't change bundle ID with project in iTunes Connect.
Can't delete app identifier in member center because it's being used by the app listing in iTunes Connect.
Can't delete app from iTunes Connect.
Hence I'm a little stuck here; what's the best way to dig out of this?
On my app developer site I created a an app ID of org.myorg.54Miles My apps name is 54Miles.
In XCode my product name is set to 54Miles under my Build Settings - but it makes my bundle identifier under the general "org.sd54.-4Miles"
Any idea why this is? It's causing me to not be able to archive the app and get it distributed because the AppID doesn't match the bundle ID in xcode.
I want it to read: org.sd54.54Miles - but currently I cannot get it to stop reading org.sd54.-4Miles
Cannot figure it out!
I ended up just leaving the bundle ID as it was since apparently Apple has a problem leading with digits in the bundle identifier.
So I just created a new App ID in the developer site to match it. I have since been able to deploy it without issue.
I can not pick a correct CFBundleIdentifier value it seems.
...
in KeyChain I have this certificate:
iPhone Distribution: ExampleCompany (DistCertificateID)
In my developer.apple.com account I have defined app:
Name: LongReadableName
Prefix: DistCertificateID
ID: com.example.*
Name: Xcode iOS Wildcard App ID
Prefix: DistCertificateID
ID: *
In iTunesConnect I have name SkuID + BundleID appname
...
I have then tried to enter and deploy with following values with different error messages:
appname
This bundle is invalid. The application-identifier entitlement is not
formatted correctly; it should contain your 10-character App ID Seed,
followed by a dot, followed by your bundle identifier:
0000000000.appname
DistCertificateID.appname
The Bundle ID DistCertificateID.appname defined in your Xcode
Project does not match the Bundle ID that you entered for this app in
iTunes Connect appname.
DistCertificateID.com.example
The Bundle ID DistCertificateID.com.example defined in your Xcode
Project does not match the Bundle ID that you entered for this app in
iTunes Connect appname.
DistCertificateID.com.example.*
The Bundle ID DistCertificateID.com.example.* defined in your Xcode
Project does not match the Bundle ID that you entered for this app in
iTunes Connect appname.
DistCertificateID.com.example.appname
The Bundle ID DistCertificateID.com.example.appname defined in your Xcode
Project does not match the Bundle ID that you entered for this app in
iTunes Connect appname.
com.example.appname
The Bundle ID com.example.appname defined in your Xcode
Project does not match the Bundle ID that you entered for this app in
iTunes Connect appname.
I think I have tried everything I could think of...
I speculate if the issue could be resolved by a different iTunesConnect configuration/upload although I have now idea at present how to create one that would solve the problems listed here. But just in case, I have create a specific SO for BundleID/iTunesConnect: iOS app Bundle ID errors and iTunesConnect
Newest update #1
I decided to drop using wildcard app IDs since I can see that has caused other people problems. Hence I chose the other option in iTunesConnect resulting it in showing me BundleID as being com.example.appname. I then made sure 1) my provisioning for distribution used DistCertificateID.com.example.* 2) to set CFBunldeIdentifier (in Delphi) as same shown in iTunesConnect. I then built and deployed followed by submitting it to Application Loader. That resulted in error message:
The Bundle ID com.example.appname defined in your Xcode Project
does not match the Bundle ID that you entered for this app in iTunes
Connect com.example.appname.
As you can see, the bundle ID is now the same, but still it complains. I do not understand why :(
Newest update #2
I actually made a small typo error last night when I tried above. Guess I was too tired. Above solution works! (I will make it an answer.)
Ditching the wildcard app ID worked for me. Hence I chose the other option in iTunesConnect resulting it in showing me BundleID as being com.example.appname. I then made sure 1) my provisioning for distribution used DistCertificateID.com.example.* 2) to set CFBunldeIdentifier (in Delphi) as same shown in iTunesConnect. I then built and deployed followed by submitting it to Application Loader.
I was struggling with the same problem, I found this link http://embarcadero.newsgroups.archived.at/public.delphi.deployment/201308/1308131098.html
I just hadn't set the CFBundleIdentifier in Debug although I was deploying for Release. I hope this will help you to solve your issue.
While upgrading an existing app, I'm getting the notorious:
"The binary you uploaded was invalid. The signature was invalid, or it
was not signed with an Apple submission certificate."
I believe it is due to the fact that I am using the wrong App ID. I forgot the one I used in the original app. Is there a way to determine the original App ID? I now using xcode 4 the original app was done back in iOS 3.0 days.
If the app is available on from the store or if you still have the bundle you submitted open it up and find the binary. On the binary run
strings - appBinary | grep -A 1 application-identifier
this will show you the appID that was used.
Incidentally this didn't completely solve my problem. However closely examining the strings on the binary I was trying to submit revealed the app was being signed by my developer cert and not my distribution cert (despite the xcode settings) there fore I changed all builds to use my distribution cert's and it then worked.