Thoughts on batch production of iOS applications

Purpose: compile, package and generate IPA through code, modify IPA, and then sign and package to generate more IPA.

Premise: iOS applications are configurable, whether through configuration files or exposed sdks (for example, exposed in Lua mode ).

Related tools and materials:

Https://code.google.com/p/iresign/

Http://www.ketzler.de/2011/01/resign-an-iphone-app-insert-new-bundle-id-and-send-to-xcode-organizer-for-upload/

Http://stackoverflow.com/questions/9708090/how-can-i-code-sign-an-ios-xarchive-so-a-client-can-resign-properly-using-pus

One idea about SDK design:

First, consider: the SDK is a function exposed by the program. What is exposed by the SDK itself? I think it should be the object model of the program.

There are many excellent software in the industry for our reference, such as Emacs.

In practice, you can refer to Emacs:

1. Define the corresponding model and function of the program.

2. Expose part of the model or feature through SDK. For example: Lua

3. decompress the packaged IPA Program, modify and add scripts to modify the program appearance and functions.

4. re-sign and package (different certificates can be used ).

5. Upload the AppStore.

The method should be relatively simple, focusing on the design of the object model and SDK, such as considerations for sandbox.

In addition, we strongly recommend that you use Lua as the SDK.

========================================================== ==================================

Modify ):

Because only the code is signed when a. app is generated, the resource is not signed.

Therefore, you can retain the. app, modify the configuration, and then package the. app signature into ipa.