iOS应用因Crashlytics含越狱检测代码遭App Store拒审求解决方案

Hey there, I’ve dealt with this exact scenario before—so let’s break down how to get your app past the 1.1 Safety rejection quickly.

First, let’s recap your situation to align: #

来自Apple
1.1 安全：不良内容
您好，感谢您的耐心等待。为解决此前告知的问题，您下次提交时需移除应用中的越狱检测类及方法。期待您重新提交后的审核。
此致
App Store审核团队

You ran a grep command and found "Cydia" references in the Crashlytics framework, but other apps using Crashlytics didn’t hit this issue. Here’s why that might be, and how to fix it:

Step 1: Update Crashlytics to the Latest Version #

Older versions of Crashlytics (especially legacy Fabric-era builds) included lightweight jailbreak detection logic to prioritize crash reports from non-jailbroken devices. Google/Firebase has since removed this code in newer releases.

To update via CocoaPods:

pod update Crashlytics

If you’re using manual framework integration, grab the latest version from the Firebase/Crashlytics developer portal and replace your existing framework files.

Step 2: Wipe All Build Caches (Critical!) #

Xcode and CocoaPods often hold onto old framework artifacts even after updates—this is likely why your other apps didn’t have issues (they probably used a clean, updated build of Crashlytics).

Follow these steps in order:

• Close Xcode completely
• Delete your Derived Data:

  rm -rf ~/Library/Developer/Xcode/DerivedData
  

• Clear CocoaPods cache:

  pod cache clean --all
  

• Reinstall pods:

  pod install
  

• Open Xcode, then run a Clean Build Folder (Cmd + Shift + K) before rebuilding your app.

Step 3: Verify the Jailbreak Detection Code is Gone #

Double-check that "Cydia" references are no longer present. Run this command again in your project root:

grep -lr "Cydia" * | grep -v .svn | grep -v .md

You can also use the nm tool to check for related symbols in the framework:

nm -U Pods/Crashlytics/iOS/Crashlytics.framework/Crashlytics | grep -i cydia

If both commands return no results, you’re good to go.

Step 4: Add a Note for the Review Team (Optional but Helpful) #

When resubmitting, add a quick note in the "App Review Information" section:

"I’ve updated the Crashlytics framework to the latest version, which removes all jailbreak detection-related code. I’ve verified the framework no longer contains references to Cydia or jailbreak detection logic."

This helps the review team validate your fix faster.

Why Your Other Apps Didn’t Have This Issue? #

Chances are those apps were already using a newer Crashlytics version without the jailbreak detection code, or their build caches didn’t have leftover old framework files. Sometimes Apple’s review criteria can also have minor variations in how they scan for this code, so updating and cleaning is the safest bet.

内容的提问来源于stack exchange，提问作者Tim Bernikovich