What is the zsource Command? Development, Implementation and Usage in Meituan’s iOS App

What is the zsource command?

Meituan’s iOS app has been using CocoaPods for componentization since 2015. To speed up builds, most components are distributed as binaries via the cocoapods-binary plugin. While binaries improve build time, they hinder debugging because source‑level information is unavailable. Developers could only see stack traces and obscure assembly when a crash occurred inside a binary component.

To address this, Meituan added a new sub‑command zsource to the CocoaPods pod command. The zsource command allows developers to quickly switch a binary component back to its source code for debugging without rebuilding the whole project.

Development History of zsource

The feature was built through a series of hypotheses, experiments, and engineering work:

Hypothesis: Xcode stores the source file path inside the binary, enabling source‑level debugging.

Research: Consulted Mach‑O and DWARF documentation to locate the relevant fields.

Rough experiments: Created a tiny binary containing a class ZSCViewController and inspected it with xxd and dwarfdump.

Discovery: The source path is stored as plain text in the "__debug_str" section, exposed via DWARF attributes AT_name and AT_comp_dir.

Engineering: Used Ruby‑macho and other tools to extract the path, then automated the download of the corresponding source files.

Key Experiments

1. Created a binary libZSource.a and ran:

xxd ./libZSource.a | grep -C 5 'ZSCViewControlle'

The output showed the class name embedded as plain text.

2. Used dwarfdump to inspect DWARF information: dwarfdump ./libZSource.a | grep 'ZSCViewContro' The dump revealed AT_name and AT_comp_dir attributes that contain the full source file path.

Engineering the Solution

With the path information available, the team implemented three CocoaPods commands under the zsource namespace. The workflow is:

Determine the common binary output directory used by Meituan components.

Run dwarfdump (or the internal wrapper) to obtain the expected source location.

Download the source code and place it in the determined directory, allowing Xcode to debug the component as if it were built from source.

Only a few components built within the last year have divergent binary paths; they can be re‑binaryed to fit the same scheme.

Summary

The zsource feature was created entirely through iterative guessing and experimentation, taking roughly two evenings from concept to production. It demonstrates that, even without deep prior knowledge of binary formats, a focused reverse‑engineering approach can quickly yield practical solutions for debugging binary‑distributed iOS components.

Author

Yu Jie , Engineer in Meituan App Business Container Team.

Team Overview

The Business Container Team maintains multiple dynamic containers for Meituan’s products, improving development efficiency across platforms such as mini‑programs, React Native, WebView, and Flutter.