registerFeatureFlagListener does not fire when a flag changes due to identity changes

[vcarl]

Is this a support request?
no

Describe the bug
A listener registered with registerFeatureFlagListener is not triggered if the value changes due to a client.identify(…) call.

I can work around this by re-registering listeners when we make the identify call, but this was difficult to discover and will complicate our logic.

SDK version
5.0.1

[gwhelanLD]

Hi @vcarl,

Thanks for reporting this issue, we've filed it internally to investigate this and attempt to improve the experience. I think this may also be a point of platform consistency we need to address, which may require updating the native SDKs that this SDK wraps to really resolve this.

Thanks,
@gwhelanLD

[yusinto]

@vcarl is this still an issue? Please update to the latest version 7.1.1 and verify.

[karengrigoryan-sg]

@yusinto still an issue for the version 7.1.1.

[vcarl]

It's been well over a year, and I'm no longer with the company I was with when I discovered this bug.

I do think it's important to say, the specific value of LaunchDarkly to me is simplifying reactivity for real-time feature flagging. Feature flagging without real-time reactivity is not difficult to do in-house, IME. That this bug, in what I view to be the absolute core of why I would want to use LaunchDarkly, has gone so long without being prioritized has led me to specifically recommend not using LD for React Native projects.

[tanderson-ld]

This issue has been fixed in 7.1.5.