PojavLauncher on iOS was always a sideloaded app rather than an App Store download. The original iOS repository is now archived, so this page documents the legacy installation routes, certificate limits and common setup problems for people who still need that reference.
Key points
- There is no App Store listing. Every iOS install is a sideload signed with an Apple ID certificate.
- A free Apple ID gives a seven-day certificate; a paid developer account gives a year.
- Without JIT enabled the launcher still runs, but frame rates drop noticeably on every device.
- iPads handle it far better than iPhones because of screen size and sustained thermal headroom.
Why iOS installation is different
Apple does not allow general-purpose runtimes that execute downloaded code, which is exactly what a Java launcher does. The project therefore ships as an IPA that users install themselves rather than through the store. Everything downstream — certificates, JIT, expiry — follows from that single restriction.
Sideloading in plain terms
Sideloading means installing an app that Apple has not distributed. The app is signed with a developer certificate tied to an account, and iOS trusts it for as long as that certificate stays valid.
What JIT has to do with it
Java runs far faster when it can compile code as it goes, which iOS blocks for sideloaded apps by default. Without JIT the launcher still runs but performance drops noticeably. Enabling it usually requires a companion tool on a computer or a device-side method that varies by iOS version.
The main installation routes
Three broad approaches exist. None is objectively best; they trade convenience against how often you have to redo the work.
Free Apple ID signing
Using a free account with a desktop sideloading tool costs nothing but produces a certificate valid for seven days. After that the app refuses to open until you re-sign it. Practical if you already have a computer nearby, tedious otherwise.
Paid developer account
A paid Apple developer account extends the certificate to a year and removes the weekly ritual. It is the smoothest route for anyone who plays regularly, at the cost of the annual fee.
AltStore-style helpers
Helper apps automate re-signing over Wi-Fi so refreshes happen in the background. They still depend on a free or paid Apple ID underneath, so the same expiry rules apply — they just handle the paperwork.
- Seven day certificates need a refresh before they lapse
- Refreshing does not delete worlds or settings
- Enterprise certificate services get revoked frequently and are best avoided
Setting up after the app installs
Once the app opens, the flow closely mirrors Android: trust the profile, sign in, pick a runtime and download a version.
Trusting the developer profile
Open Settings, then General, then VPN and Device Management, and trust the profile that appears. Without this step the icon exists but the app closes instantly.
Account sign-in
Use the Microsoft account that owns Minecraft Java Edition. The same rule as everywhere else applies: the launcher authenticates, it does not license the game.
Choosing a version
Older releases behave better here than on Android because iOS devices are strong on single-core performance but constrained by the JIT situation. 1.12.2 and 1.16.5 remain the sensible defaults.
Realistic performance on iPhone and iPad
Apple silicon is fast, and with JIT enabled a recent iPad can hold a steady frame rate at moderate render distances. Without JIT, expect a playable but clearly slower experience with visible stutter when generating new chunks.
Where iPads pull ahead
Screen size and sustained thermal headroom matter more than raw benchmark numbers. An iPad with a keyboard and mouse gets remarkably close to a laptop experience.
Battery and heat
Sustained play warms the device quickly and drains battery faster than any native mobile game. Lower render distance and a frame cap help more than any other change.
Common iOS problems and fixes
Most iOS reports fall into a short list, and almost all of them are certificate or memory related rather than bugs in the launcher.
The app will not open after a few days
The certificate expired. Re-sign it with whichever tool you used originally. Your data stays in place.
Crashes when loading a world
iOS memory limits are strict. Reduce allocated memory rather than raising it, cut render distance and close background apps before launching.
Mods refuse to load
Check the mod loader matches the game version exactly. Our Forge and Fabric guide covers the version pairing rules that trip most people up.
Is the iOS route worth it?
If you own an iPad and already have a computer for signing, yes — the experience is genuinely good. If you are on an older iPhone with no easy signing route, the weekly maintenance wears thin quickly. Being honest about that up front saves a lot of frustration, and the safety guide explains which sideloading sources to avoid entirely.
Living with certificate expiry
The single biggest difference between the Android and iOS experience is not performance, it is maintenance. Planning for expiry rather than being surprised by it makes the platform far less frustrating.
Know which clock you are on
Note the date you signed the app. A free Apple ID gives seven days, a paid developer account gives a year. Refreshing a day early costs nothing; refreshing a day late means the app will not open when you want to play.
Refreshing does not delete your data
Re-signing replaces the signature, not the app's storage. Worlds, control layouts and downloaded versions survive. The exception is deleting and reinstalling, which does remove everything not backed up.
Avoid revoked certificate services
Services that sell installs on shared enterprise certificates get revoked in batches, often without warning, and the apps stop opening for everyone at once. A personal Apple ID is slower to set up and far more stable.
Download reminder: take the build from the project's own repository. The download section on our homepage links straight to it.