注销时未处理 AutoDispose StreamProvider

AutoDisposeStreamProvider is not being disposed at loggin out

目前,我们正在使用 Firebase 在我们的应用程序上实现简单的聊天。

我们使用 Riverpod 处理应用程序的启动和身份验证。

启动过程如下:

@override
  Widget build(BuildContext context) {
    LocalNotificationService()
        .handleApplicationWasLaunchedFromNotification(_onSelectNotification);
    LocalNotificationService().setOnSelectNotification(_onSelectNotification);
    _configureDidReceiveLocalNotification();

    // final navigator = useProvider(navigatorProvider);
    final Settings? appSettings = useProvider(settingsNotifierProvider);
    final bool darkTheme = appSettings?.darkTheme ?? false;
    final LauncherState launcherState = useProvider(launcherProvider);

    SystemChrome.setEnabledSystemUIOverlays(
      <SystemUiOverlay>[SystemUiOverlay.bottom],
    );

    return MaterialApp(
      title: 'Thesis Cancer',
      theme: darkTheme ? ThemeData.dark() : ThemeData.light(),
      navigatorKey: _navigatorKey,
      debugShowCheckedModeBanner: false,
      home: Builder(
        builder: (BuildContext context) => launcherState.when(
          loading: () => SplashScreen(),
          needsProfile: () => LoginScreen(),
          profileLoaded: () => MainScreen(),
        ),
      ),
    );
  }

目前,我们仅启用从主屏幕和房间屏幕退出,如下所示:

ListTile(
                    leading: const Icon(Icons.exit_to_app),
                    title: const Text('Çıkış yap'),
                    onTap: () =>
                        context.read(launcherProvider.notifier).signOut(),
                  ),

signOut 的作用:

Future<void> signOut() async {
    tokenController.state = '';
    userController.state = User.empty;
    await dataStore.removeUserProfile();
    _auth.signOut();
    state = const LauncherState.needsProfile();
  }

问题是,每次我们进入 RoomsPage 并从它或主页注销(从房间回来)时,我们都会遇到与 firebase 相同的问题: The caller does not have permission to execute the specified operation.。 当然,signout 关闭了 Firebase,因此 Firebase 抛出了这个错误;但是,它应该在从 RoomsScreen 出来后(即使返回主屏幕也会发生),这个小部件被处置因此连接应该被关闭,处置,但看起来它仍然在记忆中。

房间页面画面如下:

class RoomsPage extends HookWidget {
  @override
  Widget build(BuildContext context) {
    final AsyncValue<List<fc_types.Room>> rooms =
        useProvider(roomsListProvider);
    return Scaffold(
      appBar: Header(
        pageTitle: "Uzmanlar",
        leading: const BackButton(),
      ),
      endDrawer: ConstrainedBox(
        constraints: const BoxConstraints(maxWidth: 275),
        child: SideMenu(),
      ),
      body: rooms.when(
        data: (List<fc_types.Room> rooms) {
          if (rooms.isEmpty) {
            return Container(
              alignment: Alignment.center,
              margin: const EdgeInsets.only(
                bottom: 200,
              ),
              child: const Text('No rooms'),
            );
          }

          return ListView.builder(
            itemCount: rooms.length,
            itemBuilder: (
              BuildContext context,
              int index,
            ) {
              final fc_types.Room room = rooms[index];

              return GestureDetector(
                onTap: () => pushToPage(
                  context,
                  ChatPage(
                    room: room,
                  ),
                ),
                child: Container(
                  padding: const EdgeInsets.symmetric(
                    horizontal: 16,
                    vertical: 8,
                  ),
                  child: Row(
                    children: <Widget>[
                      Container(
                        height: 40,
                        margin: const EdgeInsets.only(
                          right: 16,
                        ),
                        width: 40,
                        child: ClipRRect(
                          borderRadius: const BorderRadius.all(
                            Radius.circular(20),
                          ),
                          child: Image.network(room.imageUrl ?? ''),
                        ),
                      ),
                      Text(room.name ?? 'Room'),
                    ],
                  ),
                ),
              );
            },
          );
        },
        loading: () => const Center(
          child: CircularProgressIndicator(),
        ),
        error: (Object error, StackTrace? stack) => ErrorScreen(
          message: error.toString(),
          actionLabel: 'Home',
          onPressed: () => Navigator.of(context).pop(),
        ),
      ),
    );
  }
}

提供者很简单:

final AutoDisposeStreamProvider<List<fc_types.Room>> roomsListProvider =
    StreamProvider.autoDispose<List<fc_types.Room>>(
  (_) async* {
    final Stream<List<fc_types.Room>> rooms = FirebaseChatCore.instance.rooms();
    await for (final List<fc_types.Room> value in rooms) {
      yield value;
    }
  },
  name: "List Rooms Provider",
);

我想 AutoDispose 构造函数会在删除小部件时自动处理此提供程序,因此,它应该关闭与 Firebase 的连接(如文档所述)。

这里有什么问题?

我错过了什么?

我应该打开一个关于这个的问题吗?

编辑: 由于您不能直接取消 Stream,您可以转发 FirebaseCore.instance.rooms() 并让提供商进行清理:

final AutoDisposeStreamProvider<List<fc_types.Room>> roomsListProvider =
    StreamProvider.autoDispose<List<fc_types.Room>>(
  (_) => FirebaseChatCore.instance.rooms(),
  name: "List Rooms Provider",
);

上一个答案:

autoDispose 仅关闭提供的流本身(您使用 async* 创建的流),但您仍然需要自己关闭 Firebase 流。

您可以使用onDispose(),如Riverpod documentation

所示
  ref.onDispose(() => rooms.close());

documentation 中,示例使用基于 StreamController

Stream
final messageProvider = StreamProvider.autoDispose<String>((ref) async* {
  // Open the connection
  final channel = IOWebSocketChannel.connect('ws://echo.websocket.org');

  // Close the connection when the stream is destroyed
  ref.onDispose(() => channel.sink.close());

  // Parse the value received and emit a Message instance
  await for (final value in channel.stream) {
    yield value.toString();
  }
});

在您的情况下,您的方法是 returning Stream。这改变了游戏规则。只是 return Stream.

final AutoDisposeStreamProvider<List<fc_types.Room>> roomsListProvider =
    StreamProvider.autoDispose<List<fc_types.Room>>(
  (_) => FirebaseChatCore.instance.rooms(),
  name: "List Rooms Provider",
);