After upgrading to iOS 5.01, I can no longer provision to the device. I see the provisioning profiles on the device (via Organizer). And my xcode has the same developer cert that used to work just yesterday.
Anyone knows what could be the issue?
Maybe you have to create one more time the certificated to add your device and profile, also, you can eliminate all the olders certificates to have only one.
Related
All,
I am a first time iMac user. Yesterday I installed Flutter.
I used my iCloud ID to create app signing, as I am only interested in experimenting with my iPhone.
By fooling around by trying to fix another issue ("Codesign wants to access key 'access' in your keychain"), I deleted my Xcode certificate. The net result is that I can neither recover nor re-create the certificate.
How can I fix this issue? Many of the StackOverflow related posts don't appear to apply to me as I don't have a developer account and I am not interested in distribution
I am using Mojave 10.14.6, Xcode 11.3.1
I see you commented, but have you actually opened the keychain app? most of the settings for Mac is, once the application is selected, in the upper left of the screen there are preferences and options in the keychain app to delete the keychain, which would allow a fresh start. Keychain can break easily in my experience
Everything seems to be working ...
I decided to check for firmware updates, and the Mac updated from Mojave to Catalina. For reasons I don't understand, but won't complain about, that fixed the certificate issue. The certificate was automatically regenerated/fixed (?) and Xcode stopped complaining
Using Xcode, I then tried to install the app on my iPhone. I had the following error dyld: Library not loaded which apparently was due to the fact that I was using a non-developer ID. The post recommended upgrading the iPhone to iOS 13.4.
Once I did that, however, Xcode (on the laptop) was out of sync with the iPhone. I upgraded Xcode to the latest version
Xcode successfully managed to install the app on my iPhone
Flutter successfully managed to install the app on my iPhone.
#Daniel and #Gordon, thank you for your assistance
I'm building mobile apps using Xamarin-Visual Studio. I have a MacBook Air that is my iOS build host.
Every day or two I have to reset my XCode signing identities, re-download my provisioning profiles, and then reboot the MacBook. If I don't, I am unable to install the IPA on an iOS device (it creates an IPA file but just won't install to device).
Any ideas why?
XCode version is 7.3.1. My setup was working fine for months. It started doing this for no apparent reason about a week ago. I'll also add that I have another build environment with an iMac that started doing the same thing at about the same time.
Absolutely nothing has changed with my Mac and Windows environments (although I'm not sure Windows/Xamarin have anything to do with this. Seems like more of a glitch on the Mac side).
Thanks in advance!
Making comment above an answer since there has been no activity on this since:
If you are sharing a signing identity with other team members, if another team member needs to use the singing identity, they will need to reset it and redownload the profile. And when they do, you will have to do the same when you need to use it again. Resetting the signing identity basically creates a new certificate (with the same name) and thus invalidates the profile that used the "old" certificate.
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'm trying to install my prov. profile via email,itunes. When I try to tap the prov. profile in email it just directs me to settings. I believe that there should be a pop up that ask to install the prov. profile but I see none. Did I forget any important parts that cause this trouble or maybe its a bug from new iOS 8 update?
"It's not a bug, it's a feature". Apple has purposely made it so that they can no longer be installed manually by a user and must be installed by dev tools such as Xcode or device management systems such as MDM. Additionally, they are no longer shown in Profiles & Device Management and are not removable by the everyday user either.
With iOS 8, Apple has moved to the model that any flow that requires the everyday user to install, remove, or even think about provisioning profiles is flawed and that iOS should handle this automatically on the user's behalf. If the provisioning profile is expired, iOS should get rid of it automatically. As apps are deleted, iOS should properly deal with the provisioning aspects automatically. This philosophy is mentioned in WWDC 2014's talk on Managing Apple Devices around ~42 minutes in.
I guess it's a bug. I'm having the same issue with Testflight.
As a workaround install the profile using Xcode's 'Devices' view.
I don't have the Apple 79€/year account. In iOS 5.0 and Xcode 4.2.1 I changed SDKSettings.plist ecc... And it works. In iOS 5.1.1 and Xcode 4.3.2 no, I already changed settings ecc but don't work, the app installs on device but crash on launch... How can I run my app on device without crashes? Thanks, and sorry for my english.
I have had this issue before on a jailbroken device. You have a few solutions depending on the exact issue. First you can install app sync in order to allow unsigned code to work on your device if you are not using a valid code signing identity. The second option is to actually get a valid code signing identity along with the provision profile so you can run the application correctly. This involves paying for the developer program so this may not be the best option.
Last is a very common issue with jailbroken devices. Which is that you will receive an error such as "failed to get the task for process xxxxx". This tends to happen a lot with jailbroken devices. This is because Xcode notices you are not using a provision profile that is required to report error logs. All you have to do is launch the application again on the device and everything should work.
This is just Xcode not being able to fully launch your application because of the missing provision profile so it results in a crash. If none of these solutions solve your problem please post a more detailed explanation of the issue you are having.