[tags:signing certificates,provisioning profiles]

3,561 results found

Post not yet marked as solved
2 Replies
I have occasionally encountered this problem before and not found a solution other than deleting and reinstalling. You can install a previously compiled development version to test your upgrade path, or you could archive the data from the App Store using Xcode, then replace with your development build and restore the data as another alternate way of testing the update.
Post not yet marked as solved
1 Replies
456 Views
Using Xcode 7 which is also managing the provisioning profiles. I just added a new device online in the portal, but it is not getting added to the provisioning profiles. I know this because the device count is not changing in the profile's details. How do I get the device added so I can debug my app on it???
Posted
by
Post not yet marked as solved
17 Replies
Same here. I think some issues occured in Apple serverI could archive the build an hour ago.But at this moment, it gives this error.
Post not yet marked as solved
6 Replies
This happened to me after installing a build from TestFlight and overwriting it with the debug build from Xcode.Nothing helped, no clean build, no Derived Data voodoo …How I finally got it working was:- Delete debug build from phone (and watch if it’s still there).- Download TestFlight build again.- Install Test Flight Apple Watch app build from TestFlight app.- Delete TestFlight Watch app build from Phone using the TestFlight app.- Delete the TestFlight iOS app build from the phone- Now everything seems back to normal. I can run the debug build from Xcode.
Post not yet marked as solved
7 Replies
Same here.Transfered agent roles, start happening. Changed again. It didn't help. Apple support ask me to clear safari cache. what a joke.
Post not yet marked as solved
4 Replies
Mentioning a critical fact like you are using something other than plain Xcode to build when your initial posting is about a build problem would probably be helpful in the future.
Post not yet marked as solved
9 Replies
Same here.Bug filed23362706
Post not yet marked as solved
0 Replies
135 Views
When trying to sign an App I have built. XCode crashes. Saying I don't have entitelements to sign Mac OS X Code - only iOS. I have an enterprise development account - which i thought gave me everything under the model announced at WWDC. Am I wrong in that there is only one Development program now? Or is there somewhere to Buy the Mac OS X developer access that I can't find? (When I try, it says I am already a member of the Apple Developer Program and I can;t buy anything other than Technical Support Incidents) Thanks in advance.
Posted
by
Post not yet marked as solved
5 Replies
My memory is hazy but I thought when they announced it at WWDC they said this fall.
Post not yet marked as solved
6 Replies
837 Views
I was putting the final touches on my production build scripts when I discovered that the apps I'm producing won't run on some machines.My final build target builds that products for distribution (DEPLOYMENT_POSTPROCESSING=YES, Target=Deployment). These are then packaged in a disk image.I can open the disk image on my computer and run all of the apps. Note that some of the app bundles include privileged helper tools that must be correctly signed, and apparently they are because they get installed.I then copy the disk image to three other test systems (OS X 10.7, 10.9, and 10.10) and try to run them there. None of the apps will launch. I get a message that they are from an unidentified developer. (Note that all of these systems, including mine, only allow App Store and identified apps to be launched.)If I perform a codesign --verify or codesign --display -r- and dump the signing information for the apps, everything looks like it's been signed. (If I do the same to an Apple app like Numbers, I get a very simila
Posted
by