You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When upgrading from v3 → v4, the SDK stored the datafile in AsyncStorage under the same key (opt-datafile-{sdkKey}) in both versions. However, v4 introduced stricter validation of the datafile format.
On the first launch after the upgrade, v4 would read the v3-format datafile from AsyncStorage, fail validation, and log: ERROR ProjectConfigManager: Datafile is invalid because it is malformed.
Expected Behavior
v4 SDK parses datafile from v3 SDK without errors.
Steps To Reproduce
on v3, initialize the SDK, datafile is saved to storage.
update SDK to v4, reinitialize the app.
React Framework
react-native 0.81.5
Browsers impacted
No response
Link
No response
Logs
ERROR: ProjectConfigManager: Datafile is invalid because it is malformed
Severity
No response
Workaround/Solution
Clean up an existing datafile before fetching a v4 one.
Activity
[-][BUG] <v4 Malformed Datafile>[/-][+][BUG] v4 Malformed Datafile[/+]junaed-optimizely commentedon Sep 7, 2026
Hey Volodymyr Ersteniuk (@versten1uk) , looks like this is a valid issue. Thanks for reporting!
versten1uk commentedon Sep 15, 2026
Md Junaed Hossain (@junaed-optimizely) Thanks for fixing it! When can we expect a new release with this fix included?
junaed-optimizely commentedon Sep 18, 2026
Hey Volodymyr Ersteniuk (@versten1uk), v4.2.1 is out with the fix. Hope that helps!