Maximum update depth exceeded issue, while using thunder react sdk

[zesu22]

Description

From version above 0.1.0 of @thunderid/react, if installed and used in our application. It is throwing error in console with Maximum update depth exceeded.

Steps to Reproduce

1. Create any application with react for gate application
2. Install any version above @thunderid/react@>0.1.0 or any latest version
3. Try to use any flowgraph
4. Ran your gate application
5. Check the console, you can see multiple console error, and it is continuously keep coming

Here is the flowgraph which we are using: https://github.com/mosip/esignet/blob/develop-go/esignet-service/data/config/resources/flows/flow-declarative-mosip-otp-1.yaml

Version

@thunderid/react@>0.1.0

Environment Details (with versions)

No response

[brionmario]

Seems like the changes added in the Input Validation PR is triggering a infinite rendering loop.

• Add input validation support to flow components #3301

When i reverted the changes, the stack exceeding error was gone.

FYI @zesu22

[zesu22]

Sure @brionmario i will check from our side then

[webdevelopersrinu]

Hi 👋 I'd like to help fix this. I traced the root cause in @thunderid/react and it's a classic unstable-dependency render loop:

In BaseSignIn.tsx, formFields is rebuilt as a new array on every render (no memoization) and passed to useForm({ fields }). That new identity propagates through useForm:

fields → getFieldConfig ([fields]) → validateField → setTouched — so setTouched gets a new identity every render.

setTouched (aliased setFormTouched) is a dependency of the useEffect that calls clearFormErrors(). Since clearFormErrors() runs unconditionally and does setFormErrors({}) (a fresh object), it forces a re-render → new formFields → new setTouched → effect re-fires → "Maximum update depth exceeded."

Proposed fix: memoize the derived array so its identity is stable:

const formFields = useMemo(
  () => (components ? extractFormFields(components) : []),
  [components],
);

The same unmemoized pattern appears in BaseSignUp and BaseRecovery, so I'll fix all three for consistency and add a repro.

Is anyone actively working on this? If it's open, I'm happy to pick it up and raise a PR.