I have purchased a developer account from Apple. By taking development provisions, I have tested example app in device. Then I have downloaded cocos2d-iphone-1.0.1 and set it up. Then I created a project called FirstGame. When I compile sample cocos2D project on device, it gives this error:
Code Sign error: A valid provisioning profile matching the application's Identifier 'com.yourcompany.FirstGame' could not be found
In the build settings of project, the development profiles are not enabled. I am using Xcode 4.6.
Edit: I've found solution applying this solution.:
This has nothing to do with cocos2d. Just edit the bundle identifier of the project, and make sure you have correct provisioning profiles.
It should be com.ahmetatalay.FirstGame, not com.yourcompany.FirstGame which is default in cocos2d template.
Change it under Project Settings section of Xcode, to code sign it with your wildcard profile or the profile you created specifically for it.
See Apple's documentation for details:
http://developer.apple.com/library/ios/#documentation/ToolsLanguages/Conceptual/DevPortalGuide/CreatingandDownloadingDevelopmentProvisioningProfiles/CreatingandDownloadingDevelopmentProvisioningProfiles.html
Related
I have downloaded a Xamarin solution zip from
https://github.com/alexrainman/CarouselView
I tried running this solution on my MAC PC and deploying it to my Ipad. I encountered this error saying "could not find any available provisioining profiles for iOS" .
In order to resolve this I followed this link
https://learn.microsoft.com/en-us/xamarin/ios/get-started/installation/device-provisioning/free-provisioning
to create a free provisioning profile.
I have checked the settings of the iOS Bundle Signing settings of the solution i wish to run (carousel view) but although I do see that my profile is available for selecting and although I selected my profile, I still encountered the same error saying that they could not find any available provisioning profiles for IOS.
Anyone able to help me out with this?
You're on the right track. A provisioning profile can only be used for a specific bundle identifier.
The one in the Xamarin.Forms CarouselView demo is set to com.slbdev.demo.ios. Which (probably) differs from the one set in your provisioning profile.
In order to fix this open the Info.plist file and set the Bundle Identifier field to the one you used while generating your provisioning profile.
See bullet 5 in the post you linked:
Under the General > Identity section, make sure that the Bundle
Identifier matches exactly the Bundle Identifier of your Xamarin.iOS
app and ensure the deployment target matches or is lower than your
connected iOS device. This step is extremely important, as Xcode will
only create a provisioning profile with an explicit App ID:
My iOS project has an embedded framework. I am trying to build it on Bitrise, but it fails because it tries to code sign this framework with the same provisioning profile as the actual project.
This is the error it produces (split onto separate lines for readability):
❌ Code Sign error: Provisioning profile does not match bundle identifier:
The provisioning profile specified in your build settings
(“Profile Name”) has an AppID of “com.example.mainidentity”
which does not match your bundle identifier
“com.example.frameworkidentity”.
I've tried it with Force code signing with Provisioning Profile, with Force code signing with Identity, without either and various other permutations. Changing the Code Signing Identity from iOS Developer to Don't Code Sign in the framework's Build Settings. Etc.
I've left Code Sign on Copy on in the Build Phases of the main project.
Nothing seems to work.
It's my understanding that an embedded framework should just sign with the iOS Developer identity as you archive a project.
-
The project archive's fine on my local machine.
Environment & info:
Using a workspace, the embedded framework does have it's own pods, as does the main project.
I'm using Xcode 7.3 on OS X 10.11.6
The provisioning profile is an iOS UniversalDistribution type one.
The Bitrise workflow is using:
Certificate and profile installer - 1.7.0
Xcode: Create Archive - 1.9.2
If any other info is needed or anything needs clarifying let me know!
Thank you!!
You should not use "Force code signing with Provisioning Profile" in this case, as that (this is simply an option passed to Xcode) will force that specific profile to be used for every part of the project!
You can find more information here: https://bitrise-io.github.io/devcenter/ios/code-signing/#full-manual-full-control
TL;DR; don't use a full Provisioning Profile ID, rather use "Force Identity" if you really have to (and maybe just a category for Force Prov Profile, like "iPhone Distribution"), Xcode will figure out which profile to use, based on the Identity and bundle IDs etc.
That said, since Xcode 7 the recommended way is to use "Export Options Plist", and in Xcode 8 if you opt-in for automatic code signing that's your only option. In short, the recommended way is to do an initial signing with development code signing, and then specify the "export method" for Xcode (in case of Bitrise this is an option of the Xcode Archive step). The only this to note here is that you need both development and distribution certs & profiles to be available. But once you do, selecting the right one for distribution is as easy as setting the "export method" option (Xcode Archive step) to the type you want to use (e.g. ad-hoc or app-store).
More info: https://bitrise-io.github.io/devcenter/ios/code-signing/#using-export-options-available-for-xcode-7-and-xcode-archive-step-v191
P.S.: if you'd want to migrate to the new code signing options you should reset the inputs you previously specified - probably the fastest way, if you use the Web UI, is to remove the Xcode Archive step, and then add a new one to the same spot.
This question already has answers here:
The executable gets signed with invalid entitlements in Xcode
(40 answers)
Closed 2 years ago.
I would install an application in my mobile phone by using Xcode but it was not installed with following an error message.
Error Message
"The executable was signed with invalid entitlements.
The entitlements specified in your application’s Code Signing Entitlements file do not match those specified in your provisioning profile. (0xE8008016)"
Matters of Inquiry
Why does the error message occur while I install the application?
Would you mind if you can give me the solution of this problem?
Check if you are using Entitlement file in Build Setting > Code Signing Section.
If yes, try deleting that file name.
You are using Entitlement file
The entitlements file defines certain capabilities of your app. Usually, the file is automatically generated by Xcode when you enable a capability for your app. You only need the file if you enable certain capabilities, e.g. Healthkit integration. If you'd like to use these features, you have to add it. Otherwise, Apple will reject your app.
To fix this
Go to the build settings of your target.
Make sure that you have "All" selected instead of "Basic"
Type "entitlements" into the search box
The result is the build setting where you can specify where your
entitlements file is located
Remove them
You are using the wrong Provisioning Profile
A provisioning profile is a collection of digital entities that uniquely ties developers and devices to an authorized iPhone Development Team and enables a device to be used for testing. A Development Provisioning Profile must be installed on each device on which you wish to run your application code.
Go to Build Settings > Code Signing > Provisioning Profile
Select a development profile under Team
Please ensure that the Team in the project, target and tests are the same.
Bundle Identifier and App ID do not match
Go to the build settings of your target
Select Packaging and change your App ID to match the Bundle ID
Clear cache in Xcode
Command-Option-Shift-K to clean out the build folder. Even better, quit Xcode and clean out ~/Library/Developer/Xcode/DerivedData manually.
You are using wrong provisioning profile to build your app on devices make sure you are using right type of profile. I was using App Store Deployment profile to build on devices. Use ad-hoc profiles or development profiles to build on your devices.
You are using the wrong Provisioning Profile i.e. Distribution for development. Go to Build Settings > Code Signing > Provisioning Profile and select a development profile.
Check the if your "Code Signing" configurations are same on "PROJECT>Build Settings" and "TARGETS>Build Settings".
Personnally, I use for both:
- "Code Signing identity": iOS Developer
- "Provisioning Profile" : Automatic
Check your "Team" parameter at your targets. It should be the same for your project and tests.
For me none of the above answers worked. I tried to remove every code signing certificate from Keychain and build the app. When I resolved all code signing related errors for my target I still had some of them in Tests target. It has been set by someone else from my team before. I just switched to iOS Developer, and the invalid entitlement error went away.
I was getting this problem after moving app from one account to another. I tried all the solutions given by others, those might be correct in other cases. But I fixed the problem by going File -> Workspace Settings -> Build System and choosing "Legacy Build System". I'm using XCode 10.3.
I faced this problem and my problem was My Bundle Identifier and AppID was not matched. Please change your Bundle Identifier in Build Settings->Packaging like your AppID.
Just goto Apple developer portal from where you have downloaded provisioning profile.
Select your profile click edit and check whether all certificates are selected or not.
In my case selecting all certificates and downloading that new profile solved the above mentioned issue.
Also make sure in your schema you have set "Build configuration" to the correct configuration, in most cases "Debug".
I got this error when export the ipa with App Store provisioning wrongly during CI process. My intention was to export with Adhoc provisioning.
I had the same error. My problem was that I checked 'Enable HealthKit' in Entitlements.plist, but I did not enable HealthKit when I created the App Id.
In short, all entitlements in your app (Entitlements.plist file in your project) should be configured on the provisioning profile you use (Provisioning profile = app ID + certificate + information about devices your app can run on).
Had the same problem that suddenly popped up in my project from one day to the next.
What fixed it for me was turning "Automatically manage signing" off and on again for both targets and making sure the right development team was selected once it was on again (defaults to none in my project).
It could seems a easy solution but I solved updating my iPhone's iOS version.
All answers I have seen talk only about xcode update. It was strange because my old iOS version was iOS 13.3.3 and it worked on another iPhone with iOS 13.6. After updating to iOS 13.7 it worked.
I have an app I am writing for iOS that will run just fine in Xcode but AppCode by Jetbrains says :
Error:Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) matching the team ID “(null)” were found.
So what I've been doing was keeping Xcode running so that I can hit the "play" button to deploy/compile my app while doing my actual work in AppCode.
Any ideas what could cause this?
madhurtanwani's link above helped, but I had to scroll to find the solution.
Here is the section that explains the issue and how to solve it:
It looks like in AppCode you are building for a device and in Xcode for a simulator. Simulator does not perform code signing, so you don't get an error there.
If all you want to do is to run the app in a simulator, then in the toolbar change the selection from "iOS Device" to a desired simulator. To be able to sign the app you need to make sure that you have correct provisioning profile and certificate installed and check your codesign build settings.
I had a similar issue and this link on their support site helped me: https://devnet.jetbrains.com/message/5509981#5509981
The crux is that on Xcode I was building for a simulator and in AppCode it was building for an actual device (which requires signing)
I had slightly different problem, and were using real device in both Xcode and AppCode.
I've changed team in one of my projects, and while Xcode were working completely fine, AppCode gave me error: No signing certificates found
The only thing that worked for me is changing Code Signing Identity from Apple Development to iOS Developer in Build Settings in Xcode:
I tried to build the sample code in Swift provided by Apple
A Productivity App Built in Swift
But when I ran it, it pop up an error like this:
"Command /Applications/Xcode6-Beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-stdlib-tool failed with exit code 1"
Does anyone know how to fix it?
The actual cause is because xcode cannot code sign:
iPhone Developer: no identity found
**error: Couldn't codesign /Users/zhaoj5/Library/Developer/Xcode/DerivedData/Lister-hehrkmcyuflnfucnsqcofjotmglo/Build/Products/Debug-iphonesimulator/com.example.apple-samplecode.Lister.ListerToday.appex/Frameworks/libswift_stdlib_core.dylib: codesign failed with exit code 1**
Command /Applications/Xcode6-Beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-stdlib-tool failed with exit code 1
This is because you are not a registered Apple Developer. If you go to project -> General, you will see there is a warning:
"This product type must be built using a provisioning profile, however, no signing identity or provisioning profile was specified, Xcode can resolve this issue by downloading a new provisioning profile from the member center."
There is a button "Fix Issue", you can enter your account information once you become a registered developer.
As the flip side to not being set up with a developer profile, I ran into this problem as a result of having duplicate certificates set up. Once I deleted all but one, Lister finally compiled.
As volatilevar mentioned, it's a problem with the project settings, though I assume you are a registered developer with access to the sample code and Yosemite beta. I had the same issue. The Provisioning Profile isn't selected because you downloaded the code and the previously selected profile doesn't exist!
If you installed Yosemite fresh, make sure you export your profile from Xcode where you were using it before and import it again in Yosemite.
Check that your profile and identity are correctly selected under General and Build Settings for the target.
If you need some guidance on moving your profile see exporting and importing.
My solution was to set both Code Signing and Provisioning Profiles to "Automatic" under My Project -> Target My Project ->Build Settings -> Code Signing Identity and Provisioning Profile