Im trying to follow the following None of the valid provisioning profiles include the devices as I'm trying to run an application on my iPhone 5 and getting the error "No matching provisioning profiles found". which is odd as it runs on my iPhone 6 fine...
when i log into developer.apple.com and click on 'Certificates, IDs & Profiles' it takes me to 'https://developer.apple.com/account/#/welcome' where it doesn't give me any option to add a device as all i can see is:
Is there another way of fixing the error?
Any help would be appreciated.
Note : As per the new rules (2019)
After a long research & contacting to the Apple team its getting more cleared Now.
Lots of developers thinking earlier when we were giving Admin access of the Developer account, We were able to access the Certificates & Provisioning Profiles. Why this option is disabled now ?
So here is the new Rules defined by Apple :
As per new rules if you have Individual Account than you would not be able to provide the Access of Certificates & Provisioning Profiles to the other Users.
Even if you are giving Admin access to any user they will not be able to access the Certificates & Provisioning Profiles.
If you have taken Enterprise account, than the option will be open for you to give access of certificates & Provisioning profiles to the other developers.
New Edition :
Suppose if you have a Individual Account & still you want your developer to access the Certificates & Provisioning Profiles ? Than you can contact the Apple Support team & send request for the same. If they will look the request suitable than they will help to give your Developer access of the Certificates & Provisioning Profile.
Hope this clear all doubts & helps to everyone.
If you have paid Apple Developer program and lost access to certificates, ID & profile, your admin or account owner can go to developer portal, under Peoples option tap on the specific user and check mark Access to Certificates, Identifiers & Profiles under Developer resources. See below.
Being a registered Apple developer gives you access to a lot of information, but to be able to send apps to the App Store (and Create and manage certificates) you need to enroll in Apple’s iOS developer program. This is the part that will cost you US$99 per year.
For more info go to this link
But you can able to run on any device With Xcode 7 you are no longer required to have a developer account in order to test your apps on your device
check here...
This is because you are not yet enrolled as apple developer.
Just you need to enrol as apple developer for personal or organisation.
Step 1: Go to this link Apple Developer Console
Step 2: Login with your apple id, if don't have create new one then login.
Step 3: Press the enroll button present in the top-right corner.
Step 4: Read the and agree the terms to proceed.
Step 5: Select the one from which you want to enroll either personal or organisation.
Step 6: Then select your payment option, then pay.
Step 7: Finally now you are a developer after completing all the steps, now you can find certificates tab in your account page.
You need to enroll in the apple developer program if you or your organization hasn't already: https://developer.apple.com/programs/enroll/
Related
How can we associate developer account to enterprise account in large companies ?
Here my situation :
I have a Enterprise account ($299), with 100 iPhone devices added to it. Since i cant add more devices now, apple recommended me to purchase developer account ($99) and add new additional devices to it.
Here’s my question :
If my Ad-hoc profile, Dev Profile and App ID belong to Enterprise account ($299), how can i add the devices from the developer account ($99) to the profiles in Enterprise account($299)?
If my new App ID belongs to developer account ($99) and later if i need to sign the app with In-house profile using my Enterprise account ($299), how can i do it?(should i Re-sign it by creating new app ID in my Enterprise account)
PS: I went through several solutions in Stack Overflow but didn't find exact answer. (Please don't mark this as duplicate, i know there are few similar questions)
These are some of the solutions on Stack Overflow:
Managing IOS Developer AND IOS Enterprise Developer accounts
Apple Developer and Enterprise Programs together
How is a large, spread out company supposed to work with the iOS Developer Program?
Can someone give a perfect solution for my situation, thanks in advance :)
Signing an app with an enterprise profile will let you install it on any device you want (without having to register anything). I think thats the key feature of this account type.
Each App ID can only be used once, so you cannot use it in both accounts. You'll have to pick another one then:
Example:
Dev Account: com.yourcompany.yourappname
Enterprise Account: com.yourcompany.yourappname-enterprise
Of course you could use wildcard IDs but, some capabilities wont work then.
Basically the enterprise and dev accounts are completely separated. While you can be a member of both accounts with the same Apple ID, and switch them while you are logged in, the accounts themselves have nothing in common with each other.
Conclusion
For In-House-Distribution you can use the enterprise account, without the pain of registering all the devices
For App-Store Distribution you'll need a separate developer account
I am a developer and I am making an app for my client.
I have indie developer account so During testing period I am using client's UDID to build ipa file so they can test on their iOS devices.
Now client will distribute final ipa file into itunes connect.
so What are the different legal solutions for this?
Assume that they have indie developer account too and client is non-technical so they don't want to mess with xcode or source code.
And in future I will do the same for other clients too.
In order to submit an app to iTunesConnect, it has to be signed with a valid distribution certificate and provisioning profile that match the developer account they are submitted to. That means that someone (whether it's you or your client) needs to create an appID, a distribution certificate and a matching app store provisioning profile that you will then use in Xcode to sign the ipa that will be submitted to the store.
Since your client isn't a technical person and you will most likely be able to do that process much quicker and more efficiently than he/she will, the best solution would be for your client to simply give you the credentials to the developer account and for you to perform these steps there. If that's not an option, and your client has a company account (and not a personal account), he/she can give you access to their account by adding you to their development team - that way, you'll still be able to perform the necessary actions on the account, without having the admin's personal credentials.
As for the submission itself, once you have a signed archive, you can either submit it directly via Xcode or you can send the signed ipa to the client, and he/she can submit it via Application Loader from their admin credentials. But, you will still have to sign it with valid certificate/profile from the right developer account.
I hope this makes sense and makes things a bit clearer. Good luck.
I'm wanting to view an existing profile that I have already installed on my iphone. I wanted to know where and how can i view the details?
Thanks
There is no such term as APN profile. There is provision profiles and there is APN certificates that embedded into provisioning profiles. You can check list of all provisioning profiles in Settings -> General -> Profiles. You will be able to get a minimal information about required provisioning profiles such as when it received and expires. You will also be able to remove it if you want. They do not provide any specific information related to APN through this UI.
In device , you can see it in
Settings->General->Profiles
In development system, You can see it in Keychain
Open the Finder->Applications->Keychain
In key chain you can use search option and use the searching string as "iphone".
You can see the installed provisioning profiles under Xcode->window->Organizer->Devices
I'm sorting through the various Apple docs, but haven't seen it yet.
Here's the deal: I've created a series of apps that are for a service for NPOs. These are hugely popular (albeit in a very small pond), and I have been asked to make customized versions for some of these organizations.
It's a FOSS app, but these outfits can't get iOS programmers to build and release the apps. They are willing to set up App Store accounts, but don't have the geeks on hand.
Due to the way the organization manages its IP, I am not allowed to release branded apps under my app store account. They need to release under theirs.
I don't want to set up an enterprise account for this. I haven't read up on that, but I'll bet that it would not be practical, anyway.
Is there a reasonable way for folks to take apps built on one account, and apply a new provisioning profile, and release it via another account?
Yes a company can take any developer app, sign it with their own certificates, and submit it using their own iOS enrolled team leader ADC account. They can even hire a contractor or temporary employee and legally authorize them to do this work for them.
If you do this type of subcontracting, you might want to get authorization in writing from the CEO, COO or chief legal consul of the company to do so.
you can use a different provisioning profile and deliver the app to the other guys. You can have multiple profiles in your X-Code and select with which one you want to sign the app when you create the archive.
You can either do this yourself by getting access to your client's app store signing certificates, or you can get your clients to use their codesign tool - details on the latter technique can be found on google - here is one example.
Enterprise accounts don't let you release on the App Store.
A typical way of handling this is for them to set up an account and give you the details for the team agent to log in. You then generate a key pair and a certificate signing request in Keychain Access. You log in as the team agent and use the certificate signing request to get a distribution certificate, which you then download and open - this will install into the keychain. Export the key pair and supply this to them so that they aren't screwed if you get hit by a bus or something.
From that point on, it's all stuff you should be used to. Xcode knows which private key to sign the build with because it matches the provisioning profile. It knows which provisioning profile to use because the app ID in the profile matches the app ID in the Info.plist file. Beta testing with ad hoc builds is the same as normal, except you register the UDIDs after logging into their account, not yours. Archives are not tied to your account.
When you submit the app through Xcode, you'll have to supply the team agent login details again. The submission will show up under their developer account, not yours.
Technically speaking, I think it breaks their developer agreement with Apple for them to supply a third-party (you) with their login details. However I don't believe it's possible to delegate all of the privileges necessary to submit an app to anybody other than the team agent, and the parts that can't be delegated aren't easy to explain to a non-technical person. You can script some of it to make it easier, but it's easy for them to get into a mess, so it's usually best if they let you handle it all.
My team and I have been contracted by a company to develop our first iPhone Application.
I am wondering how this contractor relationship is best handled. Does the $99 SDK/Dev connection account need to be established under the contractor's name, so that when the application is approved it isn't listed by our company's name, but by their business name?
Essentially is it best-practice to submit the application under the contractor's name or is there an option to define this when you apply?
You get an account and they get an account.
Accounts serve two functions. Access to the development tools and access to the business interface for the company publishing the app.
You sign up once. Each client signs up for their own account for the most important reason. That's where the bank information is to tell where the money goes. :). And contracts and sales data, etc.
The best way for it to work is for you to do development under Wildcarded developer and distribution (ad hoc) code signing keys (your account). You sign for multiple clients with the same keys. Then at the end, you sign and publish with a specific AppStore key (each client's account).
That will allow you to do control development, testing and beta distribution. When development is finished, you zip up the release version signed with their key and they upload it via iTunes Connect under their account.
Bonus section:
This configuration is easy to set up in XCode (once you get over the 24 hours of strangling yourself getting your head around how xcode and the distribution certificates work).
Go to Project->Edit Project Settings->Configurations. Duplicate two new configurations off of the "Release" configuration. Call one "Ad Hoc", the other "AppStore". Set your signing certificates as follows, iPhone Developer for Debug/Release, iPhone Distribution (Ad Hoc) for Ad Hoc, and their iPhone Distribution (AppStore) for "AppStore". Forget you even have a client until the end, then switch to AppStore distribution, build, zip, email, and done.
In practice, it's more complicated than that as you'll need to set up multiple certs/profiles/keys on your machine, but once you're done, it basically runs like this.
I would create the dev account and publish it under the company that will own the app and the source, regardless of who is developing it.