Original Clash, Clash.Meta, and mihomo
Early Clash established many configuration conventions still in use today: define nodes in one place, organize outbounds with proxy groups, and reference them in ordered rules. Clash.Meta extended this system and was later maintained under the name mihomo. Older guides may still use the first two names. When you see the same config key, an older guide can help explain its basic purpose, but don't assume the default value, support, or behavior is identical. When troubleshooting, first identify which core your client uses, then consult the relevant project's docs.
What the client and core each do
Clash Meta for Android manages configs and provides Android VPN access; mihomo parses the config, matches rules, and establishes outbound connections. Saving a config only confirms that the file reached the client. Whether it loads and matches rules depends on the core's runtime logs. Conversely, if the system hasn't granted VPN access or a battery-saving policy has stopped the background service, changing YAML outbounds usually won't help. Before reporting an issue, identify which layer is involved: installation, system prompts, and interface issues belong with the client project; fields, rules, and connection parsing should be checked against the core docs.
How to verify community resources
Upstream repositories provide source code and commit history, and issue trackers can help you find similar errors. Search using the exact field name and error type, and check which platform and setup the discussion refers to. For example, a working system proxy on desktop doesn't prove that Android VPN capture is configured correctly. To reproduce an issue, keep the config minimal and include the steps and a redacted error excerpt. Before posting publicly, remove subscription URLs, proxy credentials, and private domains. Connection logs may also expose the destinations you visit.
Keep a working config before updating
Client packages, core changes, and subscription content all have their own update schedules. A client update may change the core, while a subscription refresh may alter node names, proxy groups, or rule order. If routing changes after an update, back up the current file and keep the last working copy. Compare release notes and config differences, and avoid reinstalling the client, refreshing the subscription, and changing DNS all at once. Change one thing at a time, then retest on the same network, app, and destination to narrow down the cause.