使用CocoaPods后IPA体积增至60MB，求保留Pod的体积缩减方案

Hey there! I totally get wanting to hold onto CocoaPods for its seamless update workflow while trimming down that IPA size. Here are practical, actionable tips to shrink your build without ditching CocoaPods:

Key Optimizations to Try #

• Switch to Static Frameworks in CocoaPods
  You don’t have to abandon CocoaPods to get static library benefits. Update your Podfile with this line to force static linkage for all pods:

  use_frameworks! :linkage => :static
  

  This mimics the static library setup you tested earlier, cutting out the overhead of dynamic frameworks that bloat your IPA.

• Enable Bitcode
  Bitcode lets Apple re-optimize your app’s binary for specific devices when it’s uploaded to the App Store. In Xcode, go to your target’s Build Settings, find Enable Bitcode, and set it to Yes. Just double-check that all your third-party pods support Bitcode (most popular ones like Kingfisher, Facebook SDK do).

• Strip Unused Architectures
  By default, Xcode includes architectures for simulators (like x86_64) and devices in your build, which adds unnecessary bulk. Add a Run Script phase in your target’s Build Phases to strip simulator architectures before packaging:

  APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}"
  
  # This script loops through the frameworks embedded in the application and
  # removes unused architectures.
  find "$APP_PATH" -name '*.framework' -type d | while read -r FRAMEWORK
  do
      FRAMEWORK_EXECUTABLE_NAME=$(defaults read "$FRAMEWORK/Info.plist" CFBundleExecutable)
      FRAMEWORK_EXECUTABLE_PATH="$FRAMEWORK/$FRAMEWORK_EXECUTABLE_NAME"
      echo "Executable is $FRAMEWORK_EXECUTABLE_PATH"
  
      EXTRACTED_ARCHS=()
  
      for ARCH in $ARCHS
      do
          echo "Extracting $ARCH from $FRAMEWORK_EXECUTABLE_NAME"
          lipo -extract "$ARCH" "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH-$ARCH"
          EXTRACTED_ARCHS+=("$FRAMEWORK_EXECUTABLE_PATH-$ARCH")
      done
  
      echo "Merging extracted architectures: ${ARCHS}"
      lipo -o "$FRAMEWORK_EXECUTABLE_PATH-merged" -create "${EXTRACTED_ARCHS[@]}"
      rm "${EXTRACTED_ARCHS[@]}"
  
      echo "Replacing original executable with thinned version"
      rm "$FRAMEWORK_EXECUTABLE_PATH"
      mv "$FRAMEWORK_EXECUTABLE_PATH-merged" "$FRAMEWORK_EXECUTABLE_PATH"
  
  done
  

  Also, set Valid Architectures in Build Settings to only include device architectures (e.g., arm64 for modern iPhones).

• Optimize Release Builds
  Tweak these Build Settings for your Release configuration:

  • Set Optimization Level to Fastest, Smallest [-Os] to let the compiler shrink code size.
  • Turn on Dead Code Stripping to remove unused functions and classes.
  • Enable Strip Debug Symbols During Copy to cut out debug info that’s not needed for production.

• Trim Unused Resources & Libraries

  • Audit your Copy Bundle Resources phase in Build Phases and delete any unused images, fonts, or asset files. Tools like LSUnusedResources can help scan for unreferenced assets.
  • Use only the parts of third-party libraries you need. For example, instead of pulling in the full Facebook SDK, specify only the modules you use:

    pod 'FacebookSDK/Login'
    pod 'FacebookSDK/Share'
    

    This cuts out unused code from the SDK.

• Compress Assets

  • Convert images to more efficient formats like WebP (you can use tools like Squoosh to compress without losing quality).
  • Enable Compress PNGs and Compress JPEGs in your Asset Catalog settings to let Xcode optimize image files during build.

• Leverage App Thinning
  While this won’t reduce your local IPA size, App Thinning ensures users only download the version of your app optimized for their specific device (e.g., no extra assets for older iPhones). Enable it by checking Enable App Thinning in your Xcode archive settings.

Combining these steps should get your IPA size close to the static library build you tested, while keeping the convenience of CocoaPods for updates.

内容的提问来源于stack exchange，提问作者Renuka Pandey