startClient not working as expected

[duveborg]

Describe the bug

<FlagProvider startClient={false}>

Providing false here seem to fire network requests to fetch flags. Is that expected?

Steps to reproduce the bug

No response

Expected behavior

No response

Logs, error output, etc.

No response

Screenshots

No response

Additional context

No response

Unleash version

No response

Subscription type

None

Hosting type

None

SDK information (language and version)

No response

[FredrikOseberg]

Describe the bug

<FlagProvider startClient={false}>

Providing false here seem to fire network requests to fetch flags. Is that expected?

Steps to reproduce the bug

No response

Expected behavior

No response

Logs, error output, etc.

No response

Screenshots

No response

Additional context

No response

Unleash version

No response

Subscription type

None

Hosting type

None

SDK information (language and version)

No response

@duveborg

If you are not passing a custom client and on a version less than 4.2.2 it is expected, because it previously only applied if you passed a custom client. In 4.2.2 we merged this PR which also makes this functionality work with passing a config. Be aware that if you are passing a config there is no way to start the client afterwards.