MoeSite Signer Documentation
How signer access, saved profiles, presets, library history, and source imports work inside MoeSite Signer
Contents
Introduction
MoeSite Signer is a web-based signing workspace for iOS IPA files. Start from /signer, then MoeSite will send approved sessions into the signer app while keeping this documentation public for everyone else.
Note: Signing applications requires a valid Apple Developer certificate or a personal development certificate. MoeSite Signer does not provide certificates. You must bring your own files.
Requirements
To use MoeSite Signer, you'll need the following:
- An IPA file (iOS application)
- A P12 certificate file (exported from Keychain Access or Apple Developer Portal)
- A mobile provisioning profile (.mobileprovision file)
- The password for your P12 certificate (if it's password protected)
- A modern web browser (Chrome, Firefox, Safari, or Edge recommended)
- A MoeSite session with signer access. Guest-style sessions may be available, but saved signer data still requires a full MoeSite account.
Basic Usage
Step 1: Prepare Your Files
Make sure you have all the required files ready:
- IPA file (the application you want to sign)
- P12 certificate file
- Mobileprovision profile
Step 2: Upload Your Files
- Click on the respective file selection buttons to upload your IPA, P12, and mobileprovision files.
- If your P12 certificate requires a password, enter it in the password field.
- Alternatively, if you have a direct URL to an IPA file, you can enter it in the "Direct IPA URL" field instead of uploading an IPA file.
Step 3: Choose Storage Option
Select one of the available storage modes:
- Temporary share link: Standard signing with an expiring install/share link
- Permanent direct link: Creates a long-lived direct link for your signed IPA when permanent storage is enabled
Step 4: Sign IPA
Click the "Sign IPA" button to start the signing process. The system will:
- Upload your files to the server
- Process and sign the IPA file with your certificate
- Generate an install button and a shareable landing page
Step 5: Install the Signed App
Once the signing process is complete, you'll see a success message with options to:
- Install the app directly on your device
- Copy the share link to send a landing page with app details and an install button
- Sign another app
File Requirements
IPA File
An IPA (iOS App Store Package) file is a compressed application bundle. Requirements:
- Must be a valid, unencrypted IPA file
- Size limit: 500MB (larger files may take longer to process)
- Should be the original application without previous modifications (for best results)
P12 Certificate
A P12 file contains your private key and certificate for signing. Requirements:
- Must be exported from Keychain Access or the Apple Developer Portal
- Should contain both the certificate and private key
- If password protected, you'll need to provide the password
Mobileprovision Profile
A provisioning profile connects your certificate with allowed devices. Requirements:
- Must be valid and not expired
- Should include the UDID of any device you want to install the app on
- Should match the certificate you're using
- For wildcard provisioning profiles, make sure the bundle ID in advanced settings matches your profile's allowed pattern
Advanced Options
Moe Signer provides several advanced options for modifying your IPA during the signing process. Click the "Advanced Modifications" button to access these features:
App Customization
- New App Name: Change the display name of the application
- New Version: Modify the version number
- New Bundle ID: Change the application's bundle identifier (must be compatible with your provisioning profile)
- Minimum OS Version: Set the minimum iOS version required to run the app
- New Icon: Replace the app icon with a custom image
Tweaks and Modifications
- Tweak Files: Add custom dylib or tweak files to the application
- Dylib Removal: Scan and selectively remove dylib files from the application
- Remove UISupportedDevices: Remove device restrictions from the Info.plist
- Remove watch apps: Strip Apple Watch components to reduce file size
- Enable document support: Add document support capabilities to the app
- Fakesign all binaries: Use fake signing for internal binaries
- Thin to arm64: Remove unused architectures to reduce file size
- Remove all extensions: Strip app extensions to reduce file size or fix compatibility issues
- Ignore encryption check: Try to sign even if the app appears to be encrypted
- Compression Level: Set the compression level for the output IPA (0-9, with 6 being the default)
Storage Options
MoeSite Signer offers different storage options for signed IPA output:
Temporary share link
This is the standard option where:
- Files are only temporarily stored on the server
- Links expire after the configured signer retention window
- Best for one-time installations or testing
Permanent direct link
This option provides permanent storage where:
- Your signed IPA is stored on a distributed storage network
- Installation links do not expire
- You can share the link with multiple people or save it for future use
- Ideal for distribution to multiple devices or maintaining a personal app library
Account Features
MoeSite Signer can be used in guest mode, but signing data is only remembered when it is tied to a MoeSite account.
Guest Mode
- You can still sign an IPA right away without stopping to create an account first
- The signer tabs remain visible so you can see what is available
- Saved signer data, history, and reusable setup tools are not stored for guest sessions
Saved Profiles
Store your P12 certificate, provisioning profile, and password in your MoeSite account so you can reload them without uploading everything again each time.
Presets
Save signer options such as bundle ID overrides, storage mode, compression level, and artifact removal selections so you can apply the same setup again later.
Library
Your signed app history lives in the library, including share links, install links, storage mode, and expiration state for older signer output.
Sources
Save AltStore-style source URLs, browse cached apps, and hand a selected app directly into the signer flow without rebuilding your source list every session.
Troubleshooting
Common Issues and Solutions
-
Invalid certificate or profile:
Ensure your certificate and provisioning profile are valid and not expired. They must match (be issued to the same Apple Developer account).
-
Installation fails:
Verify that your device's UDID is included in the provisioning profile. For enterprise certificates, ensure the enterprise is trusted in Settings > General > Profiles & Device Management.
-
Encrypted IPA:
If you receive an "IPA is encrypted" error, the application may have DRM protection. Try enabling the "Ignore encryption check" option, but results may vary.
-
Bundle ID mismatch:
If your provisioning profile only supports specific bundle IDs, make sure to set the correct bundle ID in the advanced settings.
-
App crashes after installation:
This could be due to incompatible modifications or signing issues. Try signing again with fewer modifications or using a different provisioning profile.
Frequently Asked Questions
Is this service free?
Yes, MoeSite Signer is free to use. You still need to provide your own certificate and provisioning profile.
Do I need a MoeSite account?
Not always. MoeSite manages signer access, and some setups may allow a guest-style signer session. You still need a full MoeSite account if you want saved profiles, presets, library history, or saved sources to persist.
Can I sign any IPA file?
Most unencrypted IPA files can be signed. However, heavily DRM-protected apps or those with complex entitlements may not work properly after signing.
How long do the links remain active?
Temporary links expire after the signer’s configured retention period. Permanent direct links stay active until their stored share record is removed.
Is my data secure?
MoeSite Signer processes your files securely. Even so, it is best to avoid using highly sensitive production certificates here and to prefer dedicated signing certificates when possible.
Can I install signed apps on non-jailbroken devices?
Yes, that's the primary purpose of this service. As long as your device's UDID is included in the provisioning profile, you can install the signed app on a standard, non-jailbroken iOS device.
Why does the app still ask for a developer to be trusted?
This is normal. When installing apps signed with a developer certificate, you'll need to trust the developer in Settings > General > Profiles & Device Management.