IssueTracker

Question

Should expect that onValueChange might be called any number of times for the same input?

Background

We have a custom Money TextField. The onValueChange callback parses the text and, if the input is invalid, it vibrates the phone via HapticFeedback. Tests for this component provide a fake HapticFeedback, which simply counts how many times the phone was told to vibrate. These tests ended up being unexpectedly flaky (failing ~2% of the time on CI).

The issue ended up being because onValueChange would occasionally get called twice for the same input (SemanticsNodeInteraction.performTextInput). I've attached the stack traces which show how each onValueChange invocation occurred.