fix: autoRefresh not working due to stale closure and missing in client config

[ZvonimirBusic]

What?

Fixes autoRefresh functionality that was causing "Stay logged in" modal to appear instead of automatically refreshing the token.

Why?

Two issues were preventing autoRefresh from working:

1. autoRefresh was not exposed in the client config, causing it to be undefined in the browser
2. The Auth provider's reminder timeout callback was capturing a stale autoRefresh value due to closure timing during initial component render

How?

• Added autoRefresh to client config creation to expose it to the client
• Used useEffectEvent in Auth provider to ensure the reminder timeout handler always captures the latest autoRefresh value

Fixes

#14613

[PatrikKozak]

Hey @ZvonimirBusic - thanks for opening this PR!

I was able to validate the original issue however with this fix above, although the autoRefresh is properly exposed to the Auth Provider now, I don't believe the original issue is resolved just yet.

From what I'm seeing:

When a user logs in, the config hasn't fully loaded yet so autoRefresh is undefined. There is a setTimeout callback in the Auth Provider that captures this undefined value in its closure, even though autoRefresh becomes true later, the timeout callback still has the old captured value.

Can you possibly confirm this on your end by running one of our test suites i.e test/_community within this branch and using the configuration as described in the original issue.

I think you'll still see the Stay Logged In modal appear for you.

I can go ahead and push an additional fix here to your branch which should resolve the issue. I just want to make sure that on your end you're still seeing the issue even with exposing the autoRefresh value properly to the provider

[github-actions]

🚀 This is included in version v3.65.0