After reading this StackOverflow and https://dart.dev/tools/pub/dependencies#dev-dependencies I'm considering this as proposal as there is not documentation saying that assets from dev dependencies will not be included into the final app bundle.

If you have any reference about that please share the link.
Thank you

Hi, @pedromassangocode I'm not sure why it is a proposal not a bug, if the reason to label this as proposal was documentation,
so far I didn't find any flutter documentation saying anything on how dev_dependencies behave with final app bundle as well. by that reasoning dev_dependencies shouldn't work with flutter at all.

If flutter follows dart documentation on dev_dependencies which means ignoring the package on the final app bundle, then flutter should ignore the assets declared as well.

hi @pedromassangocode Additional findings:

When adding integration_test package to dev_dependencies, GeneratedPluginRegistrant class generate the integration test class as well.

pubspec.yaml

dev_dependencies:
  flutter_test:
    sdk: flutter
  another_package:
    path: another_package
  integration_test:
    sdk: flutter

public final class GeneratedPluginRegistrant {
  public static void registerWith(@NonNull FlutterEngine flutterEngine) {
    flutterEngine.getPlugins().add(new dev.flutter.plugins.integration_test.IntegrationTestPlugin());
  }
}

after checking classes.dex in my release bundle, the IntegrationTestPlugin is included, so basically everything under dev_dependencies is included in the release bundle? I'm not sure how to check if the dart code is included in the release bundle. since there is no documentation mentioning this does it mean it is as per existing behavior? so including integration test in the final release bundle is normal ?

Hi, is there any updates? I am seeing the same issue as well

Up for this issue (sorry for not just reacting), but one use-case that might be quite annoying is: say you have an assets that are only meant to be shipped during development and you don't want that to be included in the release bundle, it won't be possible until some exclusion of assets for production build is done.

Right now there's couple of solution that might work (e.g. using script that deletes some dependency or assets during flutter build, but I'd have to admit that's not pretty.

I'm here because I just discovered that in one of my projects I've been placing essential package references under 'dev_dependencies' this whole time - and yet, my release builds have been running flawlessly. I figure it might have something to do with this

Just curious is there a plugin/package on dev_dependencies that contains large enough assets? Because I have never found a plugin/package that has very large assets on dev_dependencies 🤔

Just curious is there a plugin/package on dev_dependencies that contains large enough assets? Because I have never found a plugin/package that has very large assets on dev_dependencies 🤔↳

Sometimes we want to use certain resources only under debug.

Hi all, adding related issues above. It seemed to occur on other platforms

any update?

We were affected by this issue today. The inclusion of integration_test in dev_dependencies caused a crash in our release build. Very unintuitive, as dev_dependencies was far from the first place we went looking for the cause of a crash in the release build.

As it seems this is actually the way flutter behaves - we basically have no option but to inject the integration test dependencies into the pubspec.yaml as part of the runner script launching the tests. Not optimal.