iOS Integration

Xcode workflow

ObfGuard integrates as a build phase in Xcode or through your CI pipeline. It is recommended to target Release builds only to avoid slowing developer iterations.

• Install ObfGuard CLI on build machines
• Create a Release-only Run Script phase
• Point ObfGuard to the signed build output

Policy targeting

Use target-specific policy scopes to focus protection on sensitive frameworks and modules. This keeps build times predictable while maximizing protection where it matters.

• Scope policies by bundle ID
• Exclude third-party SDKs to avoid compatibility issues
• Enable additional string protection for API keys

CI/CD integration

Run ObfGuard after code signing to preserve integrity. The CLI produces a hardened binary and a protection report artifact.

obfguard build --policy policies/ios.yaml --input build/MyApp.app --output build/MyApp-protected.app

Validation checklist

• Launch critical flows (login, purchase, sync)
• Verify entitlement checks and licensing
• Confirm reporting artifacts are stored
• Validate crash-free sessions in staging

Best practices

Keep policies consistent across builds and document any exclusions or overrides.

• Use a baseline policy for all release targets
• Keep third-party SDKs in an explicit exclusion list
• Review protection reports with each release
• Version and tag policy changes in git