ios-provisioning

Upgrade testing for iOS - application-identifier entitlement does not match

自古美人都是妖i 提交于 2019-11-29 04:04:10
Previously with Xcode 7.3.1 I was able to build directly over my app store app on my iPad and test the upgrade scenario, which worked perfectly fine. This week I upgraded to Xcode 8 and when I try the exact same approach, I keep getting this upgrade error "This application's application-identifier entitlement does not match that of the installed application. These values must match for an upgrade to be allowed." I tried multiple solutions posted on this thread and none of them worked. I also don't have a watch app. Just a simple iOS app target. App installation failed due to application

Xcode won't recognize my new provisioning profile

给你一囗甜甜゛ 提交于 2019-11-28 23:07:33
My app's development provisioning profile expired a couple of weeks ago, so I went to the provisioning portal to get a fresh new one. After obtaining it, I visited the Xcode Organizer, removed the expired profile from my devices as well as my Mac, then imported the new profile. Xcode installs the profile onto my devices immediately, and my app runs again on the devices. The problem is that while the Organizer is able to see the new profile and install it as normal, the IDE gets confused between the old one and the new one. Every time I try to build the app, it fails immediately. The error

valid provisioning profile matching the application's Identifier could not be found

隐身守侯 提交于 2019-11-28 23:03:45
I'm trying to test my app on my device and am hitting the error stating "A valid provisioning profile matching the application's Identifier 'com.mycompany.MyApp' could not be found". I've read many similar posts here on SO but none have been able to help. What I've done so far: created a valid Provisioning Profile on the Provisioning Portal. When I look at the App ID of the profile, it is 10CHARSEED.com.mycompany.MyApp (where 10CHARSEED is obviously the Apple-generated seed id) downloaded and installed the profile in XCode Organiser, under the device name. XCode has the green tick and tells me

Is it safe to change the AppID Prefix between updates?

邮差的信 提交于 2019-11-28 22:23:52
问题 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

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

此生再无相见时 提交于 2019-11-28 22:08:25
问题 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

Apple: Enterprise Account, but deploy to App Store? [closed]

戏子无情 提交于 2019-11-28 17:51:48
I have been asked to build an app for a firm that has an enterprise account with Apple. The app has to go to iTunes. When creating a Distribution Provisioning Profile, I am given the option for " In House " or " Ad Hoc " There is no " App Store " option. How can this company distribute to the App Store? See screen shot here: According to this Enterprise FAQ page on Apple , you can't distribute on the App Store using an Enterprise account. The firm will have to also get a "regular" iOS Developer account: I am enrolled in the iOS Developer Enterprise Program. Can I distribute my applications on

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

天涯浪子 提交于 2019-11-28 16:38:29
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. If you are using Ionic / Cordova like I am see this announcement... https://github.com/apache/cordova-ios/issues/407 It's just one setting, then re-run your Archive to Submit to the Apple Store like normal. Go to "File" >

Publishing to TestFlight, new testers, do I really need to rebuild/download my provisioning profile?

空扰寡人 提交于 2019-11-28 16:11:05
I have published an app through the testflight website to allow my colleagues to test, and as more and more of them opens the initial email and find time to go through the registration process, testers are trickling in on my testflight team. However, the process to add them to the test seems a bit convoluted, so I thought I'd verify, and ask, if I'm doing it right, or if I have missed something obvious. At the moment the whole procedure looks like this: A colleague opens up the initial email, with the invitation link He/she then registers the device, and registers for the test I am informed of

Why not use development provisioning instead of ad hoc?

偶尔善良 提交于 2019-11-28 15:47:24
I was under the impression that when you use a development provisioning profile for a build of an app, only the specified developers can deploy that build to a phone. But I just deployed a build that uses a development profile to a phone using Xcode Organizer, even though I'm not one of the valid developers for that profile. One of my colleagues, who doesn't even have Xcode installed, did the same with his phone using iTunes. In that case, why not use a development provisioning profile for distributing your app to e.g. your QA team, instead of ad hoc distribution? EDIT: Please read the part in

“A valid provisioning profile for this executable was not found” error when trying to run unit tests

孤者浪人 提交于 2019-11-28 10:26:06
I have an Xcode workspace with unit test targets. The unit tests run fine in the simulator, and also run fine on one of my devices (a 4th-gen iPod touch running iOS 6). However, on two other devices (an iPad Air and a 5th-gen iPod touch running iOS 7), when I try to run unit tests I get an alert saying A valid provisioning profile for this executable was not found I only get this when running unit tests. If I try to Run the app on these devices, it installs and runs fine. I have verified that the (developer) provisioning profile set in the Code Signing build settings for the app includes these