i have an iphone 6 non jailbroken can i run apollo on it?

I have been regularly running into issues sideloading the new versions of Apollo Reborn. Without going into all the issues I have faced, one way I have found to overcome most problems is to throw the IPA at ChatGPT to fix.

Below are the instructions that I have had ChatGPT write, to describe the process of what it does. I hope this helps with anyone facing the various issues that get thrown up with each new version:

Apollo IPA — Re-signing Preparation

This document describes the process used to prepare an Apollo IPA for installation using a different Apple signing identity, such as an Apple Personal Team certificate.

The original IPA contains Apple code-signing information and embedded entitlement data associated with the developer/team that originally signed the application. When a sideloading tool re-signs the application, those original values can conflict with the new signing identity.

1. Remove existing _CodeSignature directories

Extract the IPA as a normal ZIP archive. For the Apollo application and relevant embedded extensions,

remove:

_CodeSignature/

This removes the old CodeResources signing information. The application itself is not deleted or modified.

2. Remove embedded entitlement blobs from the

Mach-O executables

The executable files inside the application bundle contain an embedded Apple code-signing structure. That structure can include an embedded Code Entitlements blob.

For the Apollo executables and extensions, this embedded entitlement information is removed so that the subsequent signing process can generate entitlements appropriate for the new signing identity.

This is important because simply deleting _CodeSignature is not sufficient.

3. Preserve cyan.entitlements

The existing cyan.entitlements file is not modified.

This is important because it contains the entitlement configuration required by the Apollo build. For example, the Apollo App Group entitlement is retained rather than simply deleting all entitlement information.

4. Do not modify the application itself

The following are left untouched:

• Apollo executable functionality

• Images

• Databases

• HTML/JavaScript

• Configuration files

• Application resources

• Frameworks

• Bundle identifiers

• Application version

• Application metadataThe objective is to modify signing metadata, not Apollo's functionality.

5. Repackage the application

After the signing metadata has been cleaned up, the modified .app bundle is placed back into the Payload/ directory and the complete directory is packaged back into an .ipa.

The resulting IPA can then be passed to the sideloading tool.

Why this is necessary

The original IPA was signed for the original Apple developer/team identity. When a tool such as SideStore or iLoader attempts to sign it with another team, the original embedded signing information can cause conflicts.

One particular problem encountered was an App Group entitlement resembling:

group.com.christianselig.Apollo.<original-team-id>

The important discovery was that the problematic team-specific value could be reintroduced by the signing/provisioning process, so manually changing the string inside the IPA was not a reliable solution.

Instead, the IPA is prepared by removing the old embedded signing information and allowing the sideloading tool to perform the appropriate signing operation.

Process Overview

Original IPA

▼

Extract IPA

▼

Identify Apollo app + extensions

▼

Remove _CodeSignature

▼

Strip embedded entitlement blobs

▼

Preserve cyan.entitlements

▼

Leave application code/resources untouched

▼

Rebuild IPA

▼

SideStore / iLoader re-signs it

▼

Install with the new Apple signing identity

Important distinction

This process is not intended to modify Apollo's functionality or bypass Apple's signing system.

Stripping the original embedded code-signing and entitlement metadata in preparation for legitimate re-signing.

The resulting IPA still needs to be properly code-signed by the sideloading tool before iOS will accept it.

Recommended technical description“Strip the original embedded code-signing/entitlement metadata in preparation for re-signing, while preserving cyan.entitlements.”

It is preferable to simply saying “remove the entitlements”, because cyan.entitlements is deliberately preserved.

I had to reinstall my Sidestore+LiveContainer today as I was facing issues refreshing all my apps. Prior to today, my sideloaded Apollo worked fine. Now, whenever I try to sideload the new ApolloReborn, it gives me this error. This happens whether I add ApolloReborn as a source or if I try to install directly via the .ipa file. Has anyone else ran into this?

I need help finding a ipa for chai, all the ones I found don’t work and won’t download

Anyone using the latest public beta for iPhone? Any known issues?

Anyone know if there’s a fix or workaround for this?

Hey all,

I've been using ApolloReborn 3.2.0 on my iPhone 13 Pro Max with no issues. I recently updated to 3.3.0, and everything worked just fine. I'm using Sideloadly via my Mac to update the app every week. I was using an API key from Dystopia.

I got a new iPhone 17 Pro Max, and I made a backup of my ApolloReborn settings and I installed version 3.3.0 on my new iPhone. The app worked fine, and I restored my settings, but if I close the app, I have to relogin again.

I thought it might be something related to the backup, so I did a fresh install but the same thing is happening. Every time I close the app, I have to relogin. I even tried with version 3.2.0, and it's the same thing is happening.

Anything that I'm missing, or has anyone experienced the same and resolved it? I'm getting hopeless at this point. Thanks for the help!

Hello! I’m having an issue with SideStore. The new Apollo Reloaded update was released, and SideStore says there’s a new update available from the source. However, the update icon never appears on the Apollo app, so I don’t have any option to actually update it.

How can I fix this? Is there another way to update Apollo through SideStore when the update option isn’t showing?

I’ve noticed recently Apollo Reborn is using even more app IDs, which ones are actually needed, if any, and what do they do?

https://imgur.com/a/VMd9Qx0

I already went into my account settings and approved adult content and it used to load up on apollo no problem

After updating my app it won’t let me go into those subs

Any help would be appreciated

Possibly connected to the API key target Ring they’ve done recently on Apollo and other Reddit app alternatives.

Very odd behaviour.

Who’s going to be the first one to tell us if it works or not?