Mixing Bloc with dependency injection tools like get_it can streamline object management but requires careful consideration to avoid pitfalls.
Bloc and Cubit have a tightly scoped lifecycle: create, render, dispose. When a screen is reopened, a new instance is created to ensure fresh state management. Using a singleton for Bloc or Cubit disrupts this lifecycle, causing issues like unexpected state persistence. Once closed, a singleton cannot be recreated during runtime, potentially leading to errors.
To prevent such issues, use registerFactory for Bloc or Cubit instances. This ensures each instance starts with a clean state and aligns with Bloc’s design. Singletons, however, work well for shared services like repositories, APIs, or databases, which benefit from persistence.
For dependency injection, Felix Angelov recommends using RepositoryProvider instead of get_it for better integration and scoped management within the widget tree. While mixing get_it with Bloc is possible, ensuring proper instance creation and lifecycle alignment is essential to maintain predictable state management system.

I post all the articles I read and find interesting myself.

Mobile Experts 👉🏻 https://codigee.com

Codigee

Mixing Bloc with dependency injection tools like get_it requires careful consideration to avoid issues with state management. Using singletons for BLoC can disrupt its lifecycle, causing unexpected state persistence and errors. Instead, use registerFactory to ensure clean state instances. For better integration, use RepositoryProvider for dependencies within the widget tree.

Don't mix bloc with get_it

Same true for get_it + provider. Be sure you understand your state management lifecycles

If a well-known and useful pattern gets in the way of your “whatever management” package, then the last one is not that good, just switch to one that actually gets the job done without you to compromise.

I developed my own dependency injection container with auto-wiring for services, using a code generator: <a href="https://pub.dev/packages/catalyst_builder" target="_blank" rel="noopener nofollow">catalyst_builder</a>.
In general, I recommend treating widgets as transient services, meaning a new instance is created each time the widget is requested.
Treating widgets—or UI components in general—as singletons usually leads to issues. It feels wrong and can cause high memory usage, since the instances stay in memory even when they’re no longer needed.