How can I send the iOS application to the client so that they can enter the code

Question

We created an iOS application for the client that we would like them to subscribe to and distribute the code.

What is the best method to do this? If I create and archive, and then share and save to disk (without re-signing), I get .ipa, as needed. My question is, how then will the client include their preparation? Sending the code to the client, unfortunately, is not an option, since we need to save the source.

Any help would be appreciated

Answer 1

Tell the customer to create a training profile.

The client will have to export his certificates and keys from access to the key chain and send you his certificates, keys and preparation profile. You can install everything on your computer, create an application with a client profile and send the assembly.

This should be safe enough from the point of view of the client, if he does not share his apple password with him.

Answer 2

Check out Erica Sudan App Subscriber. This utility allows you to opt out of an unsigned IPA with a different provisioning profile.

Easy to use, perfect for your needs.

http://ericasadun.com/ftp/Macintosh/

Obviously, it all depends on whether they have a contract for iOS development and creating their own training profile.

Answer 3

If your client has an agent level in the Provisioning Portal Resource, he can add you with an admin level. Thus, you will have less access level, but he will be able to give him a version of the "development" (in many aspects, as well as for the distribution).

This solution is much better than asking the client to export his private keys, especially if he has no experience with this.

Answer 4

I’m not quite sure that you can refuse the application the way you want it, but I think this is not possible. Thus, to get around the source code problem, you can compile a static library from your code and create an Xcode transfer project that generates a new application that you can send to your client. This way the code will be invisible to him, but he can compile it without any hassle.

Answer 5

• Just create xarchive using your certificate and provisioning profile and pass it to the client

• A client can open xarchive using xcode, and they can resign using their distribution certificate and provisioning profile and publish it to the appstore

PS:

• Verify that the client has the same package identifier added to the member center application identifier.

• Make sure that the customer provisioning profile reflects your project capabilities, as well as push notification, etc.

• In case of client rights, the client must enter the application and manually change the rights.

The file that they need to open in a text editor is archived by foam-entitlements.xcent and change PREFIX with their command identifier, which can be found here

<key>application-identifier</key> <string>PREFIX.yourappBundleID</string> <key>keychain-access-groups</key> <array> <string>PREFIX.yourappBundleID</string> </array> 

And it is better to ask the client to make sure that get-task-allow is false only if you signed your xarchive with the signature of the developers

  <key>get-task-allow</key> <false/> 

The same is true for APNS

 <key>aps-environment</key> <string>production</string> 

FYI: Many companies that I know follow this process because of their safety recommendations.