Hello all, This is the nearest category for what I want to post (as it involves Xcode more than anything else) so bear with me. I'm building a very simple iOS for a client. The client wants me to package it up when I'm done and send it to him so he can publish it himself under his developers account. He doesn't want me to publish for him under his account but, if i did, is it as simple as getting his distribution certificate etc? Has anyone done this for any of their clients? I was thinking the easiest way would be to use TeamViewer on the client's device and play around with xcode (assuming it's all set up correctly). Any opinion on the ups and downs of this? Secondly, if the client does just want the whole thing sent to him when built, what do I do? I was thinking of just zipping up the project and sending it via a file transfer site (like MailBigFile) for him to plug and play in xcode. Or am I missing something? Is this what adhoc distribution is for? Anyway, any suggestions as to the easiest way to bundle up a completed project and send it to a third party for publishing would be mush appreciated. Cheers.

Hi JimmySaver, You could easily publish it for him, under his account. He would just have to add you as an authorized user within iTunesConnect. Very simple to set up. Then you could publish it for him, but he would 'own' the app. Here's how to set it up: http://developer.apple.com/library/mac/#recipes/iTunesConnect_Recipes/Articles/ManageTeam.html If you need to send it to him, one method would be to zip it up, put it in your Dropbox account and send him a link to download it. Then you wouldn't be at the mercy of email. Good luck! Andy

Great stuff, Andy - exactly what I needed to know! Cheers.

Does this person understand the submission process? What are their concerns? I have a similar issue with a particular client who wants the same thing, but what I have told them is that's fine, but you will need to setup your developers account and make me a full admin on the account so I can create the ID, create the Provisioning Profile, setup app in iTunes Connect and submit app using the Xcode uploader. If they want to test the app, use the adhoc distribution as this is what it is for. Unless they are totally familar with the submission process and indeed have a Mac, its pointless and they will get stuck if they have never done before. Also if there is a issue, they will have to come back to you if app is rejected. They should just let you get on with it. Remember in iTunes Connect when setting up the app for submission, you can add there details if they want the app to show their companies details.

Well, the 'ad hoc' distribution is (I believe) for companies who utilize iOS in corporate devices, and rather than go through the App Store dance, they can distribute through an internal solution of distribution. Think large corp, like Macys or Cisco... I just gave a presentation today, and suspect I'll be going through the same motions... I 'planned' on having the client enroll, and provide me with the login. That way, I can create certificates, and do the motions of compiling the app and submitting the app 'for them'. Unless you use their credentials to create a certificate from your keymanager, you will also have to deal with the client creating the certificates (correctly), exporting them (correctly), and then you would need to import those keys in order to complete the process 'as the client'. Since enough developers have certificate issues, I can see that being a grand time. ;) If they wanted to do it themselves, You should be able to just zip up the project and email it to them. They would still need to do all the certs and keys and such. For me, everyone lives around the corner, so going a mile or two to an office isn't a big deal. But in remote situations, I've found the service "logmein" to be quite satisfactory for 'short term' remote interfaces with the client. It's basically remote desktop software, and if you're only doing one PC (have them sign up) then it's free. Just my take on the matter. I'm sure there are better ways, lol! Cheers! -- Smug (I completely spaced out the additional users in iTunes connect. Nice find, Andy!)

Hey Dragon, thanks for the response. I think they are somewhat familiar with the process but I guess we'll have to wait and see. Smug, I think that, as you say, they'll find the certificates process a headache. In any event, the client wanted total control over the submission (though I did point out the headaches prior to starting) and they also wanted to minimise the cost. The upside is that (and don't think I'm a capitalist monster for this) if the client can't manage, I've already quoted an additional fee for submission.

I always include a line item on my invoices for App Submission. I always follow that up with an offer to remove the line item if the client wants to learn how to submit the binary. Needless to say, I've never had a client attempt it themselves. I simply have distribution certificates on my machine for each client, and a login for ITC as well. Hope this helps.

I am of the counterpoint view ... The Client should own and manage the Certificates themselves. That is their "crown jewels" and should not give it away to "hired guns" (developers). With that mindset, the Client should then do one of two things: A. Use a remote login service, such as LogMeIn or JoinMe. Let the Developer guide or control the activities on the Client's Mac. That will help the Client to publish the app into Apple. Although, it means the Developer has to give the Client all of the Source Code! B. Have the Developer send an IPA file to the Client. The Client would then re-sign the IPA with his own Certificate and Distribution Provisioning Profile. Then Client can "publish" the app into Apple. This allows the Developer to retain the Source Code. How does that strike with you realists? :-) -- Niraj

Niraj, Resigning the IPA is a genius idea! Frankly the concept of some of my clients publishing their own stuff still sounds like science fiction to me, lol! But with the IPA concept, at least it's more 'portable' and eliminates a lot of steps in client side preparation for distribution. Have you done this? Is there a workflow that you follow to ensure all the details are met? Is is just 'match the bundle identifier' and go? This sounds like a great idea, but I haven't done it, so I'm curious about details... Cheers! -- Smug

Hello Smug, I use the iResign app from this Google Code repository: http://code.google.com/p/iresign/downloads/list I've noticed the app has been copied and updated on Github, yet I still use the original from Google Code because they have a compiled binary: https://github.com/maciekish/iReSign In any case, these simple steps suffice: 1. Specify the Client's Provisioning Profile for Distribution 2. Point to the IPA file that you had compiled under your Apple Developer Certificate 3. Use the name that your Client used. Open the Client's Keychain, click on Certificates, find the one labeled as "iPhone Distribution" or something like that (using my memory, not near a computer) That's it! -- Niraj