escamoteur
commented
3 weeks ago That is weird as we do almost the same. Could it be that there has been another scope pushed so your popScope pops the wrong scope? Try popScopeTil instead Am 17. Nov. 2024, 09:48 +0100 schrieb thanoofayoob @.***>:
Issue Summary: I am encountering an issue with the GetIt package in my Flutter application related to the lifecycle of a GraphQLClient instance. Specifically, when a user logs out, I attempt to unregister or isolate the GraphQLClient to avoid carrying over the previous user's data. However, even after introducing scoped dependencies and unregistering the old client, the new user still interacts with the previous user's GraphQL client instance or its remnants, leading to unexpected behavior such as accessing stale data or using outdated headers. Steps to Reproduce: A user logs in, and the AppGraphQLClient is registered using: injector.registerSingleton(() => AppGraphQLClient()); The client includes headers with the user's token for authentication. On user logout, I attempted two approaches: Directly unregistering the GraphQLClient instance: injector.unregister(); Introducing scoped dependencies using: injector.pushNewScope( scopeName: "NewUser", init: (getIt) { injector.registerSingleton(() => AppGraphQLClient()); }, ); The scope is dropped on logout using: injector.popScope(); A new user logs in, triggering a re-registration of the AppGraphQLClient for the new session. Despite these efforts, the new user still interacts with the old client's instance or configuration, including outdated headers like the previous user's token. Expected Behavior: After a user logs out: The previous AppGraphQLClient instance should be completely destroyed, along with any cached data or retained headers. On new user login, a completely fresh AppGraphQLClient instance should be initialized with the new user's token and other required configurations. Observed Behavior: Even after unregistering the previous client or using scoped dependencies with pushNewScope, the new user still interacts with the previous user's instance or data. This leads to stale headers or incorrect token usage. Additional Notes: I do not reset the entire GetIt container on logout, as I want to preserve other dependencies — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
thanoofayoob
Issue Summary: I am encountering an issue with the GetIt package in my Flutter application related to the lifecycle of a GraphQLClient instance. Specifically, when a user logs out, I attempt to unregister or isolate the GraphQLClient to avoid carrying over the previous user's data. However, even after introducing scoped dependencies and unregistering the old client, the new user still interacts with the previous user's GraphQL client instance or its remnants, leading to unexpected behavior such as accessing stale data or using outdated headers.
Steps to Reproduce:
A user logs in, and the AppGraphQLClient is registered using:
injector.registerSingleton(() => AppGraphQLClient()); The client includes headers with the user's token for authentication.
On user logout, I attempted two approaches:
Directly unregistering the GraphQLClient instance:
injector.unregister();
Introducing scoped dependencies using:
injector.pushNewScope( scopeName: "NewUser", init: (getIt) { injector.registerSingleton(() => AppGraphQLClient()); }, ); The scope is dropped on logout using:
injector.popScope(); A new user logs in, triggering a re-registration of the AppGraphQLClient for the new session.
Despite these efforts, the new user still interacts with the old client's instance or configuration, including outdated headers like the previous user's token.
Expected Behavior: After a user logs out:
The previous AppGraphQLClient instance should be completely destroyed, along with any cached data or retained headers. On new user login, a completely fresh AppGraphQLClient instance should be initialized with the new user's token and other required configurations. Observed Behavior: Even after unregistering the previous client or using scoped dependencies with pushNewScope, the new user still interacts with the previous user's instance or data. This leads to stale headers or incorrect token usage.
Additional Notes:
I do not reset the entire GetIt container on logout, as I want to preserve other dependencies