Uni-app iOS builds are cloud-packaged. You typically only have an IPA — not an Xcode tree Crab can obfuscate at compile time. The Uni-app path is therefore IPA in, obfuscated IPA out. Use the Uni-app edition from App Center, not the General edition used for Unity, Flutter, Cocos, or native projects.
1. Download the Uni-app edition from App Center
Install App Center, then download the Uni-app edition. The General edition expects an Xcode project. A cloud-packaged uni-app has none, so that entry will not match the payload you will submit.
2. Apply for a license and import the license file
Request a license in the tool (registration-code page) with the Bundle Id you will submit, and say the project is uni-app / IPA. When the license file arrives, import it before you pick a package.
3. Select the IPA
Choose the IPA from the uni-app cloud build. Confirm it installs and launches first. Do not reuse an IPA from another listing and only resticker the name.
4. Configure signing
Set signing with the same certificates and profiles you already use for this Bundle Id. The output IPA is what you upload, so signing has to be in place before you start.
5. Adjust obfuscation settings
Tune the obfuscation config for this package. If the IPA also contains a native module or a custom SDK, mention that when you apply so isolation and resource rules can be set.
6. Start obfuscation — you get an obfuscated IPA
Click start obfuscation. When it finishes, you have a hardened IPA. Upload with the same account and certificates. Store screenshots, description, and hidden features still have to match the package; see 2.3.1 and 4.3. Overview: Uni-app IPA hardening. Engines that still export Xcode use Cocos, Unity, or Flutter instead.
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.