Understanding Flutter Exceptions and Lifecycle Management

The Xianyu tech team introduced Flutter in early 2018 and gradually migrated complex product‑detail and publishing pages to it. After systematic debugging they reduced the Flutter exception rate from a few per‑thousand to less than one per‑thousand, solving more than 90% of the issues.

Exceptions were grouped into two major categories, which together account for about 90% of all stack traces:

1. setState‑related stacks

#0      State.setState (package:flutter/src/widgets/framework.dart:1141)
#1      _DetailCommentWidgetState.replyInput.
.
(package:fwn_idlefish/biz/item_detail/fx_detail_comment.dart:479)
#2      FXMtopReq.sendReq.
(package:fwn_idlefish/common_lib/network/src/mtop_req.dart:32)
#3      NetService.requestWithModel.
(package:fwn_idlefish/common_lib/network/src/net_service.dart:58)
#4      _rootRunUnary (dart:async/zone.dart:1132)
#5      _CustomZone.runUnary (dart:async/zone.dart:1029)
#6      _FutureListener.handleValue (dart:async/future_impl.dart:129)

2. buildContext‑related stacks

#0      Navigator.of (package:flutter/src/widgets/navigator.dart:1270)
#1      Navigator.pop (package:flutter/src/widgets/navigator.dart:1166)
#2      UploadProgressDialog.hide (package:fwn_idlefish/biz/publish/upload_progress_dialog.dart:35)
#3      PublishSubmitReducer.doPost.
(package:fwn_idlefish/biz/publish/reducers/publish_submit_reducer.dart:418)
#4      <asynchronous suspension>
#5      FXMtopReq.sendReq.
(package:fwn_idlefish/common_lib/network/src/mtop_req.dart:32)
#6      NetService.requestWithModel.
(package:fwn_idlefish/common_lib/network/src/net_service.dart:58)
#7      _CustomZone.runUnary (dart:async/zone.dart:1029)

The first group is tied to the element‑state lifecycle, while the second is linked to BuildContext . In Flutter, BuildContext is merely an interface; its concrete implementation is Element . The following getters illustrate how BuildContext is obtained from an element:

Element get _currentElement => _registry[this];
BuildContext get currentContext => _currentElement;

Understanding the Flutter lifecycle is essential. The state lifecycle is driven by the element that creates it, and the activity lifecycle (Android) maps to AppLifecycleState values: resumed , inactive , paused , and suspending . These states affect when draw‑frame callbacks occur.

A common source of exceptions is invoking setState after a State object has been disposed (e.g., from timers, animations, or network callbacks). The safe pattern is to check mounted before calling setState :

if (mounted) {
  setState(() { /* update UI */ });
}

Another frequent mistake is using a BuildContext from a different widget tree (e.g., an outer context when showing a bottom sheet). The correct approach is to use the context that belongs to the widget that owns the UI element, such as the bottom‑sheet’s own context for focus handling.

For further reading, see the official Flutter repository and documentation.