Gert Dreyer

Willing to accept a PR fixing this issue

Please see https://github.com/final-form/react-final-form/issues/130

The use case does make sense, I have a feeling it is achievable already at this stage - have a look at wizards? If you can create a mock-up sandbox...

I have not debugged this behaviour properly but I feel it may be related to the code below when the field is not rendered anymore and touched becomes undefined. https://github.com/final-form/final-form/blob/d20c44be8766b93424e7754fe2629820fd93d21a/src/FinalForm.js#LL616C1-L619C19...

See https://codesandbox.io/s/react-final-form-field-arrays-forked-mx8532?file=/index.js for getting ARRAY_ERROR set correctly on the object.

This is a bug willing to accept a PR that fixes this.

https://github.com/final-form/final-form/commit/33e551f2cbcecb46bd93dde860b3bf39380a31a5 solved a big bug in arrays so I would like to build on those changes instead of rolling back. Is it possible to provide a CodeSandbox of some sort...

I attempted to trigger the error with your Sandbox. Here is a forked version: https://codesandbox.io/s/nervous-grass-dsy7k0?file=/src/App.tsx I thought it may happen when you call focus or change on a field that...

Please see https://github.com/final-form/react-final-form/issues/985#issuecomment-1363973861

Can you please provide a CodeSandbox to replicate the problem?