Important Notice — Jailbroken Devices
GoodFeelings does not support jailbroken environments. Our software is designed exclusively for non-jailbroken (stock) iOS devices using sideloading methods.
If your device is jailbroken, you will encounter errors and we cannot provide support. This includes devices with Palera1n, Dopamine, unc0ver, checkra1n, or any other jailbreak.
Jailbreak environments modify system libraries and inject code into processes, which triggers our integrity verification system. These detections are by design and cannot be bypassed or disabled.
To use GoodFeelings, restore your device to stock iOS via iTunes/Finder and sideload the app using Sideloadly or AltStore.
When the app encounters a problem, it shows an error popup with a code. There are two types of error codes:
- GFC- — Client-side errors detected on your device
- GFS- — Server-side errors returned by our backend
Understanding Error Codes
Client error codes use the format GFC-XYYY where the first digit indicates the category:
- 1XXX — Startup Method Integrity (per-method detail)
- 2XXX — Session Token Verification
- 3XXX — Environment Detection
- 4XXX — Network Security
- 5XXX — Application Integrity
- 6XXX — Runtime Method Integrity (per-method detail)
- 7XXX — Runtime Session & Injection
- 0000 — Unknown / Unclassified
Startup Method Integrity (GFC-1XXX)
These errors occur during app startup when the security system verifies that each individual internal method hasn't been modified. The format is GFC-1GMM where G = module group and MM = method number within that group.
Group 1: Security Analysis (GFC-1101 — GFC-1109)
The core security analysis module has 9 internal functions. If any is compromised, the specific function is identified.
| Code | Failed Check | What to Do |
|---|---|---|
| GFC-1101 | Main security scan function integrity compromised. | The main security scan was disabled by external software. This indicates a component that specifically targets security checks. Disable any code modification or bypass software and restart. |
| GFC-1102 | Instrumentation scanner function integrity compromised. | The instrumentation detection was disabled. If you have Frida or similar analysis tools running, close them completely. Otherwise, a third-party component is disabling this check — remove it and restart. |
| GFC-1103 | Debug detection function integrity compromised. | The debugger detection was disabled. Disconnect any debugger. If none is attached, a third-party component is bypassing this check — remove it and restart. |
| GFC-1104 | System modification scanner function integrity compromised. | The system modification scanner was disabled. A third-party component is preventing the app from scanning for modifications. Remove recently installed tweaks or packages and restart. |
| GFC-1105 | Modification detection function integrity compromised. | The hook detection was disabled. Something is preventing the app from detecting modifications to its own code. Remove any bypass or modification software and restart. |
| GFC-1106 | Code signature verification function integrity compromised. | The code signature verifier was disabled. Something is preventing the app from verifying its own binary. This indicates active code modification — remove the responsible software and restart. |
| GFC-1107 | SSL bypass detection function integrity compromised. | The SSL bypass detector was disabled. If you're using SSL inspection tools (e.g., Charles Proxy, Surge), close them. Otherwise, a third-party component is disabling this check — remove it and restart. |
| GFC-1108 | Proxy detection function integrity compromised. | The proxy detector was disabled. Disconnect from any proxy. If you're not using one, a third-party component is disabling this check — remove it and restart. |
| GFC-1109 | VPN detection function integrity compromised. | The VPN detector was disabled. Disconnect your VPN. If you're not using one, a third-party component is disabling this check — remove it and restart. |
Group 2: Session Management (GFC-1201 — GFC-1205)
The authentication and session management module has 5 methods.
| Code | Failed Check | What to Do |
|---|---|---|
| GFC-1201 | Authentication status function integrity compromised. | The authentication check was disabled. Something is intercepting login verification — typically modification software trying to bypass license checks. Remove it and restart. |
| GFC-1202 | Welcome flow function integrity compromised. | A UI flow function was modified by external software. This is usually caused by a broad hook from a tweak or injected component. Remove recently installed tweaks and restart. |
| GFC-1203 | Key expiry check function integrity compromised. | The license expiry check was disabled. Something is trying to bypass license validation. Remove modification software and restart. |
| GFC-1204 | Heartbeat function integrity compromised. | The heartbeat function was disabled. Something is preventing the app from sending periodic security checks to the server. Remove modification software and restart. |
| GFC-1205 | Session invalidation function integrity compromised. | The session cleanup function was modified by external software. Remove recently installed tweaks or packages that modify other apps and restart. |
Group 3: Modification Detection (GFC-1301 — GFC-1303)
The modification detection module has 3 functions that detect various types of unauthorized changes.
| Code | Failed Check | What to Do |
|---|---|---|
| GFC-1301 | Critical function modification scanner integrity compromised. | The function hook scanner was itself disabled. A third-party component is trying to hide its own hooks from detection. Remove it and restart. |
| GFC-1302 | SSL pinning bypass scanner integrity compromised. | The SSL bypass scanner was disabled. Close any SSL interception tools. If none are running, a third-party component is hiding its SSL bypass — remove it and restart. |
| GFC-1303 | Symbol rebinding scanner integrity compromised. | The symbol rebinding scanner was disabled. A third-party component is hiding its function redirections from detection. Remove it and restart. |
Group 4: Instrumentation Detection (GFC-1401)
| Code | Failed Check | What to Do |
|---|---|---|
| GFC-1401 | Instrumentation tool scanner integrity compromised. | The instrumentation scanner was disabled. Close Frida, Objection, or any similar runtime analysis tool. If none are running, a third-party component is disabling detection — remove it and restart. |
Group 5: Debug Detection (GFC-1501)
| Code | Failed Check | What to Do |
|---|---|---|
| GFC-1501 | Debugger detection function integrity compromised. | The debugger scanner was disabled. Disconnect from any debugger (Xcode, LLDB, GDB). If none is attached, a third-party component is disabling debugger detection — remove it and restart. |
Group 6: Code Verification (GFC-1601)
| Code | Failed Check | What to Do |
|---|---|---|
| GFC-1601 | Code signature verification function integrity compromised. | The code verification function was disabled. Something is preventing the app from verifying its own binary integrity. This indicates active binary modification — download the original file from User Panel → My Products → Download. |
Group 7: Network Security (GFC-1701)
| Code | Failed Check | What to Do |
|---|---|---|
| GFC-1701 | SSL certificate validation handler integrity compromised. | The SSL certificate handler was disabled. Close any SSL/TLS interception or certificate override tools. If none are running, a third-party component is disabling SSL validation — remove it and restart. |
Group 8: Cryptography (GFC-1801 — GFC-1804)
The cryptographic operations module has 4 methods handling encryption and key derivation.
| Code | Failed Check | What to Do |
|---|---|---|
| GFC-1801 | Challenge-response computation function integrity compromised. | The authentication challenge handler was modified. This is a critical security violation — something is intercepting authentication. Remove ALL modification software immediately and download a clean copy from User Panel. |
| GFC-1802 | Session key derivation function integrity compromised. | The encryption key generator was modified. Something is trying to intercept your session keys. Remove ALL modification software and download a clean copy from User Panel. |
| GFC-1803 | Payload encryption function integrity compromised. | The data encryption function was modified. Something is intercepting outgoing encrypted data. Remove ALL modification software and download a clean copy from User Panel. |
| GFC-1804 | Payload decryption function integrity compromised. | The data decryption function was modified. Something is intercepting incoming encrypted data. Remove ALL modification software and download a clean copy from User Panel. |
Group 9: Device Verification (GFC-1901 — GFC-1902)
The device fingerprinting and response validation module has 2 methods.
| Code | Failed Check | What to Do |
|---|---|---|
| GFC-1901 | Device fingerprint generation function integrity compromised. | The device identification function was modified. Something is trying to spoof the device identity. Remove modification software and restart. |
| GFC-1902 | Server response validation function integrity compromised. | The server response validator was modified. Something is intercepting communication with our server. Remove modification software and download a clean copy from User Panel. |
Session Token Verification (GFC-2XXX)
These errors occur after login when the app verifies the session token was created and stored correctly.
| Code | Meaning | What to Do |
|---|---|---|
| GFC-2001 | Session was not established after authentication. | The login succeeded but the session wasn't saved. Restart the app and try logging in again. If this persists, a background process may be interfering with the app's memory. |
| GFC-2002 | Session data is corrupted. | The session data structure is invalid. This can happen if something modified the app's memory after login. Restart the app. If it persists, check for memory editing tools. |
| GFC-2003 | Session verification failed. | The session's integrity signature doesn't match. Something modified the session data after it was created. Restart the app. If it persists, remove software that modifies app memory. |
| GFC-2004 | Session security key error. | The internal security key was cleared from memory. Restart the app — a new key is generated on each launch. If it keeps happening, check for software that wipes app memory. |
| GFC-2005 | Session expired immediately after creation. | Your license may have just expired during login. Check your key status at goodfeelings.cc → User Panel → My Keys. |
| GFC-2006 | Session timestamp anomaly detected. | Your device's clock appears to be significantly incorrect. Go to Settings → General → Date & Time and enable "Set Automatically". |
| GFC-2007 | Session integrity constraint exceeded. | The session was created but the security environment is too compromised to continue. Close any software that modifies other apps, restart, and log in again. |
Environment Detection (GFC-3XXX)
These errors are triggered when the app detects software or conditions in the device environment that are incompatible with our security requirements.
| Code | Meaning | What to Do |
|---|---|---|
| GFC-3001 | Runtime instrumentation tools detected. | A runtime analysis framework (e.g., Frida, Objection, Cycript) was detected. Close it completely — including any background scripts or server processes — and restart the game. |
| GFC-3002 | Debug interface detected. | A debugger is attached to the app process. Disconnect it (Xcode → Debug → Detach, or kill the LLDB/GDB process) and restart the game. |
| GFC-3003 | Incompatible system modifications detected. | Incompatible jailbreak modifications were detected. Some tweaks interfere with our software. Try disabling tweaks for this app via iCleaner Pro or Choicy, then restart. |
| GFC-3004 | Post-launch component injection detected. | A third-party dynamic library was injected into the app after launch. Identify and remove the tweak or tool that injects into other apps (check recently installed packages), then restart. |
Network Security (GFC-4XXX)
These errors are triggered when the app detects that its network connection security has been compromised or intercepted.
| Code | Meaning | What to Do |
|---|---|---|
| GFC-4001 | Secure transport interception library detected. | An SSL/TLS interception library was detected on the device. Uninstall or disable SSL Kill Switch, ssl-kill-switch2, or similar certificate override tools and restart. |
| GFC-4002 | Connection security bypass detected. | The app's secure connection was intercepted at a system level. Disable any network modification tweaks or SSL bypass tools (e.g., FLEXing, SSLBypass) and restart. |
| GFC-4003 | Traffic inspection proxy detected. | An HTTP/HTTPS proxy is configured on your device. Disconnect from Charles Proxy, Surge, mitmproxy, Proxyman, Fiddler, Burp Suite, or any similar tool. If this is a corporate or school proxy, switch to a different network. |
| GFC-4004 | Network tunnel interface detected. | A VPN connection is active. Disconnect your VPN and use a regular Wi-Fi or cellular connection. VPN tunnels interfere with network security verification. |
Application Integrity (GFC-5XXX)
These errors indicate that the app's code or internal structure has been modified since it was built.
| Code | Meaning | What to Do |
|---|---|---|
| GFC-5001 | Application function modification detected. | Critical app functions have been redirected to external code. A third-party component is intercepting internal function calls. Identify and remove the injecting software (check installed tweaks/packages) and restart. |
| GFC-5002 | Binary verification failed. | The app binary has been physically modified since it was built. Do not modify the .ipa or .deb file. Download the original unmodified file from User Panel → My Products → Download and install it. |
| GFC-5003 | Method consistency check failed. | Internal methods have been replaced or swizzled by external code. This is caused by software that patches the app's behavior at runtime. Remove it and restart. |
| GFC-5004 | Runtime symbol redirection detected. | The app's function dispatch table has been modified (GOT/PLT rebinding). A third-party component is redirecting internal function calls. Remove it and restart. |
Runtime Monitoring (GFC-6XXX / GFC-7XXX)
These errors occur during gameplay when the app's periodic health checks detect that something has changed since the app started.
Runtime Method Integrity (GFC-6XXX)
Same per-method codes as startup (GFC-1XXX), but detected during gameplay. The format is GFC-6GMM mirroring the startup codes. This means the method was intact at launch but was compromised while the app was running.
| Code | Meaning | What to Do |
|---|---|---|
| GFC-6101 — GFC-6109 | Security Analysis method modified during runtime (see GFC-1101—1109 for specific method). | A security function was compromised while the app was running. Something began modifying the app mid-session. Close any recently launched tools or background apps that modify other processes, and restart. |
| GFC-6201 — GFC-6205 | Session Management method modified during runtime (see GFC-1201—1205). | An authentication function was modified during gameplay. A background process started interfering with the app's code. Close background apps, remove interfering software, and restart. |
| GFC-6301 — GFC-6303 | Modification Detection method compromised during runtime (see GFC-1301—1303). | A protection scanner was disabled during gameplay. Something actively disabled a detection mechanism mid-session. Remove the responsible software and restart. |
| GFC-6401 | Instrumentation scanner modified during runtime. | The instrumentation scanner was disabled during gameplay. A runtime analysis tool was launched after the app started. Close it and restart. |
| GFC-6501 | Debugger scanner modified during runtime. | The debugger scanner was disabled during gameplay. A debugger was attached after launch. Detach it and restart. |
| GFC-6601 | Code verification function modified during runtime. | The code verifier was disabled during gameplay. Something modified app code mid-session. Remove the responsible software and download a clean copy from User Panel. |
| GFC-6701 | SSL handler modified during runtime. | The SSL handler was modified during gameplay. A network interception tool was activated mid-session. Disable it and restart. |
| GFC-6801 — GFC-6804 | Cryptographic method modified during runtime (see GFC-1801—1804). | Critical — a cryptographic function was modified during gameplay. Something began intercepting encrypted communication mid-session. Remove ALL modification software immediately and download a clean copy from User Panel. |
| GFC-6901 — GFC-6902 | Device verification method modified during runtime (see GFC-1901—1902). | A device verification function was modified during gameplay. Something started spoofing device information mid-session. Remove the responsible software and restart. |
Runtime Session & Injection (GFC-7XXX)
| Code | Meaning | What to Do |
|---|---|---|
| GFC-7001 | Session token not found during runtime check. | The session token disappeared during gameplay. This can happen if the system cleared the app's memory under pressure, or if something wiped it. Restart the app and log in again. |
| GFC-7002 | Session data corrupted during runtime. | The session data was corrupted during gameplay. Something modified the app's memory while running. Restart the app. If it persists, check for memory editing or game modification tools. |
| GFC-7003 | Session verification failed during runtime. | The session's integrity signature failed during a periodic check. The session data was modified in memory. Restart the app. If it persists, remove software that modifies app memory. |
| GFC-7004 | Session security key lost during runtime. | The security key was cleared from memory during gameplay. Restart the app — a new key is generated on each launch. If it keeps happening, check for software that wipes app memory. |
| GFC-7005 | Session expired during gameplay. | Your license expired while you were playing. Purchase a new key at goodfeelings.cc → User Panel. |
| GFC-7006 | Session timestamp anomaly during runtime. | The device clock changed significantly during gameplay. Enable "Set Automatically" in Settings → General → Date & Time. |
| GFC-7007 | Session integrity constraint exceeded during runtime. | The security environment degraded below the required level during gameplay. A new threat was detected mid-session. Close any recently launched software that modifies other apps and restart. |
| GFC-7100 | Runtime injection detected during gameplay. | A new dynamic library was injected into the app while it was running. Something loaded code into the process mid-session. Identify the recently launched software that injects into other apps, remove it, and restart. |
Unknown / Fallback
| Code | Meaning | What to Do |
|---|---|---|
| GFC-0000 | Unclassified error. | The error source could not be determined. Restart the app and try again. If recurring, open a support ticket with the error code. |
Server Error Codes (GFS-)
These errors are returned by our backend when it detects a problem during authentication or session validation. They appear alongside an error message in the app.
| Code | Meaning | What to Do |
|---|---|---|
| GFS-1001 | Authentication challenge verification failed. | The secure handshake with our server failed. Restart the app and try again. If repeated, check your internet connection or try a different network. |
| GFS-1002 | Encrypted payload could not be verified. | The server could not decrypt the authentication data. This may indicate network interference. Disable any VPN or proxy and try again. If the problem persists, re-sideload the app. |
| GFS-1003 | Device fingerprint mismatch. | Your device information doesn't match what's on file. If you recently restored or reset your device, re-enroll it at goodfeelings.cc → User Panel → Devices. |
| GFS-1004 | Integrity violation detected by server. | The server detected that the app has been tampered with. Re-sideload a clean copy from User Panel → My Products → Download. Do not use modified files. |
| GFS-1005 | Binary hash mismatch detected by server. | The server detected that the app binary has changed since your last session. This usually means the binary was patched or modified. Re-sideload the original file. |
| GFS-1006 | Internal server error. | Something went wrong on our end. Wait a few minutes and try again. If this keeps happening, open a support ticket in our Discord server. |
| GFS-1007 | Device not linked to this key. | This key is not linked to your current device. Re-authenticate to link this device, or check that you're using the correct key. |
Login Error Messages
During login, the app may show plain text error messages instead of error codes. These are simple, self-explanatory messages from the server:
| Message | Meaning | What to Do |
|---|---|---|
| Invalid license key | The key you entered does not exist. | Double-check your key for typos. It should be in the format XXXXX-XXXXX-XXXXX-XXXXX. Keys are case-sensitive. |
| This key is for a different product | Your key is valid but for a different game. | Make sure you're using the correct key for this specific game. Check your keys at goodfeelings.cc → User Panel → My Keys. |
| This key is bound to a different device | Your key is permanently linked to another device. | Each key is bound to one device permanently. You need a new key for this device. Device binding happens on first activation and cannot be changed. |
| Your license has expired | The key's time period has ended. | Purchase a new key. You can check expiry dates at goodfeelings.cc → User Panel → My Keys. |
| This key has been disabled | The key has been banned, revoked, or suspended. | Contact support via a ticket in our Discord server if you believe this is an error. |
| Game updated to X.X — cheat supports Y.Y | The game has updated and our software has not caught up yet. | Wait for an update from us. Check the announcements channel in our Discord server for update status. |
| Too many attempts | You've been rate-limited. | Wait a few minutes before trying again. |
ℹ️ Not jailbroken but still getting errors?
If your device is not jailbroken and you are experiencing errors from this list, it may be a bug in our software client. Please open a support ticket in our Discord server and include: the error code, your device model, iOS version, and the game version. Our team will investigate.
If your device is not jailbroken and you are experiencing errors from this list, it may be a bug in our software client. Please open a support ticket in our Discord server and include: the error code, your device model, iOS version, and the game version. Our team will investigate.
Still Having Issues?
- Restart the app — Most errors are resolved by a fresh launch
- Re-sideload — Download a fresh copy from goodfeelings.cc → User Panel → My Products → Download
- Check your environment — Disable VPNs, proxies, and any software that modifies other apps
- Check your clock — Ensure "Set Automatically" is enabled in Date & Time settings
- Re-enroll your device — If you're having device issues, go to User Panel → Devices
- Contact support — Open a ticket in our Discord server and include the error code