How to Release to a Client's App Store Account

I work as part of a development team writing flutter applications. A client asked us to create and maintain a Flutter app for him, which is now nearly ready for release. Having read through any documentation I could find, I wasn't able to find any guidance on how to develop the application ourselves and release it to the client such that he can take ownership of it. The documentation always seemed to assume that the developer developed and realeased software for themselves, rather than to a client.



We assumed that we would develop and Test-flight the app on our account, which we have done without any problems. What we're having difficulty with is putting the software on the client's App Store account. One of our development team has been given admin and app manager rights on the client's (paid) developer account but is unable to create identifiers (they just appear in our account when he tries it). The client was able to create an identifier that we could use to add an app, but obviously the bundle ID was different to ours, which meant that when we tried to replace ours with it in xcode, we received a message that we couldn't use another team's ID. Hence, we can't upload to the client's App Store account.



If the method i've just described is not the way to go about it, could anyone tell me the correct procedure, please?

Something ive seen mentioned is an App Transfer, where we release on our account then App Transfer the app to the client's account, but would that mean we would have problems maintaining the app for him?



Thank you for any advice that anyone can give.

Answered by KMT in 375654022

Yes, you can't simply manage an app that has a bundleID belonging to another account with your account. The submittal process is the same, regardless of whom owns the account, however. It's just a matter of working with the proper credentails.


An app transfer is applicable if the two parties wish to maintain the original bundleID. It sounds like that is not a requirement in this example, so again, all you need to do is use the proper credentials you to sign in to Xcode accordingly.


Co-mingled account data means you're not signed out of your account, and/or not properly signed in with theirs.


The process, otherwise, when you use their credentials is the same as if the app was yours.


An alternative for you is to create another user on your mac, then run Xcode under that fresh user account and create a new team/provisoing account via Xcode prefs with their credentials. When that is complete, load the app, confirm the user's bundleID, option-clean the build (important!) and build for the store, and, same to maintain later. Note that Xcode can handle multiple dev accounts, so this process should not be necessary, but in cases where keeping track of different dev accounts is for some reason problematic, it can provide less confusion.


Note this assumes latest Xcode 10.3

Accepted Answer

Yes, you can't simply manage an app that has a bundleID belonging to another account with your account. The submittal process is the same, regardless of whom owns the account, however. It's just a matter of working with the proper credentails.


An app transfer is applicable if the two parties wish to maintain the original bundleID. It sounds like that is not a requirement in this example, so again, all you need to do is use the proper credentials you to sign in to Xcode accordingly.


Co-mingled account data means you're not signed out of your account, and/or not properly signed in with theirs.


The process, otherwise, when you use their credentials is the same as if the app was yours.


An alternative for you is to create another user on your mac, then run Xcode under that fresh user account and create a new team/provisoing account via Xcode prefs with their credentials. When that is complete, load the app, confirm the user's bundleID, option-clean the build (important!) and build for the store, and, same to maintain later. Note that Xcode can handle multiple dev accounts, so this process should not be necessary, but in cases where keeping track of different dev accounts is for some reason problematic, it can provide less confusion.


Note this assumes latest Xcode 10.3

How to Release to a Client's App Store Account
 
 
Q