Make the `unregister` method ignore the non-existence of an instance instead of throwing an error.

[Gorniaky]

I'm developing an app, but I noticed that the dispose method of a widget is being called more than once, causing the second time to throw an error with the unregister method, which I think is unnecessary since it could easily be ignored.

[escamoteur]

That would be a possibility but in reality this shows you that you call dispose once too often. If you cannot fix it add a guard value in your dispose function. It's important that the library throws so you know that there is a logic problem Am 25. Jan. 2026, 13:32 -0500 schrieb Gorniaky ***@***.***>:

…

Gorniaky created an issue (flutter-it/get_it#420) I'm developing an app, but I noticed that the dispose method of a widget is being called more than once, causing the second time to throw an error with the unregister method, which I think is unnecessary since it could easily be ignored. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Gorniaky]

I understand there's something wrong with the flow, but in production this only hinders progress. I simply put the function in a try-catch block because, to me, there's nothing wrong with my workflow, mainly because I register the dependency in initState and cancel it in dispose.

In short, my suggestion is to ignore the instance's non-existence.

That would be a possibility but in reality this shows you that you call dispose once too often.

If you cannot fix it add a guard value in your dispose function.
It's important that the library throws so you know that there is a logic problem
Am 25. Jan. 2026, 13:32 -0500 schrieb Gorniaky @.***>:
…

Gorniaky created an issue (flutter-it/get_it#420)
I'm developing an app, but I noticed that the dispose method of a widget is being called more than once, causing the second time to throw an error with the unregister method, which I think is unnecessary since it could easily be ignored.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>