## The problem

Reported in LaunchDarkly: React Native SDK leads to unexpected `on('change', ...)` calls reverting previous flag evaluations.

## The fix

Upgrade to the React Native SDK release containing the identify-queueing fix (PRs #842 and #867). The root cause was overlapping identify calls producing out-of-order re-evaluations and stale change handlers; the fix queues identifies and disconnects update handlers for closed data sources. The reporter tested the fix and got the expected change events, then upgraded to the released versions and accepted the closure. Also avoid initializing multiple SDK instances on the same environment (the cache is per environment), and you can set `debug: true` in the SDK options to trace identify ordering if problems persist.