ios-provisioning

Error Your account already has a valid iOS Distribution certificate

徘徊边缘 提交于 2019-12-01 12:01:54
问题 I've seen other questions with this kind of error, but none helped me to solve my problem. I have my personal apple developer account and one from the company I'm working for. When I'm trying to submit an app for my company in order to beta test it I have an error: "Your account already has a valid iOS Distribution certificate". I tried importing developer profile again, but it didn't helped. 回答1: Just for documentation purposes: You need to edit your iOS Provisioning Profile in member center

Xcode 7.2: Failed to Locate or generated signing assets, Wild Card App IDs can not be used to create In House Provisioning Profiles

大兔子大兔子 提交于 2019-12-01 11:26:09
I signed an iOS App and WatchKit App & Extension targets with valid provisioning profiles (Separate provisioning profile for each app identifier, and not wild card App ID), Build was archived successfully but when I try to export/save Enterprise build, Xcode auto generate/locate XC: provisioning profile and it also and resets/invalidates previously selected provisioning profiles. I get below error. (even though we are not using Wild Card App IDs) "Failed to Locate or generated signing assets, Wild Card App IDs can not be used to create In House Provisioning Profiles". It seems like it is bug

Unable to Download App + App is No Longer Available

白昼怎懂夜的黑 提交于 2019-12-01 08:37:34
问题 We have an app that was distributed using Enterprise Distribution Profile. Now, the same app is working for some but others are reporting the following issues. Existing/Installed app throws this error, and doesn't open: {App Name} Is No Longer Available Users who try to download the app from the Enterprise link are reporting this error: Unable to Download App - {App Name} could not be installed at this time. Done Retry Users running iOS 8.4.1 are specifically reporting these issues. I

Your account already has a valid iOS distribution certificate from same machine

a 夏天 提交于 2019-11-30 18:23:04
问题 I am trying to create an IPA from my machine. While creating an IPA I am getting the error "Your account already has a valid iOS distribution certificate". I created the certificate and provisioning profiles, so all my code signing identities are on my machine. I'm able to run the app in device with the same certificate but unable to build the .ipa file. I am creating the certificates with admin rights (not with agent rights). I am creating Development certificate (not an ad hoc certificate:

XCode 5 hangs with a timeout error when validating/uploading a “ready to be uploaded” app

て烟熏妆下的殇ゞ 提交于 2019-11-30 17:28:20
I've been developing and uploading apps for some months. Whenever they needed being uploaded to the app store, I could do it without problem, but now, I'm stuck with one that doesn't want to be validated/uploaded. XCode says "the request timed out" after MANY minutes with a spinwheel on screen. The differences between my old updates to the app store and the one I'm trying right now are: -Xcode 4.X before, Xcode 5 now. -I had to recreate the app store certificate/provisioning profiles, because they just expired. -I inherited this project from other coworker (not here anymore) and maybe my

XCode 5 hangs with a timeout error when validating/uploading a “ready to be uploaded” app

匆匆过客 提交于 2019-11-30 16:38:31
问题 I've been developing and uploading apps for some months. Whenever they needed being uploaded to the app store, I could do it without problem, but now, I'm stuck with one that doesn't want to be validated/uploaded. XCode says "the request timed out" after MANY minutes with a spinwheel on screen. The differences between my old updates to the app store and the one I'm trying right now are: -Xcode 4.X before, Xcode 5 now. -I had to recreate the app store certificate/provisioning profiles, because

ERROR ITMS-90174: “Missing Provisioning Profile - iOS Apps must contain a provisioning profile in a file named embedded.mobileprovision.”

六月ゝ 毕业季﹏ 提交于 2019-11-30 06:17:32
问题 When I upload to Application Loader I receive the following message: ERROR ITMS-90174: "Missing Provisioning Profile - iOS Apps must contain a provisioning profile in a file named embedded.mobileprovision." I have this contained in my app folder. When I compress no matter how obvious I make the provisioning profile, I receive this error trying to upload my app for Apple. 回答1: If you are using Ionic / Cordova like I am see this announcement... https://github.com/apache/cordova-ios/issues/407

Is it safe to change the AppID Prefix between updates?

这一生的挚爱 提交于 2019-11-30 01:36:35
I am trying to understand the role of the first part of the AppID for iOS apps. This part was formerly known as the "Bundle Seed ID", but is now often referred to as the AppID Prefix. A while ago (iOS 5?), Apple made some changes in both their portal and their documentation and started to recommend using the "Team ID" (unique per developer account) as the AppID Prefix. This is simple and straightforward for new developers with new apps. But what is the the best practice for handling existing apps with regards to the AppID prefix? I know that it is not possible to change BundleID (= the second

Code Sign error: No unexpired provisioning profiles found that contain any of the keychain's signing certificates

拈花ヽ惹草 提交于 2019-11-30 01:20:41
I think I've reached the nadir of iOS provisioning hell. After migrating to a new mac and doing an archive for distribution, I received the error: Code Sign error: No unexpired provisioning profiles found that contain any of the keychain's signing certificates I then erased all certs and keys and provision profiles and did a "hard reset" (deleting all keys, certs, and profiles), following Apple's instructions by hand, with the same error. Then I did another hard reset and then had Xcode handle the whole thing via the Organizer, did another archive - only to see the same error. I have all certs

Difference between code signing target and project

可紊 提交于 2019-11-29 16:02:42
问题 I noticed that in Xcode I can set the Entitlements and Code signing settings both on: the Project (double click on the top item in Groups & File, which has the name of the project) the Target (under Targets, double click on your project name). What's the difference between these two? I know that with header paths, one tends to override the other (without warning of course...). 回答1: Target settings override Project settings. Project settings are valid for all Targets where the setting has not