Use JikGuard Protection Tool in your Android build and release workflow.Works with supported Android APK / AAB builds from Unity, Cocos, and Unreal Engine projects.
Start from your existing APK or AAB.
Use JikGuard Protection Tool in your Android build and release workflow.Works with supported Android APK / AAB builds from Unity, Cocos, and Unreal Engine projects.
Start from your existing APK or AAB.
Protect your first Android build with JikGuard Protection Tool.
Confirm that you have the approved Protection Tool package for your environment before starting your first protection run.
Have your release signing key ready for APK builds, or your Google Play upload key for AAB builds.
Use the APK or AAB produced by your existing Android build workflow.
Set the required input, output, and project-specific Protection Tool configuration for this build.
ConfigurationRun the Tool on your prepared build to get the protected APK or AAB.
Protect APK / AABSign the protected build in your existing release-signing process, then verify it before testing or distribution.
Signing GuideJikGuard needs the App signing key certificate SHA-256 from Google Play Console, not the Upload key certificate.
Google Play App SigningTake an existing Android APK or AAB through the JikGuard protection stage and continue with the protected build in your release workflow.
Before continuing, make sure this is the build you intend to protect.
Review the Protection Tool configuration for the build you selected and make sure the required settings for this protection run are in place.
The package name of this build should match the package name assigned to your license. Changing the package name after protection may cause the protected app to fail to start, so finalize it before you run protection.
Run JikGuard Protection Tool with the selected APK or AAB and the configuration prepared for this protection run. The Tool connects to JikGuard during the build-time protection process. When protection completes, continue with the resulting protected APK or AAB.
The protected game itself does not need to connect to JikGuard when players run it.
If protection does not complete, contact JikGuard support.
Signing GuideSign the protected APK or AAB using your existing Android signing workflow.
Your keystore, private key, and signing password remain in your environment.
Use the protected APK produced by JikGuard.
Align the protected APK as required by the Android release workflow.
Sign the aligned protected APK with your release signing key.
Verify the signed protected APK before continuing to testing or distribution.
Use the protected AAB from the protection process.
Use your Google Play upload key to sign the protected AAB before upload.
If you use Google Play App Signing, continue with the dedicated signing guide.
Google Play App SigningUse the SHA-256 certificate fingerprint from the App signing key certificate in Google Play Console when configuring JikGuard for Google Play App Signing.
Your team uses the upload key before the AAB is uploaded to Google Play.
Google Play uses the app signing key for the app that is delivered through Google Play.
Select the Android app you are preparing for release.
Locate the App signing key certificate section for the app.
Copy the SHA-256 shown under the App signing key certificate.
You do not need to provide DER / PEM certificate files, keystore, or private key.
Check these common issues first.
The Tool needs to connect to JikGuard while protection runs. Check that the machine running the Tool is online, then run protection again.
Make sure the package name matches the one assigned to your license, and do not change it after protection.