My customer's iOS in-house provisioning profile is ending in 2 weeks. So, to renew them, I wanted to create a new in-house certificate but when the "add" on-house and ad hawk option is disabled, clicking on what could be the reason?
I passed the client's license to the license yesterday Has it been renewed before I can re-create in-house certificates? (This works on all my other clients (non-enterprise) accounts)
I am an agent company The enterprise account of your and your issue is mainly as stated above: The existence of two enterprise carats where I am a bit confused, so many people are working as your agent. Apple has signed an enterprise account & amp; Amp; The portal is such a way that a company-wide agent should have full control over that enterprise distribution certificate and it is connected with its CSR / private key. If you really want to do this, then you should be in charge of the account. The agent will have to catch up and call it CSR & amp; Distribution proof so that you can develop against it. If you are not doing, then suggesting that the organization which produces the final product for enterprise deployment, should better coordinate our efforts with the agent because they have a plan that you do not know.
About multiple certificates
At the end, one point is that at the same time you can easily create a new distribution proof on your app at the same time Can cut from The certificate is good for 3 years Your provisioning profile will still expire in 12 months, to ensure that your client is determining their updates & amp; Proper maintenance rhythm
I feel free to shoot any questions on this. Good luck!
Edit
The agent's role is to serve as a gatekeeper for a company. This creates a problem for a large company to pump a multi-in-house application, but the control factor helps in maintaining a compositor environment
Where are you starting to get into trouble , When your original proof ends and you need to roll them into the new certificate, for which the agent has access. He / she has to export your private key to compile your code or use the key so that you can use that new Enterprise District Proof.
Generally what an agent creates first evidence and all in-house applications are signed for it. This proof will end in 2016 as an example, per profile will end every year, although each app must update at least every 12 months to refresh itself with the new Pro Profile. Fast for the end of 2015 and you are reducing the expired evidence. If you want to create a replacement certificate, update the provisioning profile for each active app with the new certificate (the length of time to say in 2019), then each app with a new Pro profile attached to the new certificate before the 2016 certificate. Update.
Understand?
No comments:
Post a Comment