如何检查CocoaPods模块是否嵌入静态库及.a库是否含Alamofire

Let's break down how to verify if Alamofire is embedded in your .a library, and figure out why that armv7 error is popping up.

Step 1: Verify Your Library's Supported Architectures #

First, confirm that your library actually includes the armv7 architecture slice (since the error specifically mentions it). Run this in Terminal:

lipo -info /path/to/your/library.a

You should see armv7 listed in the output. If it's missing, that's a red flag—your library wasn't built for armv7 at all. If it is present, move on to checking for Alamofire symbols.

Step 2: Check for Alamofire Symbols in the armv7 Slice #

To see if Alamofire code is embedded in the armv7 part of your library, use the nm tool to search for Alamofire-related symbols:

nm -arch armv7 /path/to/your/library.a | grep -i alamofire

If you get output like _OBJC_CLASS_$_Alamofire.Session or _Alamofire_Request_serializeResponse, that means Alamofire symbols are present in the armv7 slice. If you get no output, the symbols are missing—your library wasn't properly linked with Alamofire for armv7.

Another way to check dependencies is with otool:

otool -L -arch armv7 /path/to/your/library.a

If this lists Alamofire.framework as a dynamic dependency, that means your library expects Alamofire to be present at runtime (which would cause the error if users don't include it). If you intended to statically link Alamofire into your .a, this line shouldn't exist—instead, the symbols should be embedded directly.

Step 3: Reading Module Information #

Static libraries don't store full module metadata like frameworks do, but you can check for Swift module hints if Alamofire (or your library) uses Swift:

otool -arch armv7 -s __TEXT __swift5_types /path/to/your/library.a | head -20

This will show Swift type metadata. If you see references to Alamofire classes here, it confirms Swift module info related to Alamofire is present in the armv7 slice.

If you have access to the project that built the library, also check the build settings:

• Ensure VALID_ARCHS includes armv7
• Verify that Alamofire is set to link statically (if using CocoaPods, use use_frameworks! :linkage => :static or specify :linkage => :static for Alamofire in your Podfile)
• Double-check that ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES is configured correctly for your target

Troubleshooting the Error #

Even if your config didn't change, here are common fixes:

• Clean and rebuild: Cached build artifacts can cause missing symbols. Clean your project's build folder, then rebuild the library from scratch.
• Check CocoaPods integration: Run pod deintegrate followed by pod install to reset your Pods setup—sometimes Pods can get out of sync with target architectures.
• Verify static linking: Make sure Alamofire is being linked statically into your library, not dynamically. If it's dynamic, users will need to include the Alamofire framework separately (which they're not doing, hence the error).
• Check armv7 build flags: Ensure that when building the library, the armv7 architecture isn't excluded. Some projects might accidentally drop armv7 in newer Xcode versions.

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