Troubleshooting

If you experience issues with the protection process or the app after protection, then the first step is to isolate the protection feature that might be causing the problem. Disable all protections and re-enable them one by one until the issue resurfaces. You can then try narrowing the issue down to specific section rules, symbol locations, etc.

{
    "seed": 645261,
    ...
}

This would rule out if the transformation variation from a particular seed is causing conflicts.

If you start using fixed seeds, then you should, at the very least, change the seed for every release. Using the same seed gives attackers a known starting point for reverse engineering.

If the issue is not related to Jigsaw specifically, refer to the App Shielding Reference Documentation for Android and iOS.

App Store Warnings

When uploading your iOS app to the App Store, you might receive the following warning from the App Store Team:

ITMS-90999: Invalid executable - The executable in your app contains multiple segments with the executable permission bit set when it should only contain one.

This is only a warning and should not block the submission of your app. It is a byproduct of how Jigsaw implements its protection features and will be a non-issue in a future release of the engine.

However, you might also receive the following error when uploading your app:

ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

In this situation, you can try excluding the __DATA,__data section from being encrypted. For example:

jigsawConfiguration "myAppConfig" {
	"sectionEncryption": {
        "enabled": true,
        "sectionRules": [ "*", "!__DATA,__data" ]
    }
}

protect:myAppConfig "Payload/MyApp.app/MyApp";

If you are still experiencing issues with uploading to the App Store, please contact OneSpan Support.