FAQ

What is the difference between online and offline signing?

Online signing uploads the IPA and certificate materials for server-side processing—best when you want personal storage, higher limits, or install links. Offline signing finishes in the browser and does not upload the package by default—better for privacy or constrained networks. Both need a valid certificate and provisioning profile.

Do offline tools upload my IPA to the server?

No, by default. Offline sign, edit, and analyze process files in your local browser. Only online tools temporarily store necessary files during processing, then clean them up per the rules.

What materials do I need to sign?

Typically an IPA, a P12 certificate (and password), and a matching mobileprovision profile. Bundle ID, certificate, and device UDID in the profile must match the target, or you may sign successfully but fail to install.

Why did signing fail, or why won’t the app open after install?

Common causes include expired certificates or profiles, a wrong P12 password, certificate/profile mismatch, a device UDID missing from the profile, unsupported OS versions, or a damaged package. Inspect the P12 on-site, verify the UDID, then retry.

How do guest and signed-in quotas differ?

Signed-in users usually get personal storage and higher upload/signing limits; guests have a smaller allowance—see the UI and account page. When a quota is exhausted, wait for reset or sign in to use account limits.

How do I install a signed IPA on a device?

Use this site’s install page link, or import the IPA into your signing/install tool. Enterprise, personal, and TrollStore-style flows differ. If install fails, confirm the certificate covers the device and check Profiles & Device Management / trust settings.

Where can I get help?

Start with this FAQ and the User Guide, and double-check your certificate materials. If you still need help, join the community via the footer link, or see the contact notes in the Terms of Service.