-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flutter recognition not working for transitive dependencies #177
Comments
@mosuem do you know how to reproduce this issue? looking into the pubspec.lock will be difficult without a |
even running |
right.. @HosseinYousefi any idea why the jni/jnigen repo might complain about using |
Based on the logs, it seems to be a location problem.
+1
|
@mosuem @HosseinYousefi I tried to reproduce that issue inside a Docker container but this worked as well: https://gist.github.com/devmil/5c4d66e7f5aea38c18a49ac108a3c030 I also checked the health GH runner setup and if I'm not mistaken then it installs the stand-alone dart only if flutter is disabled, right? |
Thanks a lot for the effort in debugging this! Weird error..
Yes, it should only install Flutter in this case. |
@mosuem we could make that flutter / dart decision configurable so that packages could override the decision dart_apitool would make |
Describe the bug
The apitool checks if a package should use
flutter ...
ordart ...
commands by checking the pubspec forflutter
- but this does not work if flutter is a transitive dependency, leading to failures such as this. There, the packagejnigen
depends onjni
which depends onflutter
.At least that is my working assumption on what is going on there. Maybe instead of the
pubspec.yaml
, thepubspec.lock
file should be checked usingpackage:pubspec_lock_parse
?The text was updated successfully, but these errors were encountered: