Weird problem formik setting isSubmitting to false while starting a mutation in the submit method

[Jurek-at-work]

Hi, I am in a react 18 project using Formik 2.4.6.

Since a slight refactoring I experience a weird behaviour with the isSubmitting state in a formik form:

The form has a submit handler like this:

const onSubmit = async (values, { setSubmitting, setStatus }) => {
    return new Promise(async (resolve, reject) => {
      try {
        ...
        await signupSubmit.mutateAsync({ values, setSubmitting });
        ...
        resolve();
      } catch (e) {
        ...
        reject();
      }
    }
}

This worked correctly until I moved the Formik container a bit, which shouldn't be a problem... Suddenly formik sets the isSubmitting state to false at the start of the above mutateAsync() call. Directly before this mutate call, the submitting state still is true, but in the first line of the mutation method, the submitting state is false.

My workaround now is to have a setSubmitting(true) in the very first line of the mutation method...

But I have no explanation why the behaviour changed. Is this an intended behaviour, or a bug? Any idea why this is happening? This submit also works as expected otherwise...