scenario_app build rules doesn't recompile when files are edited

[gaaclarke]

Steps to reproduce:

1. Type garbage into the file at flutter/testing/scenario_app/lib/src/scenarios.dart
2. delete out/ios_debug_sim_unopt/scenario_app/Scenarios/App.framework
3. compile with autoninja -C out/ios_debug_sim_unopt && autoninja -C out/host_debug_unopt/
4. Notice that there was no compilation error
5. Notice that out/ios_debug_sim_unopt/scenario_app/Scenarios/App.framework has been regenerated somehow despite the error

cc @dnfield

[dnfield]

This is jit mode. App.framework is a stub in that case. You should get an error during kernel complication though

[gaaclarke]

Ahh okay, the problem is made worse because the App.framework is used in UI tests which makes it hard to debug problems in the underlying process.

[gaaclarke]

shoot, got so caught up with the other issue I mentioned I forgot that it was off topic from the original issue of not having compilation errors show up.

[gaaclarke]

I suspect the files aren't even getting compiled. Not only am I not getting compilation errors, I'm also seeing the old behavior in spite of changes.

[gaaclarke]

If you touch testing/scenario_app/lib/main.dart it seems to cause a recompilation, touching testing/scenario_app/lib/src/scenarios.dart isn't enough.

[dnfield]

Sounds like a depfile issue. At one point I listed all the sources explicitly but then I thought the depfile would work. @zanderso maybe knows

[dnfield]

So the depfile we're getting from Dart does not contain the application sources. I'm trying to get feedback fromt he Dart team about whether this is WAI or not. If it is we need to list the sources manually, which seems unfortunate.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.