Supports various language mixed compilation c/c++/OC/OC++/swift/dart, all languages mixed compilation, no developer adjustments needed.
Static .a libraries and static frameworks can go through project obfuscation. To harden a Framework / SDK itself at IR (Crab Directed Hardening, same family as OLLVM), use the Framework hardening entry. A prebuilt Dynamic Mach-O with no IR left is not supported on either path.
Please rest assured to try, we have a large number of successful online cases, you can personally verify.
Project obfuscation covers static .a libraries and static frameworks. Dynamic Mach-O frameworks do not use that entry. If the Framework still compiles through LLVM and has IR, Crab Directed Hardening (IR-level, OLLVM-like) can be evaluated. A stripped dynamic library with no IR cannot.
The tool works at the build-system level on symbols, resources, and call stacks so each build can have independent characteristics, which helps with 4.3 and 2.3.1 class issues. Review still depends on whether the app itself complies. We do not promise approval.
Download App Center, choose the General edition or the Uni-app edition, then apply for a license on the registration-code page.
macOS (Apple Silicon / Intel) has full feature support and talks to the Xcode flow. The Windows build is partial; complete compile and submission still needs a Mac.
Use the single-app trial plan for one Bundle Id. Choose monthly starter or enterprise if you need multiple apps and isolation sets. Enterprise includes more machines and support. IPA analysis and submission help are sold separately. See Pricing.
Yes. Turn on Restore dSYM file in the tool’s run settings to map obfuscated symbols back to original names. Code expansion still lets you restore the stack, but not the exact source line. See the dSYM article in the blog.
Yes. The tool integrates with Xcode so you can debug the obfuscated binary. Exclusion rules are in the online docs.
Yes. Languages include c/c++/objc/swift/dart, plus Unity3D, Flutter, SwiftUI, and Cocos-exported iOS projects. Uni-app uses IPA hardening. IR-level protection of a Framework / SDK or the App binary uses Crab Directed Hardening (Framework hardening and App hardening are separate entries). See the matching solution pages.
Resources can be renamed, signature-broken, and encrypted. The runtime support SDK uses independent characteristics per build to reduce cross-app interference. Exact scope follows your project config and the docs.
Crab Directed Hardening is an IR-level path in the same family as OLLVM (control-flow flattening, bogus control flow, instruction substitution). It is not a fork of public OLLVM, and not Xcode-project confuse or uni-app IPA hardening. Use Framework hardening and write 「Framework hardening」 for an SDK; use App hardening and write 「App hardening」 for the App binary.
Request a trial, then archive and submit
Download App Center, choose the General or Uni-app edition, then apply for a license on the registration-code page. The docs cover the operator steps.