Where Does SideStore Keep Pairing and Logs?
SideStore refreshes on-device through VPN with a pairing file in Files, while the iloader helper keeps logs per OS. No fixed IPA library exists.
Last updated
SideStore moves refreshes onto the phone. A pairing file in Files plus on-device VPN with WireGuard replaces the desktop server AltStore needs. The iloader helper covers initial installs with per-OS logs.
IPA handling stays transient through system temp without a library folder. Model differences from AltStore run deep, from plugins to frameworks to refresh paths. Quote pairing plus logs and nothing more.
Where SideStore stores this, by platform
/var/mobile/Containers/Data/Application/<guid>/Documents
On-device pairing document visible through Files with wrapped variants nesting deeper. Refresh runs on-device after setup without desktop servers. Bundle ID verified through contributing docs.
%APPDATA%\me.nabdev.iloader\logs
Helper logs per OS for install traces with transient IPA staging through system temp. No fixed IPA library exists. User IPAs arrive per sideload through pickers.
Frequently asked questions
How do I pair SideStore?
Place the pairing file through iloader Manage next to the SideStore entry, visible in Files as the mobiledevicepairing document. On-device VPN plus WireGuard handles refreshes without a desktop server. Wrapped variants nest the path one level deeper.
SideStore or AltStore paths?
They invert the model. AltStore leans on AltServer with Mail plugins and Apple frameworks while SideStore refreshes on-device after iloader setup. AltServer install paths and anisette caches belong to the other workflow.
Where does iloader keep files?
Check the iloader logs folder per OS for install traces. Downloaded IPAs stage through system temp without a fixed library folder. User IPAs arrive through file pickers per sideload.
Notice an outdated path? Let us know.