I removed all my app IDs and provisioning profiles from Apple's Developer site. Then I created a new Xcode 7.3.1 project, and clicked "Fix Issue" next to the "no matching provisioning profiles found" message.
The app ID it created is called "XC Wildcard", but it's not a wildcard ID; it's set to the bundle identifier of the Xcode project. And the development profile it created is assigned to that app ID.
If I change the bundle identifier and click "Fix Issue", it creates a second app ID called "XC Wildcard", with the new bundle identifier, and another development profile for it.
This works, but seems wrong. Shouldn't it be creating an actual wildcard app ID, unless I turn on specific capabilities like Push Notifications?
Xcode create "XC Wildcard" to be used for debugging so it matches all app id's
change deployment configuration from debug to release and Xcode will create a provisioning profile with your app id.
Related
(new to xcode. need to change working project) I want to rename my xcode project, followed the instructions in https://help.apple.com/xcode/mac/11.4/#/dev3db3afe4f
but if I change the Identity|BundleIdentifier, The Signing section warns that "The provisioning profile does not match the ... bundle ID"
Where do I add new BundleIdentifier and how do I use it?
(my xcode version is 10.1)
From If the provisioning profile App ID doesn't match the bundle ID:
If there is a conflict between the App ID in the provisioning profile
and the bundle ID in your project, you receive error messages similar
to the following:
Code Sign error: Provisioning profile 'MyApp Profile' specifies the
Application Identifier 'com.mycompany.MyApp.*' which doesn't match the
current setting 'com.mycompany.MyApp' In the project editor, choose
the target and click General.
In the Identity section, set the bundle ID to match the App ID.
In the Signing section, verify that the team, provisioning profile,
and signing certificate settings are correct.
Next to the provisioning profile, click the information icon.
In the dialog that appears, verify that the provisioning profile
contains the correct App ID.
In addition, you can view the App ID and provisioning profile details
in your developer account.
The Xcode default is to generate a profile per app (ie. com.mypackage.myapp)
You can generate provisioning profiles for a package (ie com.mypackage.*), but this may require a paid developer account and may also require selecting it in the app settings.
I have created my first ever iOS app. I am basically an android developer. and I know how to do things in android like the one I am trying to do in iOS
Right now I have made one app and I want to change a little and deliver it to my another client. For this I have to change only 4 things
URL
APP NAME
BUNDLE ID
SOME PASSWORD STRINGS
now as I have created a new target by following this tutorial, I have seen the red mark on provisioning profile. It says "NAME_MY_PROVISIONING PROFILE" has app ID com.mypreviousclient.bundle.identifier which does not match the bundle id of my new client
It clearly tells that the bundle id I just created is not inside my provisioning profile.
But I really do not know what to do now? What should I do now?
For changing bundle id in xcode for new app. You have to also create that bundle id in apple developer console. Here are the steps.
create bundle id in apple developer console.
Now you can create application in itune.
create certificates.
create provisioning profiles.
set them into xcode and run.
Happy coding.
I would like to export a new build of my Xcode app to iTunes Connect, but I always get the following error:
Failed to create provisioning profile.
The app ID "[myappid].OneSignalNotificationServiceExtension" cannot be registered to
your development team. Change your bundle identifier to a unique string
to try again.
Provisioning profile failed qualification
Profile doesn't include the selected signing certificate.
I tried the following:
Cleaning the build
Restart xCode
Creating new profiles (distribution/development)
Removing .OneSignalNotificationServiceExtension (gives another error)
I don't want to change the app id since I want to continue on the same app (for my testers).
I had to change my password of my Apple ID due to security issues, but I changed it everywhere they asked for it.
Does anybody know how to fix this?
As oneSignalNotification is an Extension, the App Id of the extension should have main App id as prefix. ie, If your main App id is : com.xx.xxapp, then the app id for your extension should be com.xx.xxapp.someExtention. Also you need to have separate provisioning profile for main App and extension target.
I am trying to archieve my app for submission however I am running into issues with code signing.
Basically I have a Today Widget extension for my app. I am unsure about what I should be setting the provisioning profile as. I assumed that I would just use the same profile that I have used for my app, however I get this error:
The provisioning profile specified in your build settings (“AppName”) has an AppID of “BundleID” which does not match your bundle identifier “BundleID2”. Xcode can resolve this issue by downloading a new provisioning profile from the Member Center.
I can of course click 'Fix Issue', but does this actually solve the problem? It just changes my distribution settings to 'iOS Developer' and providing profile to 'Automatic'.
I was struggling with the same problem, and resolved it this way:
You need one App ID configured to the provisioning portal (I assume you have your com.apple.yourappname there)
You need to then configure the second App ID for the Today Widget (which should be com.apple.yourappname.something, where something is the name for your widget, like Today)
Then you need to create two App Store Distribution provisioning profiles:
One for the main App
Second one for the widget
Then assign the correct provisioning profiles for each target to the project settings and set to build for Distribution.
My problem was because of i added "arm" in the Excluded architecture section. I revert it and the problem goes away. It is weird.
Try to create a new App Id for your App extension in Certificates, Identifiers & Profiles (https://developer.apple.com/account). Then create a Provisioing profile for the newly created App id.
If the bundle id for your App is com.apple.appname you create an app extensions with the bundle id com.apple.appname.appextensionname. The same id is then used in Xcode for the widget.
I am having a fairly annoying problem with my provisioning profile, The app I am working on started off with a name lets call it awesomeapp, so in the provisioning portal at apple I have a ios app identifier with the id "com.mydomain.awesomeapp".
but my apps bundle identifier is called AwesomeApp, and it turns out that the provisioning profile that is used the app identifier I have created is case sensitive. as I get this error
The provisioning profile specified in your build settings (“iOS Team
Provisioning Profile: com.mydomain.awsmomeapp”) has an AppID of
“com.mydomain.awsomeapp” which does not match your bundle identifier
“com.mydomain.AwsomeApp”. Xcode can resolve this issue by
downloading a new provisioning profile from the Member Center.
If I click okay it goes ahead and removes the provisioning profile and uses a wildcard one i set up.. However I dont want to use the wild card provisioning profile.
So, I went back to create a new app identifier and I entered the id to be com.mydomain.AwsomeApp however this prompts an error
An App ID with Identifier 'com.mydomain.AwesomeApp' is not available.
Please enter a different string.
which suggests to me that when you create an app ID it is case Insensitive.. how do I get around this problem?
I think there is no other solution than deleting the app id and recreating it with the proper identifier.
Originally Apple had no options to edit, rename or delete an App-Id at all.
However at some point in 2013 they've added an delete button available in your members
provisioning center -> App-Id -> Edit one specific -> delete
Some users have reported, that the delete button has been disabled again but for me, it is still working: