Uni-app uses IPA hardening
Uni-app iOS titles use IPA hardening, not the Xcode-project confuse flow. HBuilderX (or the uni-app CLI) already produced the package. Crab hardens that IPA’s binary and resources. Do not import the Vue project as if it were a Unity or Flutter export.
When to use this path
You have a uni-app app that installs from an IPA, and you need a different fingerprint from another listing or from a previous package. You do not have a maintainable Xcode tree that Crab should compile.
When not to
Native, Unity, Flutter, and Cocos projects still go through their Xcode export and the compile-level tool. Using IPA hardening on those is the wrong entry. A self-built Framework / SDK that still has LLVM IR uses Crab Directed Hardening, not this IPA path. See the Uni-app IPA article for the checklist, and obfuscation vs hardening for the wording.
Apply with Bundle Id + “uni-app / IPA”. Review outcomes still depend on a listing that matches the hardened package.
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.