# 在构建过程中调用了 setState() 或 markNeedsBuild()

- **ID:** `flutter/setstate-or-initstate-async`
- **领域:** flutter
- **类别:** runtime_error
- **验证级别:** ai_generated
- **修复率:** 92%

## 根因

Widget 的 build 方法或其依赖项同步触发了 setState()，违反了 Flutter 的单帧构建约束。

## 版本兼容性

| 版本 | 状态 | 引入 | 弃用 |
|------|------|------|------|
| Flutter 3.10 | active | — | — |
| Flutter 3.13 | active | — | — |
| Flutter 3.16 | active | — | — |

## 解决方案

1. ```
   Use addPostFrameCallback to defer the setState call until after the current build frame:
WidgetsBinding.instance.addPostFrameCallback((_) {
  setState(() { /* update state */ });
});
   ```
2. ```
   Restructure widget to avoid calling setState during build. Move the triggering logic to initState or a separate event handler that runs after the initial layout.
   ```
3. ```
   If the update is from a stream or future, use a StreamBuilder or FutureBuilder to handle asynchronous state changes without manual setState.
   ```

## 无效尝试

- **Wrapping the setState() call in a Future.delayed(Duration.zero)** — Merely postpones the call to the next frame but does not address the root cause of calling setState during build. (40% 失败率)
- **Moving setState() to initState() without checking lifecycle** — initState() is called before build, but if the setState depends on BuildContext or inherited widgets not yet available, it can still cause issues. (50% 失败率)
- **Using a global variable to track build state and skip setState** — Brittle and error-prone; global state management often leads to other race conditions and missed updates. (60% 失败率)