duplicate action sent on dismissal when using bindingAction

[joprice]

I'm using a coordinator that derives the state for a few screens from the coordinator's state, using a similar pattern to the Form example. The app has a list that allows drilling into detail screens. The detail screen has a binding action controlling a TextField When dismissing a detail screen, I get errors like

A binding action sent from a view store for binding state defined at ... was not handled.

It seems that an extra binding action call is sent, and I'm not sure if this is a bug or the coordinator is intended to account for this. I can extract a minified example if this doesn't sound like a familiar issue.

[johnpatrickmorgan]

Thanks @joprice, it's not a familiar issue and I tried to reproduce it but I wasn't able to, so a minimal reproduction would indeed be very helpful if you can. Thanks!

[joprice]

Ok, I'll create a repro repo. It might take me a few days as I'm in the weeds with some other issues.