I bought a new Mac, and installed Xcode again etc.
But I have problems with certificates and provisioning profiles.
In Organizer, Xcode is giving the error under the status of all my provisioning profiles:
"Valid signing identity not found"
Is it because I bought a new Mac?
I searched on the web a lot, but I couldn't find a working solution.
1)
do you have an older Macintosh that you used to build your iOS / MacOS apps on?
If so, you need to migrate your certificates and provisioning profiles.
This tutorial shows you how to do that.
2)
If you never built iOS or Mac apps before, then you need to create new certificates and provisioning profiles.
This related question should point you the right direction.
Related
I have troubles with saving an account credentials inside an IPhoneSimulator's Keychain. I cannot use AccountSaver.Create().Save(credentials, "app") without Entitlements.plist. However when I add it to my project, compilation error shows up:
Could not find any available provisioning profiles for iOS.
I've added iOS Development certifcate to my account on Mac and tried to create a free provisioning profile but failed due to a lack of IPhone device.
Suprisingly, when I tried to build dummy project with added Keychain to Entitlements inside Xcode on my Mac and run it on a simulator no compilation errors occured.
My questions are: Do I have to make Apple Developer Account to test my Xamarin.iOS app inside IPhoneSimulator or is it possible without it and I'm doing something wrong? If so, what should I do to be able to compile my app?
I use Visual Studio 2017 on Windows 8 connected to a Mac Agent (Mac Mini).
P.S.: Most posts states, that simulator doesn't need provisioning profile, but according to this thread:
Starting with Xamarin.iOS 8.10, if the Entitlements.plist file is set at all for the iPhoneSimulator build configuration, then codesigning is required and thus an iOS code signing certificate is required to be installed in your keychain. ~ Xamarin Forum
Some time has passed since I asked this question, but I think it deserves an answer not only in the comments.
As #wottle wrote it is required to be enrolled i Apple Developer Program in order to have access to Keychain.
I sugest also to use Xamarin.Essentials' SecureStore instead of AccountSaver.
We have a bunch of Apple Store applications that had their Apple Distribution profiles expired. The issue was gone once we regenerated the Apple Distribution Certificate and created a new Distribution Profile for the impacted Applications.
i installed xcode(6.3.1 beta) for unity ios app in Yosemite and was working fine when in upgrade to sierra and upgrade to xcode(8.1) xcode was not working and after checking in forms i found that it is OS issue i inatlled xlion .The problem i have another mac with Yosemite and installed the xcode(6.3.1) and was messed up with key chain and other certificated for provision and distribution.Now i totally messed with xcode and distribution in developer account certificates and i was totally working with it for past two days and clueless what to do,How can i clear all developer certificates and key chain certificates from xcode like development and distribution i want to reset all things in xcode and developer account and start from starch and setup again everything .Please what are the things we needed to delete in the developer account and xcode and key chains and setup again to start as a new.
Got to https://developer.apple.com/account/ios/certificate/
then revoke you certificate..
then go to xcode. add a certificate to your project using your account xcode then will create certificate for you.... cheers...
I have installed new inHouse provisioning profiles, however when I archive my build in Xcode, I am presented with a message saying the iOS development team is missing. I have xcode 6.4.
I know that you are able to build and sign an app if you don't have a developer team membership in Xcode.
Anyone know what is wrong?
Also another strange thing when I go into keychain to check if profiles and keys are there, they are not stored under the "Login" section like other profiles, but in "System". Is this ok?
Thanks
In order to archive your build (either for the App Store or Adhoc) it must be codesigned by Xcode. This requires a signing identity. Signing identities are only obtainable through the developer console at http://developer.apple.com/ and requires being a member of the apple developer program to access.
Sorry to break the news but without a developer membership you won't be able to archive your app for a device, but run it in the simulator only.
I have had many problems with certificates, provisioning profiles and bundle ids in the past and here is the latest.
When trying to run my App on an iOS device I get the following error:
Your application failed code-signing checks. Check your certificates, provisioning profiles, and bundle ids. Probably your device is not part of the selected provisioning profile (error: 0xe8008015).
I am aware of the following questions that touch similar topics but I seem to have perhaps a combination of them with something else:
Invalid Provisioning Profile- Missing Code-Signing Certificate
Xcode fails with “Code Signing” Error
why does xamarin suddenly not let me deploy to iOS devices
iOS 8, How to use device for development?
In the past the following things fixed a similar type of error message, however, this time the error at most changed slightly:
Go to Apple Member center and check that the device I am using is listed under "iOS devices"
Go to "Provisioning Profile" -> "Development" and check the profile is active
3.Check the device is listed in the provisioning profile. Re-download the provisioning profile.
4.Clean and build the solution a lot.
Any help would be appreciated.
I am using a macbook air running OSX 10.9.5 and iPad with iOS 8.2.
Xamarin version 5.7.2
Xcode version 6.01
As I was typing the last line of my question it occurred to me that I should check if my Xcode is up to date: It wasn't!
Solution:
Updated Xcode to the latest version (i.e. 6.2). In the update details it says: "Adds support for iOS 8.2 and WatchKit to create apps...".
While Xcode was updating I also did the following:
Correct a spelling mistake in my bundle identifier (To be EXACTLY the same as in my provisioning profile).
In Apple member center I had the possibility to update the list of devices. This is since I renewed my licence not long ago and it gave me the option to reset my previous list. I just followed the instructions and left exactly the same devices as I had previously.
After X-code updated I cleaned the solution and DONE.
I had few things going on so perhaps this won't be really useful to anyone but who knows... I hope this helps
I started some days ago a small Mac app for Mac OS X Lion. I've never uploaded a Mac app before, so this is the very first time.
This is what I've already done:
Created App ID
Created Certificate
Installed Certificate
Created a Production Provisioning Profile
Changed the App ID to my generated one
Created a new Configuration based on "Release"
Changed its Code Signing to 3rd Party Mac Developer Application
Selected the "Production"-Configuration which I created for the Archive-Scheme
Archived the Application
Now I wanted to "Share" the Application. Xcode (4.1 btw) said to me, there were no valid signing identities. Does I need to add an Entitlement.plist like in iOS? Have I forgotten something?
Update:
I just figured out, that I have to sign my app twice. I've still selected "3rd Party Mac Developer Application" but I can't select the Installer cert while submitting my app.
Have you installed the WWDR intermediate certificate? I just had the exact same problems and my issue was that the intermediate certificate was not installed on my machine. Granted, nowhere does Apple explicitly say you need it installed, more like suggestions. But, you do need it. You can find it here, or by going to Developer Certificate Utility under the Mac Developer Center.
I got it to work. I deleted my App and created it new.
I didn't create a new Configuration, and I only changed the Code Signing Indentity of the Target to 3rd Party Mac Developer Application. After this, I archived the app and then I was able to select the installer cert.