Public | Automated Build

Last pushed: 2 years ago
Short Description
isign docker image
Full Description


A tool and library to re-sign iOS applications, without proprietary Apple software.

For example, an iOS app in development would probably only run on the developer's iPhone.
isign can alter the app so that it can run on another developer's iPhone.

Apple tools already exist to do this. But with isign, now you can do this on operating
systems like Linux.

Table of contents

  • Installing_
  • How to get started_
  • How to use isign_
  • isign command line arguments_
  • Contributing_
  • More documentation_
  • Authors_

.. _Installing:



The latest version of ``isign`` can be installed via `PyPi <>`__:

.. code::

  $ pip install isign

Mac OS X

On Mac OS X, there are a lot of prerequisites, so the pip method probably won't work.
The easiest method is to use git to clone the source code repository <>__ and
run the install script:

.. code::

$ git clone
$ cd isign
$ sudo ./

.. _How to get started:

How to get started

All the libraries and tools that isign needs to run will work on both Linux
and Mac OS X. However, you will need a Mac to export your Apple developer

If you're like most iOS developers, credentials are confusing -- if so check out
the documentation on credentials <>__ on Github.

You should have a key and certificate in
Keychain Access <>__,
and a provisioning profile associated with that certificate, that you
can use to sign iOS apps for one or more of your own iOS devices.

In Keychain Access, open the Certificates. Find the certificate you use to sign apps.
Right click on it and export the key as a .p12 file, let's say Certificates.p12. If Keychain
asks you for a password to protect this file, just leave it blank.

Next, let's extract the key and certificate you need, into a standard PEM format.

.. code::

$ ~/Certificates.p12

If you get prompted for a password, just press Return.

By default, will put these files into ~/.isign, which is
the standard place to put isign configuration files.

Finally, you need a provisioning profile from the Apple Developer Portal that uses
the same certificate. If you've never dealt with this, the provisioning profile is
what tells the phone that you Apple has okayed you installing apps onto this particular phone.

If you develop with XCode, you might have a provisioning profile already.
On the Mac where you develop with XCode, try running the script.
If you typically have only a few provisioning profiles and install on one phone, it might find it.

Anyway, once you have a .mobileprovision file, move it to ~/.isign/isign.mobileprovision.

The end result should look like this:

.. code::

$ ls -l ~/.isign
-r--r--r-- 1 alice staff 2377 Sep 4 14:17 certificate.pem
-r--r--r-- 1 alice staff 9770 Nov 23 13:30 isign.mobileprovision
-r-------- 1 alice staff 1846 Sep 4 14:17 key.pem

And now you're ready to start re-signing apps!

.. _How to use isign:

How to use isign

If you've installed all the files in the proper locations above, then isign can be now invoked
on any iOS .app directory, or .ipa archive, or zipped directory. For example:

.. code::

$ isign -o resigned.ipa my.ipa
archived Ipa to /home/alice/resigned.ipa

You can also call it from Python:

.. code:: python

from isign import isign

isign.resign("my.ipa", output_path="resigned.ipa")

.. _isign command line arguments:

isign command line arguments


.. code::

isign [-h] [-a <path to applecerts.pem>] 
           [-c <path to your cert in .pem form>]
           [-k <path to your key in .pem form>] 
           [-p <your.mobileprovision>] 
           [-o <output path>]
           <path to app to resign>

-a <path>, --apple-cert <path>

Path to Apple certificate in PEM format. This is already included in the library, so you will likely
never need it. In the event that the certificates need to be changed, See the Apple Certificate documentation <docs/applecerts.rst>__.

-c <path>, --certificate <path>

Path to your certificate in PEM format. Defaults to $HOME/.isign/certificate.pem.

-h, --help

Show a help message and exit.

-k <path>, --key <path>

Path to your private key in PEM format. Defaults to $HOME/.isign/key.pwm.

-o <path>, --output <path>

Path to write the re-signed application. Defaults to out in your current working directory.

-p <path>, --provisioning-profile <path>

Path to your provisioning profile. This should be associated with your certificate. Defaults to

.. _Contributing:


Development happens on our Github repository <>__. File an issue, or fork the code!

You'll probably want to create some kind of python virtualenv, so you don't have to touch your system python or its
libraries. virtualenvwrapper <>__ is a good tool for this.

Then, just do the following:

.. code::

$ git clone
$ cd isign
$ dev/
$ ./

If the tests don't pass please file an issue <>__. Please keep the tests up to date as you develop.

Note: some tests require Apple's
codesign <>__
to run, so they are skipped unless you run them on a Macintosh computer with developer tools.

Okay, if all the tests passed, you now have an 'editable' install of isign. Any edits to this repo will affect (for instance)
how the isign command line tool works.

Sauce Labs supports ongoing public isign development. isign is a part of our infrastructure
for the iOS Real Device Cloud <>__,
which allows customers to test apps and websites on real iOS devices. isign has been successfully re-signing submitted customer apps in production
since June 2015.

This project not have an official code of conduct, yet, but one is forthcoming. Please contribute
to discussion here <>__.

.. _More documentation:

More documentation

See the docs <docs>__ directory of this repository for random stuff that didn't fit here.

.. _Authors:


Neil Kandalgaonkar <>__ is the main developer and maintainer.

Proof of concept by Steven Hazel <>__ and Neil Kandalgaonkar.

Reference scripts using Apple tools by Michael Han <>__.

Docker Pull Command
Source Repository