Closed jbrookssmokeball closed 3 months ago
Thank you for bringing this to our attention. I will investigate and respond once completed.
Logged as SC-246089
@jbrookssmokeball , I have been able to reproduce the issue and am investigating the root cause now.
We have opened a PR for the fix and should have that released in the next day or two. PR is here.
Version 5.2.1 has been released with the fix. Thank you for your help!
Description The FlagValueChanged event does not fire on the first event after initializing if
AutoEnvAttributes
is enabled.To reproduce Use the following code to initialize
LdClient
withAutoEnvAttributes
enabled: (updateYOUR_USER_ID
with any LD user's ID andYOUR_KEY
with your SDK key).The
NotifyFlagValueChanged
function looks like:Run the code and make a change to a flag on LaunchDarkly that will change the evaluated value for the user.
Expected behavior The flag change event is received by the client side code.
Actual behavior The first flag change event is not received by the client side code. Subsequent flag change events are received by the client side code.
SDK version LaunchDarkly.ClientSdk 4.0.0
Language version, developer tools C#
OS/platform Windows 11, .NET 6
Additional context If
AutoEnvAttributes
is disabled, then this works as expected. Unable to reproduce on LaunchDarkly.ClientSdk 3.1.0.