移动应用
mobile-release-error-handling
更新于 2026-11-02
Mobile Release · 错误处理规则
Error-handling rules for Mobile Release: classification, typed codes and single-point mapping to user outcomes.
- 技术栈
- Mobile Release
- 主题
- 错误处理
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Classify failures once: expected (validation, not-found) vs unexpected (bugs, dependencies down)
- ✓ Return typed errors carrying a stable code plus human-readable context
- ✓ Map errors to user-visible outcomes at the outermost layer only
✕ 常见反模式
- ✕ String matching on error messages to decide control flow
- ✕ Swallowing an error to keep the happy path green
- ✕ Leaking stack traces or internal identifiers to end users
◎ 交付前验证
- ◎ Association file fetch validated with the platform validator tooling
- ◎ Deep links opened from an external app on a real device
- ◎ Release build signed with the production key
同分类条目
26 篇移动应用
Flutter 工程规则
Flutter rules: adapter-separated platform code and rebuild-scope discipline
移动应用
React Native 工程规则
React Native rules: native module boundaries and release-mode measurement
移动应用
Android Compose 工程规则
Jetpack Compose rules: stateless composables and stable remember keys
移动应用
SwiftUI 工程规则
SwiftUI rules: single source of truth state and MainActor UI updates
移动应用
HarmonyOS ArkTS 工程规则
ArkTS rules: declarative state decorators and ability lifecycle handling
移动应用
WeChat Mini Program 工程规则
Mini Program rules: setData payload discipline and package-size budget