The Mach-O has an encryption-info load command but cryptid is 0, so the executable is shipped in the clear (easier to reverse).
How it's exploited
cryptid=0 means the executable is not FairPlay-encrypted, so the binary on disk is the binary in memory: trivially disassembled, string-dumped, and repackaged.
Why it matters
Reverse engineering and tamper analysis require no decryption step at all. (Ad-hoc/enterprise/TestFlight builds are legitimately unencrypted; store builds should not be.)
How to fix it
For App Store distribution this is applied by Apple automatically; investigate why the analyzed store build lacks it.
Do not rely on binary encryption as your only obfuscation; strip symbols and avoid secrets in code regardless.