Getting Null check operator used on a null value after upgrading to build_runner 2.5.x

[saibotma]

Logs:

Building package executable... (2.3s)
Built build_runner:build_runner.
Creating the asset graph.                                                                                                                                                                                    


You have hit a bug in build_runner
Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues


Null check operator used on a null value
package:build_runner_core/src/asset_graph/graph.dart 127:42          AssetGraph.build.<fn>
dart:_internal                                                       WhereIterator.moveNext
package:build_runner_core/src/asset_graph/graph.dart 255:22          AssetGraph._setDigests
package:build_runner_core/src/asset_graph/graph.dart 126:17          AssetGraph.build
package:build_runner_core/src/generate/build_definition.dart 131:39  _Loader.prepareWorkspace
package:build_runner_core/src/generate/build_series.dart 158:27      BuildSeries.create
package:build_runner_core/src/generate/build_runner.dart 37:7        BuildRunner.create
package:build_runner/src/generate/build.dart 110:17                  build
package:build_runner/src/entrypoint/build.dart 44:18                 BuildCommand._run
package:args/command_runner.dart 212:13                              CommandRunner.runCommand
package:build_runner/src/entrypoint/run.dart 26:18                   run
.dart_tool/build/entrypoint/build.dart 112:44                        main

Dart: 3.7.2
build_runner: 2.5.2
Using: drift_dev 2.26.0, dart_mappable_builder 4.5.0 and riverpod_generator 3.0.0-dev.15
Using macOS

Can not share the project, unfortunately.

[davidmorgan]

Thanks!

I think I see the codepath you're hitting: it's triggered by having previously generated output on disk that also matches as input to a generator. So a workaround should be to delete generated output manually before running. I'll work on a proper fix :)

[davidmorgan]

The fix is released--please reopen or open a new issue if you see any further issues. Thanks!