Flutter中捕获Null异常详情：BLOC场景下的问题求助

问题背景 #

我在Flutter项目中采用BLOC模式结合Stream做状态管理，Stream监听Loading、Data、Error三种状态同步到UI展示。目前遇到两个场景的矛盾：

场景一：无try/catch时的表现 #

• 实现代码：

getNotificationDetail({required String notificationId}) async {
    await _notificationRepository
        .getNotificationDetail(
      getNewNotificationEndPoint: END_POINT_NOTIFICATION_DETAIL,
      notificationId: notificationId,
    )
        .then(
          (responseValue) {
        _notificationDetailController.sink.add(MessageState.loading);
        if (responseValue?.messageState == MessageState.data) {
          notificationDetailModel = responseValue!.data;
          notificationDetailData = notificationDetailModel!.data;
          _notificationDetailController.sink.add(MessageState.data);
        } else if (responseValue?.messageState == MessageState.requestError) {
          errorHandlingModel = responseValue?.data;
          _notificationDetailController.sink.add(MessageState.requestError);
        } else if (responseValue?.messageState == MessageState.serverError) {
          _notificationDetailController.sink.add(MessageState.serverError);
        }
      },
    );
  }

• 报错信息：

E/flutter (22630): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: type 'Null' is not a subtype of type 'int'
E/flutter (22630): #0      new NewNotificationCountData.fromJson (XXXXXXXXXX/model/notification_model/new_notification_count_model.dart:39:19)

• 优缺点：控制台能精准定位到Model中具体的Null字段，方便快速修复；但UI会一直卡在Loading状态，无法切换到错误状态。

场景二：添加try/catch后的表现 #

• 实现代码：

getNotificationDetail({required String notificationId}) async {
    try {
      await _notificationRepository
          .getNotificationDetail(
        getNewNotificationEndPoint: END_POINT_NOTIFICATION_DETAIL,
        notificationId: notificationId,
      )
          .then(
        (responseValue) {
          _notificationDetailController.sink.add(MessageState.loading);
          if (responseValue?.messageState == MessageState.data) {
            notificationDetailModel = responseValue!.data;
            notificationDetailData = notificationDetailModel!.data;
            _notificationDetailController.sink.add(MessageState.data);
          } else if (responseValue?.messageState == MessageState.requestError) {
            errorHandlingModel = responseValue?.data;
            _notificationDetailController.sink.add(MessageState.requestError);
          } else if (responseValue?.messageState == MessageState.serverError) {
            _notificationDetailController.sink.add(MessageState.serverError);
          }
        },
      );
    } catch (e) {
      errorMessage = e.toString();
      _notificationDetailController.sink.add(MessageState.exception);
    }
  }

• 报错信息：

The following _CastError was thrown building StreamBuilder<MessageState>(dirty, state: _StreamBuilderBaseState<MessageState, AsyncSnapshot<MessageState>>#aa511):
Null check operator used on a null value

The relevant error-causing widget was: 
  StreamBuilder<MessageState> StreamBuilder:file:///XXXXXXXXXXX/lib/modules/notifications/view_items/notification_detail_body.dart:29:13
When the exception was thrown, this was the stack: 

• 优缺点：UI能正常切换到Exception错误状态；但控制台仅显示模糊的Null check operator used on a null value，无法定位具体的Null字段，需要手动排查API和Model。

核心需求 #

实现：API返回Null时，UI显示错误状态，同时控制台能自动定位到具体的Null字段。

解决方案 #

1. 增强Model层fromJson的错误捕获与日志 #

问题根源在于fromJson转换时抛出的异常被外层try/catch捕获后丢失了原始详细信息。需要在Model的fromJson方法中单独处理，打印具体字段的Null信息后再重新抛出异常。

以NewNotificationCountData为例，修改fromJson方法：

factory NewNotificationCountData.fromJson(Map<String, dynamic> json) {
  try {
    return NewNotificationCountData(
      id: json['id'] as int, // 原报错的第39行字段
      // 其他字段转换逻辑...
    );
  } catch (e) {
    // 定位并打印出错的字段
    String errorField = '未知字段';
    if (json['id'] == null || json['id'] is! int) {
      errorField = 'id';
    }
    // 扩展：可遍历所有字段自动检测类型不匹配或Null的情况
    print("NewNotificationCountData转换失败: 字段[$errorField]异常，错误信息=$e");
    // 重新抛出异常，让上层BLOC捕获
    rethrow;
  }
}

或者用通用工具函数批量处理字段：

// 通用字段解析工具，打印错误信息并返回结果
T? safeParse<T>(dynamic value, String fieldName) {
  if (value is T) {
    return value;
  }
  print("字段[$fieldName]解析失败: 期望类型${T.toString()}，实际值=$value");
  return null;
}

// 在fromJson中使用
factory NewNotificationCountData.fromJson(Map<String, dynamic> json) {
  final id = safeParse<int>(json['id'], 'id');
  if (id == null) {
    throw Exception("字段[id]为Null或类型错误");
  }
  return NewNotificationCountData(id: id);
}

2. 调整BLOC层的try/catch与异步逻辑 #

原代码中then回调的异常不会被外层try/catch捕获，改用纯async/await链式写法，确保所有异常能被捕获，同时保留完整错误栈：

getNotificationDetail({required String notificationId}) async {
  try {
    // 先发送Loading状态，避免API请求耗时过长时UI无状态
    _notificationDetailController.sink.add(MessageState.loading);
    // 用await替代then，统一异常捕获
    final responseValue = await _notificationRepository.getNotificationDetail(
      getNewNotificationEndPoint: END_POINT_NOTIFICATION_DETAIL,
      notificationId: notificationId,
    );

    if (responseValue?.messageState == MessageState.data) {
      // 替换非空断言为null检查，减少潜在错误
      if (responseValue?.data != null && responseValue!.data.data != null) {
        notificationDetailModel = responseValue.data;
        notificationDetailData = notificationDetailModel.data;
        _notificationDetailController.sink.add(MessageState.data);
      } else {
        throw Exception("API返回的data或data.data字段为Null");
      }
    } else if (responseValue?.messageState == MessageState.requestError) {
      errorHandlingModel = responseValue?.data;
      _notificationDetailController.sink.add(MessageState.requestError);
    } else if (responseValue?.messageState == MessageState.serverError) {
      _notificationDetailController.sink.add(MessageState.serverError);
    }
  } catch (e, stackTrace) {
    // 打印完整错误栈，包含Model层的详细错误位置
    print("获取通知详情失败: $e");
    print(stackTrace);
    errorMessage = e.toString();
    _notificationDetailController.sink.add(MessageState.exception);
  }
}

3. 额外优化：减少非空断言的使用 #

尽量用null检查或??默认值替代!非空断言，从源头减少Null错误的发生：

// 替换
notificationDetailModel = responseValue!.data;
// 为
if (responseValue?.data == null) {
  throw Exception("API返回的data字段为Null");
}
notificationDetailModel = responseValue!.data;

内容的提问来源于stack exchange，提问作者La Pyae