From 7.0.0 the offline build splits the automation engine into two kinds. Before you choose, answer one question: after the service process drops, do you want another app to bring it back up.
The offline build supports iOS 15 and later only. On iOS 15 and later you can use offline main program v7.2.0 and later directly, as the USB automation program. The official download page has a pre-signed IPA. Install that first for testing. Phones below iOS 15 stay off this path.
Single app: sign only the main program
Single app installs only the main program. Open Automation options in the app settings, choose Single app, save, then turn automation on. The benefit written in the docs is that you sign one IPA, it is a bit faster, and it stays compatible with the previous usage.
A test phone can use the package already signed on the download page. To hang it under your own Apple developer account, an individual developer account is 688 yuan a year, up to 100 devices, iOS 12 and later. That is the signing fee Apple charges.
The script can read the current mode:
function main() {
logd(getAutomationEngineMode());
}
main();
A return of single means single app. To change the mode:
setAutomationEngineMode("single");
Single app fits these cases: one or two phones, and a person is nearby, so if the service stops you can tap turn-on again yourself. The package count is small, and the signing list has only the main program on it.
Dual app: sign a proxy IPA as well
Dual app, besides the main program, also signs and installs the proxy IPA. The two programs run in different processes. The docs state that if the automation service drops, self-activation can bring it back up, for unattended running.
When you set it, change the mode to dual app:
setAutomationEngineMode("dual");
getAutomationEngineMode() should return dual then. With only the main program installed and the proxy IPA still missing, stay off this mode.
The conditions for dual app are specific: the phone has to sit and run for a long time, with nobody nearby watching Start Automation. The extra signed proxy IPA is there so the processes stay separate and a dropped service can still be brought back. The signing list has to hold both the main program and the proxy program. When both expire, self-activation has no package it can start.
| Single app | Dual app | |
|---|---|---|
| Install | Main program only | Main program, plus the proxy IPA |
| Settings | Choose Single app under Automation options, save, then turn it on | Set the engine to dual, with the proxy IPA installed |
| If the service drops | Turn it on again inside the main program | Self-activation can bring it back up |
| System | iOS 15 and later, main program can be v7.2.0 and later | The same system requirement |
Get single app running first with the pre-signed IPA on the official download page. After you confirm the business needs unattended running, sign the proxy IPA and set the engine to dual.
About EasyClick: A mobile automation script development platform covering three phone ecosystems: Android without root, iOS without jailbreak, and HarmonyOS. It also offers Apple script writing, Apple cluster control, Android cluster control, remote cloud control, and AI phone cluster control. → Explore all products
Ready to build it for real?
Every approach in this article can be built with EasyClick capabilities on iEasyClick — full documentation, developer tools and automation products, free to try.