Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Provider: Widget Function(BuildContext) can't be assigned to a builder parameter

ErrorThe argument type 'Widget Function(BuildContext)' can't be assigned to the parameter type 'Widget Function(BuildContext, Widget)'

Short answer

Provider builders pass more than the BuildContext. Consumer's builder receives (context, value, child), and the builder on ChangeNotifierProvider is a TransitionBuilder that receives (context, child). A closure with only context has the wrong type. Add the missing parameters, or use create to build the model.

  • Applies to Flutter 3.x stable, provider 6.x
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Find the exact call the analyzer underlines and note whether it is Consumer or a Provider class.

    grep -rnE "Consumer<|ChangeNotifierProvider\(" lib/
  2. 2Match what you see, then jump to its fix

    1. 1The underlined call is Consumer<Model>(builder: (context) => ...)Consumer builder written with one parameterFix
    2. 2The underlined call is ChangeNotifierProvider(builder: (context) => CartModel())ChangeNotifierProvider builder is used as if it built the modelFix
    3. 3Code copied from an old tutorial that passes builder where a model is expectedOld code that used the removed builder parameter on providersFix

What does the error look like?

  • The argument type 'Widget Function(BuildContext)' can't be assigned to the parameter type 'Widget Function(BuildContext, Widget)'
  • Consumer builder with only a BuildContext parameter is rejected by the analyzer

Cause 1 of 3

Consumer builder written with one parameter

1Check

Consumer's builder has the signature Widget Function(BuildContext context, T value, Widget? child).

grep -rn "Consumer<" lib/

2Fix

Take the value (and the child, even if you ignore it with an underscore).

Consumer<CartModel>(
  builder: (context, cart, child) => Text('${cart.count}'),
)

3Verify

The analyzer error disappears.

flutter analyze

Confirmed by pub.dev

Did this fix it?

Cause 2 of 3

ChangeNotifierProvider builder is used as if it built the model

1Check

In provider the model is created by the create parameter. builder is a TransitionBuilder, syntax sugar for getting a BuildContext that can read the new provider. The rename of builder to create dates from provider 4.0.0.

grep -rn "builder:" lib/main.dart

2Fix

Create the model in create. Use builder only when a descendant needs a context below the provider, and give it both arguments.

ChangeNotifierProvider(
  create: (_) => CartModel(),
  builder: (context, child) => const CartScreen(),
)

3Verify

The app starts and context.watch<CartModel>() works inside CartScreen.

flutter run

Confirmed by pub.dev

Did this fix it?

Cause 3 of 3

Old code that used the removed builder parameter on providers

1Check

The changelog for 4.0.0 records that builder of the Provider classes was renamed to create (deprecated in 3.2.0).

flutter pub deps | grep provider

2Fix

Rename builder to create, and change the closure to take a context as before.

// before
ChangeNotifierProvider(builder: (context) => CartModel())
// after
ChangeNotifierProvider(create: (context) => CartModel())

3Verify

The analyzer is clean.

flutter analyze

Confirmed by pub.dev

Did this fix it?

How do I stop it coming back?

  • Let the analyzer, not a tutorial, tell you the builder signature of the provider version in pubspec.lock.
  • Use create for building models and keep builder for the rare case that needs a descendant context.
  • Pass the child argument to Consumer for parts of the tree that do not depend on the model.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Google Play says the app does not support 16 KB memory pages

check_elf_alignment.sh reports UNALIGNED for a library under lib/arm64-v8a

Google Play requires apps that target Android 15 or higher and ship native .so libraries to run on devices with 16 KB memory pages; from 1 February 2027 it will block updates that do not.

5 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.