provisioning-profile

How to find out what profile was used for building *.ipa file?

最后都变了- 提交于 2019-11-27 11:11:05
Is it possible and how to grab that information about profile just from existing *.ipa file? I can give you a direction in this, not sure if it'll actually help: Change the extension of the *.ipa file to *.zip . Un-archive this zip file. The folder contains a *.app file. Open its package contents by right clicking it. Inside, you'll find an embedded.mobileprovision file. EDIT- Since Xcode 6 doesn't show the provisioning profile, I'll extend the answer to still see the details: Change the extension of the embedded.mobileprovision to embedded.txt or just open it with any text editor of choice.

Xcode 7: App installation failed: A valid provisioning profile for this executable was not found

老子叫甜甜 提交于 2019-11-27 10:14:29
问题 I have already searched and almost implemented max solution but it's not installing any app even though if I am creating just sample single view app. App installation failed A valid provisioning profile for this executable was not found. 回答1: ============== update ==================== I fixed this issue today. First, go to ~/Library/MobileDevice/Provisioning Profiles . Make sure Xcode isn't running. Then, delete all provisioning files (like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.mobileprovision

Over The Air (OTA) iOS IPA File Distribution For Public?

时光总嘲笑我的痴心妄想 提交于 2019-11-27 10:10:40
I saw this Chinese company offering a demo for their app/service which is a "ipa" file. You can simply visit a link by your iPhone via Safari and you can install the demo ipa file. The link is right under the iphone app download button. This makes me wonder what stops people from distributing their app this way outside the Apple app store. A legal issue, but technical can-do? And I am also wondering what the provisioning profile they have used is, to generate this ipa file from XCode with such broad capacity of installation. As far as Ad Hoc distribution profile goes, it allows only 100 users,

Provisioning profile for Today Widget extension

只愿长相守 提交于 2019-11-27 09:20:48
问题 I am trying to archieve my app for submission however I am running into issues with code signing. Basically I have a Today Widget extension for my app. I am unsure about what I should be setting the provisioning profile as. I assumed that I would just use the same profile that I have used for my app, however I get this error: The provisioning profile specified in your build settings (“AppName”) has an AppID of “BundleID” which does not match your bundle identifier “BundleID2”. Xcode can

Make an .IPA for iPhone and iPad

瘦欲@ 提交于 2019-11-27 08:11:15
问题 As I had asked this question already and didn't get the answer that I needed, the problem is as follows: I developed a game for both iPhones and iPads. Everything is working fine but now I want to Archive my project. As I already have signed in for an Apple account, the problem is I don't have another device to register with. And, according to Apple's terms and condition "Creating a provisioning profile requires one or more devices to be registered with your Account." Is there any way we can

A valid provisioning profile for this executable was not found… (again)

走远了吗. 提交于 2019-11-27 07:23:16
I know this has been asked and answered multiple times but I'm tearing my hair out as none of the proposed solutions appears to work. I receive the above error, despite having a valid provisioning profile which, as far as I can tell matches the bundle identifier: I've followed the steps in various suggested solutions on this site, including deleting all existing certificates and starting again, as suggested here and here . One thing I have noticed is that the profile doesn't show up in the code signing lists, either for target or project. Can anyone offer any further suggestions? John Starr

The executable gets signed with invalid entitlements in Xcode

与世无争的帅哥 提交于 2019-11-27 07:09:15
I got this error with Xcode 5 when I try to run the app on my device. The executable was signed with invalid entitlement It worked fine with Xcode 4.x. Anyone knows how to get rid of the error? I grappled with this issue for an hour, and finally found a fix. Turned out the Development Team was different in ProjectTarget and ProjectTests. Restarting Xcode was what worked for me. I found out the problem. The app I created on developer.apple.com does not include inter-app-audio. The project entitlements plist file on Xcode has inter-app-audio set to YES (by default). Once I changed the setting on

Can't build an app for distribution after joining existing enterprise developer program

ぃ、小莉子 提交于 2019-11-27 07:07:23
问题 I joined an existing enterprise developer program . I was able to run the app in developer mode, but had issues with building and archiving. The certificate for creating a universal distribution app is already present, but I am not able to build with it. How can I do it in steps?? 回答1: The certificate is only half the necessary parts. You also need the key for the certificate. Open Keychain Access on your Mac and select the Certificates filter on the left. When you select the certificate for

How to manage Personal Team info on Apple Developer website?

可紊 提交于 2019-11-27 05:12:24
问题 Ever since WWDC 2015, developers now have a Personal Team in addition to the other teams they are members of. My account is part of an organization as well, so when I go to my Accounts in Xcode, I see something like so under Team Names: Organization , Agent, Agent User (Personal Team), Free, Free I accidentally created an app identifier using the "Fix It" button in Xcode using the wrong team (personal team instead of the organization). Now if I attempt to register that App ID for my

Xcode6 error: “No matching provisioning profiles found for application”

…衆ロ難τιáo~ 提交于 2019-11-27 04:23:24
问题 I'm trying to submit my iOS app in Xcode6. When I click Submit or Validate in the organizer, a window pops up that says: Failed to locate or generate matching signing assets: Xcode attempted to locate or generate matching signing assets and failed to do so because of the following issues: No matching provisioning profiles found for "Applications/MyApp.app” None of the valid provisioning profiles allowed the specified entitlements: application-identifier, beta-reports-active, keychain-access