FAQ & Troubleshooting
The common questions and fixes. Still stuck? Reach out on Discord or email support.
You'll need to provide your own GameCube (ISO) and Wii (WBFS/ISO) game files. These can be imported through the built-in Wi-Fi web server (see Importing Games), iTunes file sharing, cloud storage, or other file management apps. Make sure you own the original games before using ROM files.
iCube is distributed via sideloading for iOS/iPadOS and tvOS. We recommend using SideStore to install the app on your iOS/iPadOS device. To install on your tvOS device, use Sideloadly. To enable JIT on iOS/iPadOS, we recommend using StikDebug — see the JIT & Performance guide. JIT is only available on the sideloaded builds, never on TestFlight or the App Store.
iCube supports MFi (Made for iPhone) controllers, PlayStation DualShock 4, PlayStation DualSense, Xbox Wireless Controllers, and the Siri Remote on Apple TV. Touch controls are also available on iPhone and iPad. See the Controllers page for details.
iCube requires iOS/iPadOS 16.0 or later for iPhone and iPad, and tvOS 17.0 or later for Apple TV. For optimal JIT-less performance, we recommend newer devices like iPhone 16 or later, iPad (7th generation) or later, and Apple TV 4K (4th generation).
Yes! iCube supports both in-game saves (like the original consoles) and save states, which allow you to save and load your progress at any point during gameplay. All saves are stored locally on your device.
While iCube has high compatibility, some games may have issues due to their complexity or specific hardware requirements. We're constantly working to improve compatibility through regular updates.
Yes, on the sideloaded builds. iOS 26's Trusted Execution Monitor requires a debugger to authorize each page of JIT memory before it will run, and iCube now performs that handshake at startup when StikDebug (or any attached debugger) is present. TestFlight and App Store builds cannot do this at all, because Apple does not permit the required entitlement there; they always run the Cached Interpreter. See the JIT & Performance guide.
The single biggest win is turning on JIT, which is several times faster than the interpreter — see the JIT & Performance guide. Beyond that, try reducing the internal resolution, disabling enhanced features like anti-aliasing, closing other apps, and ensuring your device isn't overheating. Performance varies based on the game and your device's capabilities.
Only for the GameCube Main Menu itself, or when the “Load GameCube Main Menu” setting is on. Most games run without it. See GameCube BIOS (IPL) for how to dump and install your own.
iCube has a built-in web server with a Web UI and a WebDAV address. See Importing Games for step-by-step instructions.