nab138

[GUIDE] SideStore as an Alternative to AltStore + Fix for Error -80046 If AltStore is currently not working for you and you’re looking for an alternative, SideStore is worth trying. SideStore is a community-developed fork of AltStore that lets you sideload IPA files without needing a computer every time you install or refresh apps. 1. What do you need? Before starting, make sure you have: -An iPhone or iPad running iOS/iPadOS 15.0 or later, with a passcode enabled. -A computer running Windows, macOS, or Linux (required for the initial setup). -An Apple ID / Apple Account. -A Wi-Fi connection. -LocalDevVPN, the VPN app required by SideStore. -iLoader, the computer tool used to install SideStore and manage pairing files. -A USB cable to connect your iPhone to your computer. Official links: SideStore documentation: docs.sidestore.io iLoader downloads: github.com/nab138/iloader/releases/latest LocalDevVPN: apps.apple.com (search for “LocalDevVPN”) 2. How to install SideStore Step 1 — Install the required software 1. Install LocalDevVPN on your iPhone. 2. Download and install iLoader on your computer from its official GitHub releases page. 3. On Windows, install iTunes if required for device communication. 4. Open LocalDevVPN and allow the VPN configuration when iOS asks for permission. Step 2 — Install SideStore using iLoader 1. Connect your iPhone to your computer using a USB cable. 2. Unlock your iPhone and tap Trust This Computer if prompted. 3. Open iLoader. 4. Sign in with your Apple Account. 5. Select your connected device. 6. Choose Install SideStore (Stable) and wait for the installation to finish. Step 3 — Trust the developer certificate On your iPhone: 1. Open Settings → General → VPN & Device Management. 2. Select the developer profile associated with your Apple Account. 3. Tap Trust and confirm. 4. If required by your iOS version, enable Developer Mode under Settings → Privacy & Security, then restart your device. Step 4 — Complete the setup 1. Open LocalDevVPN and tap Connect. 2. Open SideStore. 3. Sign in using the same Apple Account you used in iLoader. 4. Open My Apps. 5. Tap the 7 DAYS counter next to SideStore to refresh it and complete the initial setup. Keep LocalDevVPN connected whenever you install, update, or refresh apps through SideStore. You generally won’t need your computer for routine refreshes. 3. Fix for SideStore login error -80046 If SideStore gives you error -80046 when logging in, the following workaround has been reported by a user experiencing the same issue. It is not guaranteed to work for every version. 1. Open Settings → User Customizations. 2. Disable On-Device Anisette. 3. Go to Settings → Anisette Servers. 4. Select SideStore (New) (new.ani.sidestore.io). 5. Disable Enable Auto Rotation. 6. Go back to User Customizations → Anisette Client Configuration. 7. Under Remote Server Sync, tap Fetch, then Save as Overrides. If a separate Save Overrides option appears, use it as well. 8. Return to User Customizations and tap Reset adi.pb. 9. Try signing in again with your Apple Account. If the options have different names or are missing, check your SideStore version before changing other settings. 4. What if Health Check says DDI is not mounted? You might also see this message: Mount(protocol: rppairing, reason: dmg=false started=false) Or: Developer Disk Image (DDI): Not Mounted (JIT unavailable) This is related to mounting the Developer Disk Image and JIT functionality. It does not automatically mean that your Apple Account login is failing for the same reason. First, make sure your VPN and pairing file are working correctly. If necessary, follow the official pairing-file guide: docs.sidestore.io Official documentation * Installation: docs.sidestore.io * Troubleshooting: docs.sidestore.io * Pairing file: docs.sidestore.io Important: The login workaround is community-reported, not an officially guaranteed fix. Please comment below if it works for you, including your iOS and SideStore versions, so other users can compare results.

Managing iPhone IPA installs and renewals from Windows and Discord I wanted my IPA files, Apple account assignments, and renewal status in one place. That became iPhone IPA Manager, an open-source Windows application with an optional private Discord bot. This walkthrough covers the basic workflow and its limits. It is a public community preview, not a way around Apple's provisioning restrictions. *Disclosure: AI tools assisted with development of this project and preparation of this article. Screenshots show the actual application with sample data.* !IPA Manager overview with sample data Start with USB, not remote access The easiest starting point is Windows 11 x64, Apple's device software, an unlocked iPhone, a USB cable, an Apple account, and an IPA you are entitled to install. 1. Download the installer or portable build from the official releases. 2. Connect the iPhone over USB and approve Trust This Computer on the phone. 3. In Connections, choose Pair connected iPhone. 4. Choose your IPA folder, add your Apple account, complete verification, and assign the IPA. Save the settings. 5. Run Check setup, then Install apps. The standalone build does not require Python. The application runs as a normal Windows user; installing Apple device software or the optional Wi-Fi bridge service is a separate administrator task. Keep assignments explicit Each account has one assigned IPA. When a new version arrives, select the new file and save the assignment. Future installs and renewals use that saved choice. !Sample account assignments Any file-transfer tool can place completed IPAs in the configured folder. The app does not depend on a particular transfer service and does not supply IPA files. Its account slots do not increase Apple's allowed number of apps or devices. Installation and refresh are different jobs A full installation signs and transfers the assigned IPA. A refresh tries to renew the provisioning profile, avoiding a full application transfer where supported. Known profile expiry or rejection, or a pending IPA change, can trigger a full installation fallback. An ambiguous connection failure is not a reason to blindly repeat an install: the job can stop for inspection instead. This distinction matters particularly on a slower connection. It does not imply a fixed speed improvement; performance depends on the connection and the job. Add Discord after the first installation works The optional bot runs on the Windows PC. Configure your own bot token locally, along with the allowed user, server, and channel. Commands from other users or destinations are rejected. Useful commands include: | Command | Purpose | | --- | --- | | /accounts | See account numbers and assignments | | /files | Browse the managed IPA folder | | /inbox | Choose an account and file, save the assignment, and install it | | /sideload | Fully install all assigned apps or a selected account | | /refresh | Renew assigned apps, using the documented fallback when needed | | /status | Check the running version, connection, and progress | | /queue | Queue work until a usable connection is available | | /stop | Request safe cancellation | Account and file choices support autocomplete. The desktop and bot share saved assignments, so changing a file through Discord also affects subsequent renewal. The bot is a remote control for the PC, not a cloud installation service. Prefer the desktop for Apple credential entry. Optional Discord sign-in forms are processed by Discord and are not end-to-end encrypted. What happens when a scheduled refresh is missed? Automatic renewal is opt-in. Its six-day schedule is checked at Windows sign-in and every 15 minutes. If the PC was off, overdue work waits for a usable connection. Turning on the PC without signing into the owning Windows user is not enough. The PC must be awake, the assigned file must remain available, and the phone must offer a supported authenticated connection. Scheduling cannot guarantee an app will stay available indefinitely. Remote access has real limits After USB works, local Wi-Fi is the next step. The manager prefers an authenticated local route when one is available. Tailscale can provide an experimental remote route, but the tunnel needs to be prepared on home Wi-Fi before leaving. A VPN cannot make iOS expose a service that has stopped listening. Remote cold starts and uninterrupted roaming are not guaranteed. Mobile transfer speed also depends on home upload speed, mobile signal, latency, and relay use. Try it and report the rough edges The current public build is an unsigned community preview. For support, use the redacted diagnostics and avoid publishing credentials, account details, or pairing records. Feedback on first-run setup across different Windows/iPhone combinations is particularly useful. - Website and screenshots - Official releases - Source code and issue tracker - Connection guide The project is GPL-3.0-or-later. Its native signing integration derives from iloader, by nab138 and contributors. JAS, by jkcoxson and contributors, inspired the profile-renewal and IP-device research; no JAS code was copied. The repository's NOTICE credits the wider dependency community.

Added an optional fix to my Impactor Windows fork I added an optional compatibility mode to my Impactor fork to help with Apple ID sign-in errors. It uses updated anisette servers and matching authentication information. Credit to the iLoader developers for the workaround! To enable it, go to Settings → Authentication mode → iLoader compatibility - Jkcoxson. SideStore and StikStore servers are also available as alternatives. Standard mode remains the default. GitHub It worked for me—hopefully it helps others having similar login issues.

🔥 [FIX] SideStore -80045 / 503 Login Errors — Tested & Working on iOS 27! 🔥 SideStore -80045 / 503 Login Error Fix — Tested & Working! Hey everyone! 👋 After dealing with multiple SideStore errors, including -80045, 503 Service Temporarily Unavailable, and Incorrect Password, I finally managed to get Apple Account sign-in working again. I tested the following steps myself, so I'm sharing what worked for me. I also included a separate troubleshooting section for signing certificate errors. ✅ Part 1 — Fix Apple Account Sign-In ⚙️ Step 1: Update Anisette Configuration Open SideStore and navigate to: Settings → User Customizations → Anisette Client Configuration Replace the existing values with the following: Client Info <PC> <Windows;6.2(0,0);9200> <com.apple.AuthKit/1 (com.apple.iTunes/12.12.4.1)> User Agent / Browser Agent akd/1.0 CFNetwork/808.1.4 Save your changes, completely close SideStore, and reopen it. 🔄 Step 2: Reset On-Device Anisette ⚠️ IMPORTANT: This is the step I performed immediately before my sign-in succeeded. Go to: Settings → User Customizations 1. Turn OFF On-Device Anisette. 2. When the reset confirmation appears, tap Reset. 3. Reopen the settings. 4. Turn ON On-Device Anisette. 5. When prompted again, tap Reset. 6. Verify that On-Device Anisette is ON. Now try signing in with your Apple Account. 🎉 Result: SUCCESS! After following these steps, I was finally able to sign in successfully! ✅ Apple Account sign-in working ✅ No more -80045 during successful login ✅ No more 503 during successful login ✅ On-Device Anisette enabled The exact root cause is still unclear, but this combination of settings worked on my device. 🛠️ Part 2 — Troubleshooting Signing Certificate Errors After fixing the login issue, I also encountered errors when refreshing or resigning sideloaded apps. Error messages: SideStore.OperationError 8 Could not locate signing certificate MinimuxerError 36 0xe8008015 If you're experiencing these issues, here's a possible recovery method. 🔐 Step 1: Revoke Existing Certificates 1. Open SideStore. 2. Navigate to Settings → Certificate Management. 3. Revoke all certificates listed there. ⚠️ Warning: Revoking certificates can invalidate existing sideloaded apps. Back up important app data before proceeding. 💻 Step 2: Reinstall Using iLoader Download the latest official version of iLoader: 📥 Official iLoader Downloads - GitHub (Latest Stable): github.com/nab138/iloader/releases/latest - GitHub (All Releases): github.com/nab138/iloader/releases - Official Website: iloader.app Then: 1. Connect your iPhone to your PC. 2. Open iLoader. 3. Reinstall SideStore using iLoader. 4. Allow iLoader to generate a new signing certificate. 5. Open SideStore and sign in again if necessary. 🔁 Step 3: Refresh Your Apps Once SideStore is installed: 1. Enable the required VPN connection. 2. Open My Apps in SideStore. 3. Refresh SideStore first. 4. Refresh your other sideloaded apps. If refreshing fails, try resigning the affected app. ⚠️ Note: This certificate recovery procedure is additional troubleshooting guidance. Unlike the Apple Account login fix, I haven't confirmed that it fully resolves the signing errors yet. 📱 My Test Environment |Component|Version| |:-|:-| |iOS|27.0| |SideStore|0.7.0 Nightly (20261017.511)| |LiveContainer|3.8.11| |PC|Windows| |Installer|iLoader| |On-Device Anisette|Enabled| 💡 Quick Summary Having -80045, 503, or incorrect password errors? ➡️ Update Anisette Client Configuration. ➡️ Turn On-Device Anisette OFF → Reset. ➡️ Turn it back ON → Reset again. ➡️ Sign in to your Apple Account. Having signing certificate errors? ➡️ Back up your sideloaded app data. ➡️ Revoke existing certificates in Certificate Management. ➡️ Reinstall SideStore using iLoader. ➡️ Try refreshing or resigning your apps. ❤️ Final Notes This isn't an official SideStore fix. It's a workaround that successfully resolved the login issue on my device. I can't guarantee it will work for everyone, especially across different SideStore versions. If this helped you, please share your iOS version, SideStore version, and results in the comments. Hopefully this saves someone else a few hours of troubleshooting! 🔥 #SideStore #Sideloadi

これについて重要なお話です 現在確認サイドストアのリポジトリにもissueが飛び交っています 私の修正を適用するより公式の修正を待つのが確実です… また、iloaderでは最新バージョンにて修正が適用されていてログインできます！🔥⬇️ github.com/nab138/iloader/releases/tag/v2.3.9 #80045bug #iloader #sidestore