UNREGISTER_FIELD sync error issue

[iliesalex89]

Starting from version 7.0.2, I discovered that issuess fixed in the past regarding removing sync errors when a field is unregistered are back in current behavior. I think this thing appeared after "Fixed tricky bug with UNREGISTER action not removing deep sync errors. #3219 #3189".

I have now a form with destroyOnMount false and when I'm trying to getFormSyncErrors for fields that are not registered, this is not possible. I think my issue is closely related to issues raised in the recent past like:
"Do not clear errors unless field is being removed from the form #3064"
"[6.7.0] Unregister field shouldn't clean up its sync error if there are multiple fields under this name #2979"

[bharadwajsampath]

Even I have the same issue.
I am unregistering a field but the sync error for that field happens to be present in the reduxForm syncerrors state.

[gustavohenke]

Do you guys still happen to have this issue? If so, can you provide a sandbox that replicates it with the latest version?

[gustavohenke]

Closing due to inactivity.

[mitk0936]

The bug is still reproducible in 7.3.0

[aldoshin]

I tried explicitly dispatching unregisterField(SCHEMA_FORM_NAME, id, true) when the component containing the Field componentWillUnmount and worked seems some issue the way the third parameter destroyOnUnmount is handled

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.