A simple StosSign wrapper app that allows you to enable "Increased Memory Limit" for your sideloaded apps without using Xcode.
This fork defaults to the following SideStore configuration:
Client Info: <PC> <Windows;6.2(0,0);9200> <com.apple.AuthKit/1 (com.apple.iTunes/12.12.4.1)>
User Agent: akd/1.0 CFNetwork/808.1.4
Both values are editable and saved under Settings → Authentication. They apply to anisette provisioning, GrandSlam sign-in (including the app-token request), and trusted-device/SMS two-factor requests. Changes take effect on the next sign-in. The server URL is also reread on each sign-in. Developer Services retains StosSign's existing Xcode user agent.
The pinned StosSign patch adds an optional user-agent override and retains the original defaults for other clients. The capability request still targets INCREASED_MEMORY_LIMIT. Authentication diagnostics omit raw anisette secrets, and generated timestamps use UTC.
Version 1.1 handles Apple's automatically pushed 2FA challenge (hsc=409 with missing or empty au), following SideSign's fix. Previously this response was mistaken for completed authentication, so the developer-token request could fail with -22411 before code entry. The app now waits for the code already sent, skips requesting a replacement, refreshes anisette before trusted-device validation and reauthentication, and limits the flow to one 2FA retry. The AltSign implementation discussion documents the same failure sequence. Genuine -22411 errors are still errors; the app only takes this path when the password response identifies a challenge.
Version 1.2 refreshes anisette before listing App IDs and updating a capability, prevents overlapping capability requests, and replaces the stale AppID(...entitlements: []) debug dump with an explicit result. That empty list was initialized locally and never populated by the PATCH response; it did not prove that Apple rejected or accepted the entitlement. Apple JSON:API errors now retain their HTTP status, error code, title, and detail. An empty successful HTTP 204 is accepted, while an empty HTTP 200, malformed response, or missing resource remains unconfirmed. The JSON:API Accept header now matches AltSign's capability request. No automatic retries or additional capability writes are performed.
Twelve offline tests cover authentication and capability requests, including 200/204 responses, 403 HTML, JSON:API rejection details, malformed data, and missing resources. Device testing confirmed Apple sign-in, completion of the capability request, and Increased Memory Limit in the regenerated Apple provisioning profile. Inspection of the exported signed LiveContainer IPA found the entitlement missing from both the main executable and LiveProcess executable signatures despite its presence in their profiles. End-to-end MeloNX operation therefore remains unverified and blocked by the separate signing issue. A successful capability request does not prove that the final executable signature includes the entitlement or that the running process receives a higher memory limit. See GetMoreRam #35, #36, and SideStore #1616 (related, but describes a missing profile entitlement rather than a missing executable entitlement).
- Download
GetMoreRam-WindowsAuth.ipafrom this fork's Releases. Each build is also available as an Actions artifact. - Install the IPA through SideStore using the Apple ID that owns LiveContainer's App ID.
- Open GetMoreRam → Settings. The Windows / iTunes values above are already filled in. Confirm the anisette server matches your working server, then tap Sign in and complete two-factor verification.
- Open App IDs, tap Refresh, and select LiveContainer's exact App ID.
- Tap Add Increased Memory Limit.
- Refresh/re-sign LiveContainer in SideStore so its new provisioning profile contains the capability. If reinstalling is necessary, back up its containers and app data first.
- Re-enable JIT using your working StikDebug connection and test the emulator.
The IPA is unsigned; SideStore signs it during installation. This setting requests a higher memory limit and does not add physical RAM or guarantee a specific limit. Each installation still needs verification of the profile, executable signature, and resulting runtime behavior. No Apple credentials are required for builds.
The existing Import SideStore Account option remains available for SideStore's exported account JSON. It imports credentials and provisioning identity; it does not import .sideconf settings.
The GitHub Actions workflow creates an unsigned arm64 archive, packages the IPA, uploads an artifact with its SHA-256 checksum, and publishes a release on pushes to main.
For a local build with Xcode installed:
xcodebuild archive -project GetMoreRam.xcodeproj -scheme GetMoreRam \
-configuration Release -destination 'generic/platform=iOS' \
-archivePath build/GetMoreRam.xcarchive \
CODE_SIGN_IDENTITY='' CODE_SIGNING_REQUIRED=NO CODE_SIGNING_ALLOWED=NO
mkdir -p build/ipa/Payload dist
cp -R build/GetMoreRam.xcarchive/Products/Applications/GetMoreRam.app build/ipa/Payload/
ditto -c -k --norsrc --keepParent build/ipa/Payload dist/GetMoreRam-WindowsAuth.ipa- SideStore's anisette configuration resolves editable client-info and user-agent headers. This fork follows that approach with the supplied defaults.
- iLoader's sign-in delegates authentication and remote-v3 anisette to the Rust
isideloadlibrary. Replacing this Swift app's authentication stack with that Rust stack is a larger change; the header patch keeps GetMoreRam's existing sign-in, two-factor, account import, and capability APIs.
Request-construction tests in the StosSign fork verify the headers for GrandSlam init, completion, app tokens, and both two-factor flows. Configuration validation can be checked locally:
swiftc GetMoreRam/AuthenticationConfiguration.swift Tests/AuthenticationConfiguration/main.swift -o /tmp/getmoreram-configuration-tests
/tmp/getmoreram-configuration-tests- Sideload this app
- Go to settings, sign in your account that you used to sign the app you want to enable "Increased Memory Limit"
- Go to "App IDs" page
- Tap Refresh
- Tap the app you want to enable "Increased Memory Limit"
- Tap "Add Increased Memory Limit"
- Reinstall the app from SideStore/AltStore
- Check if you have "Increased Memory Limit"
Stossy11 - For StosSign. SideStore - Anisette Data fetching codes are stolen from SideStore