BuildBox

BuildBox can be installed on a compatible iPhone running iOS 18 or later.

The application is distributed as an unsigned IPA. You need a compatible sideloading tool to install BuildBox for the first time.

How to install BuildBox IPA

1. Open Settings → General → About on your iPhone.
2. Check that your device is running iOS 18 or later.
3. Visit the official BuildBox GitHub repository.
4. Open the Releases section.
5. Select the latest release, BuildBox v2.1.0.
6. Download the available BuildBox IPA file.
7. Save the IPA in your Files app.
8. Open AltStore, SideStore, ESign, Feather or another compatible installer.
9. Import the downloaded BuildBox IPA.
10. Complete the signing process using your supported configuration.
11. Install BuildBox on your iPhone.
12. Enable Developer Mode if requested.
13. Open BuildBox from your Home Screen.
14. Explore the Catalog, Compile, Sign and Signed sections.
15. Configure your GitHub account if you want to compile Swift projects.
16. Import a compatible signing certificate if you want to sign applications.
17. Start using the available app-building and IPA management features.

How to compile Swift apps using BuildBox

1. Open BuildBox.
2. Select the Compile tab.
3. Write or paste Swift code, or import a supported Swift project.
4. Sign in to GitHub when requested.
5. Follow BuildBox's instructions to prepare your private build repository.
6. Start the build.
7. GitHub Actions will compile the project remotely.
8. Monitor the build logs and progress.
9. Download the unsigned IPA after the build completes.
10. Open the Sign tab if you want to install the newly created app.

You need an internet connection and an eligible GitHub Actions workflow to compile the application.

How to sign an IPA using BuildBox

1. Open BuildBox and select Sign.
2. Open the certificate section.
3. Import your .p12 signing certificate.
4. Import the matching .mobileprovision provisioning profile.
5. Enter the certificate password if required.
6. Select Import IPA.
7. Choose an IPA from Files or the BuildBox library.
8. Review the app name, bundle identifier and version.
9. Make changes only if they are supported and necessary.
10. Tap Sign.
11. Review the signing log.
12. Wait for BuildBox to finish.
13. Open the Signed tab.
14. Select the signed app and tap Install.

How to install an IPA without ESign

Once BuildBox has been installed and configured with valid signing credentials, you can sign and install compatible applications directly from its own interface.

BuildBox uses a local HTTPS installation workflow. A separate ESign installation is not required for each subsequent compatible IPA.

How to use BuildBox app sources

1. Open the Catalog tab.
2. Browse MikeBuilds Apps or the ryP0 catalog.
3. Open the Sources sheet to manage compatible app sources.
4. Select an application.
5. Download an available authorized IPA.
6. Sign it using your own compatible certificate.
7. Install it from the Signed tab.

Important: BuildBox does not supply signing certificates or remove Apple's provisioning restrictions. Protect your certificate password and private signing keys.

BuildBox combines Swift app compilation, IPA signing, installation, app discovery and package customization in one iPhone application.

Swift App Compiler

Write, paste or import compatible Swift source code and start a build directly from your iPhone.

GitHub Actions Compilation

BuildBox uses GitHub Actions to compile Swift applications. Compilation takes place on GitHub's build infrastructure, not locally on the iPhone.

Private Build Repository

The developer's compilation workflow uses a private repository within the user's GitHub account.

Unsigned IPA Downloads

After compilation, BuildBox can download the resulting unsigned IPA for signing or sharing.

On-Device IPA Signing

Import a compatible signing certificate and provisioning profile to sign IPA packages directly on your iPhone.

P12 Certificate Support

BuildBox supports .p12 certificates with matching .mobileprovision provisioning profiles.

Direct IPA Installation

Install correctly signed applications directly from BuildBox through its local HTTPS installation workflow.

Signed IPA Library

Manage signed applications with app icons, search, sharing and installation options.

App Name Editing

Change the display name of compatible applications before signing.

Bundle Identifier Editing

Edit an application's bundle identifier when supported.

Some applications depend on their original identifier, so changing it may break app groups, notifications, sign-in or other functions.

Application Version Editing

Modify supported app version metadata before signing.

Dylib Injection

BuildBox supports injecting compatible .dylib files into applications before signing.

The injected library must be able to operate in the installed app's environment.

DEB Tweak Injection

Version 2.0.2 introduced support for attaching compatible .deb tweak packages.

BuildBox can unpack supported packages and include their libraries, frameworks and resources in an IPA before signing.

Multiple Tweak Packages

Compatible builds can attach more than one DEB file or a ZIP containing multiple tweak packages.

Important Injection Limitations

Tweaks depending on a full jailbreak environment, Substrate, ElleKit, system daemons or unavailable entitlements may not work after injection.

An incompatible tweak may cause the target application to crash.

App Sources

BuildBox supports compatible AltStore and ESign-style JSON app sources.

MikeBuilds App Catalog

Browse applications from the developer's own catalog.

ryP0 Catalog Integration

Version 2.1.0 adds the ryP0 application catalog directly to the BuildBox Home tab.

App Search and Discovery

Browse available apps and choose compatible downloads from connected catalogs.

Catalog Refresh

Version 2.1.0 adds a refresh button for loading updated catalog information.

App Requests

The Add tab allows users to request an application for the catalog.

Cryptographic Signature Checks

Version 2.0.3 improves installation checks so the Install action becomes available only when BuildBox recognizes a valid cryptographic signature.

Signing Stability Improvements

Version 2.1.0 fixes a problem that caused some successfully installed apps to fail when opening.

Catalog Signing Fix

Version 2.1.0 also fixes a crash that could close BuildBox when signing an app downloaded from its catalog.

Signing Logs

View detailed signing information and copy logs when troubleshooting a failed installation.

Compile Logs

Review the progress and errors returned by the GitHub Actions build workflow.

Clear All Logs

Version 2.1.0 adds an option to clear the Sign and Compile logs.

Updated Interface

BuildBox v2.1.0 uses a redesigned layout with Catalog, Compile, Sign, Signed, Add and About tabs.

No Jailbreak Required

The main BuildBox workflow works without installing a traditional jailbreak.

Supported iOS Versions

1. iOS 15 - iOS 27.2

Supported Devices

BuildBox is designed for compatible iPhones.

The original documentation focuses on iPhone, so full iPad support should not be claimed without additional developer confirmation.

Computer Requirements

A Mac or Windows PC is not required for BuildBox's main compilation, signing and installation workflow after initial setup.

However, you still need internet access for GitHub Actions compilation.

Signing Requirements

You need a compatible certificate and provisioning profile to sign IPAs.

Applications may require specific entitlements not available through your chosen certificate.

Important Limitations

BuildBox cannot guarantee successful compilation of every Swift project.

Projects requiring unavailable dependencies, private Apple frameworks or specialized build configurations may fail.

The app also cannot bypass every Apple signing restriction or guarantee that all injected tweaks will run.

If BuildBox is not compiling, signing or installing applications, try these simple checks.

BuildBox IPA Is Not Installing

Make sure you have downloaded the official unsigned IPA and are using a compatible signing method.

BuildBox Requires iOS 18

Version 2.1.0 requires iOS 18 or later. Install an earlier compatible version only if its developer documentation supports your firmware.

BuildBox Is Not Opening

The original IPA may not have been signed correctly, or its installation certificate may have expired.

GitHub Login Is Not Working

Check your GitHub account connection and internet access. Complete authentication through GitHub's official process.

Swift Compilation Is Not Starting

Make sure your GitHub account is connected and the required build repository has been created.

GitHub Actions Build Is Stuck

Open the Compile logs and check the build status in GitHub Actions.

A build may remain queued or fail because of GitHub Actions availability, repository permissions or compilation problems.

Swift Project Fails to Compile

The project may contain code errors, missing dependencies or unsupported build settings.

Copy the build log and review the reported failure.

IPA File Is Not Appearing After Compilation

Confirm that GitHub Actions completed successfully and generated the expected artifact.

Signing Certificate Is Missing

Open the certificate section and import your own valid .p12 certificate and matching .mobileprovision file.

P12 Password Is Incorrect

Make sure you are using the password associated with the imported certificate.

Provisioning Profile Is Invalid

Your profile may be expired, revoked or incompatible with the application identifier and requested entitlements.

BuildBox Signing Is Not Working

Check the signing log for the exact error. Verify the certificate, provisioning profile and IPA structure.

BuildBox Closes During Signing

Update to v2.1.0. The developer fixed a crash when signing applications from the catalog.

Signed App Installs but Does Not Open

Version 2.1.0 addresses a signing issue that caused some apps to install but fail at launch.

Install Button Is Disabled

BuildBox verifies the IPA's cryptographic signature before enabling installation.

An unsigned or incorrectly signed IPA may not pass the check.

IPA Installation Fails

Check that the certificate is valid for the device and that the application has compatible signing permissions.

App Source Is Not Loading

Verify the JSON source URL and check your internet connection.

ryP0 Catalog Is Missing

Update to BuildBox v2.1.0, where the ryP0 catalog appears in the redesigned Catalog tab.

Injected Dylib Causes an App Crash

The library may be incompatible with the selected application or depend on jailbreak-only components.

Remove the injection and test the original app first.

DEB Tweak Injection Is Not Working

Check whether the tweak includes all required dependencies and whether those components support a non-jailbroken environment.

Changing the Bundle ID Breaks Login

Some applications require their original bundle identifier for authentication, push notifications, app groups or keychain access.

Restore the original identifier when possible.

Large IPA Takes a Long Time to Sign

Signing speed depends on file size, storage performance and the amount of code or resources being processed.

BuildBox Stops Working After an iOS Update

Check the developer's latest release notes and GitHub issues for signing or installation changes.

Security Tips

Use official BuildBox releases and trusted source repositories.

Do not share your P12 certificate, certificate password, private keys or provisioning information with unknown services.

Only inject modifications into apps you own or are authorized to modify.