Ant Design Form failing to sync with asynchronous initialValues

The direct answer

No. Ant Design's Form consumes initialValues only at mount time. Changing the prop after the Form has mounted does not re-evaluate it or update the internal store. This is intentional, documented behavior — not a race-condition bug. If the prop were reactive, every re-render with new data would silently overwrite the user's in-progress edits.

Recommended pattern: setFieldsValue in an effect

The officially supported way to sync async data is to get the form instance via Form.useForm() and push the fetched values in a useEffect:

const [form] = Form.useForm();
const { data } = useQuery(['user', id], fetchUser);

useEffect(() => {
  if (data) {
    form.setFieldsValue(data);
  }
}, [data, form]);

return (
  <Form form={form} onFinish={onSubmit}>
    <Form.Item name="email" label="Email"><Input /></Form.Item>
  </Form>
);

Two facts clear up the common fears about this approach:

• setFieldsValue only writes to the store. It does not trigger validation or onValuesChange, and it does not cause render loops by itself. Loops only happen when the effect's dependencies are unstable — for example, depending on an object literal recreated every render. Depend on the query result or a stable identifier, not on inline objects.
• Never call setFieldsValue during render — only in an effect or event handler.

If you need the injected values validated, call form.validateFields() explicitly afterward.

Declarative alternative: delay or force the mount

If you'd rather stay purely declarative, make the mount coincide with data availability so initialValues is applied fresh:

{data && <Form initialValues={data}>...</Form>}

{/* or force a remount when the record changes */}
<Form key={data?.id ?? 'loading'} initialValues={data}>...</Form>

The trade-off: a remount discards all form state (touched flags, errors, unsaved edits), so it fits "load once, then edit" screens but not forms that receive updates while the user is typing.

Version and edge-case notes

• In antd v5 you can update one field with form.setFieldValue(name, value); v4 has only setFieldsValue. Check your package.json before relying on the singular form.
• If fields mount conditionally, values for unmounted fields may be dropped from the store unless preserve is configured on the Form or Form.Item.
• Partial updates are fine: setFieldsValue with a subset of fields leaves the rest untouched.

How to verify the behavior yourself

1. Mount a Form with empty initialValues, then resolve async data into the prop — confirm the fields stay empty, proving the prop is mount-only.
2. Add a log inside the useEffect calling setFieldsValue and confirm it runs once per data change, not in a loop.
3. Test the remount variant by setting key={data.id} and confirming fields populate on arrival.

One caveat: exact defaults for preserve and the availability of setFieldValue vary across antd 4.x/5.x minor releases, so confirm against your installed version's docs.