Jailbroken iOS devices (Pro)
Goal: You will learn how to notice when your iOS app is running on a jailbroken device.
The problem
A normal iPhone or iPad keeps your app inside Apple's limits. A jailbroken device can leave those limits and run extra code next to your app. That makes it easier to change the game or read its files.
The solution
Use the iOS Jailbreak Detector. It is already on the Anti Cheat Monitor prefab. It looks for common signs of a jailbreak, such as jailbreak apps, unusual files, a broken sandbox, injected code, and known tweak libraries.
The native plugin ships in Assets/GUPS/AntiCheat/Plugins/iOS/.
Important
In the plugin import settings, keep Add to Embedded Binaries enabled. Without it, the iOS app can crash at launch.
Step 1: Choose which signs to check
Open Edit > Project Settings > GuardingPearSoftware > AntiCheat and switch to the iOS tab.
iOS jailbreak settings.
You can turn each check on or off, and add your own suspicious paths or library names. When the URL-scheme check is on, AntiCheat adds the entries iOS needs so that check can run.
Note
The Detect fork() option is listed in the settings, but it is turned off for now. The other checks still run.
Note
Verify development builds is off by default. While it is off, this check skips the Editor and development builds. A real result still needs a device build.
The result
When a sign is found, the detector raises the threat score. You can refuse a purchase, flag the session, or close the game.
Settings reference: iOS jailbreak.