Skip to content
Snippets Groups Projects
user avatar
flutteractionsbot authored
**This pull request is opened against a release branch.<br>
To request a cherry pick of a commit, please fill in the form below.** (Questions with an asterisk are required.)<br>

**To fill in the form, you can edit this PR description and type your answers after the 'My Answer' keywords. <br>
A flutter domain expert will evaluate this cherry pick request shortly after ALL questions are answered.**

* Issue Link: What is the link to the issue this cherry-pick is addressing?<br>

<pre>
  <b>My Answer:</b> https://github.com/flutter/flutter/issues/143513
</pre>

* Changelog Description: Explain this cherry pick in one line that is accessible to most Flutter developers
        See https://github.com/flutter/flutter/wiki/Hotfix-Documentation-Best-Practices for examples (Bug fix, feature, docs update, ...)<br>
<pre>
  <b>My Answer:</b> Fixes issue where `flutter test` uses stale assets cached by previous invocations of `flutter test`.
</pre>
* Impacted Users: Approximately who will hit this issue (ex. all Flutter devs, Windows developers, all end-customers, apps using X framework feature)?

<pre>
  <b>My Answer:</b> All end customers using `flutter test` and the assets feature together.
</pre>
* impact_description: What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)? Does it impact development (ex. flutter doctor crashes when Android Studio is installed), or the shipping production app (the app crashes on launch)<br>

<pre>
  <b>My Answer:</b> Updates to assets files my not be reflected on successive runs of `flutter test`.
</pre>
* Workaround: Is there a workaround for this issue?<br>

<pre>
  <b>My Answer:</b>
Do one of the following before running 'flutter test' to force a rebuilding of the asset bundle:
1. Delete the build/unit_test_assets/ directory.
2. Modify the pubspec.yaml file.

</pre>

* Risk: What is the risk level of this cherry-pick?<br>

<pre>
  <b>My Answer:</b>

</pre>

* Test Coverage: Are you confident that your fix is well-tested by automated tests?<br>

<pre>
  <b>My Answer:</b>

</pre>

* Validation Steps: What are the steps to validate that this fix works?<br>

<pre>
  <b>My Answer:</b>
Follow the repro steps mentioned in the original issue and see if the issue is still reproducible.

</pre>
c371bd9b
Name Last commit Last update