Is there an existing issue for this?
SDK Version
4.0.1
Current Behavior
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.
Recent Change
No response
Conflicts
No response
Is there an existing issue for this?
SDK Version
4.0.1
Current Behavior
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
React Framework
react-native 0.81.5
Browsers impacted
No response
Link
No response
Logs
ERROR: ProjectConfigManager: Datafile is invalid because it is malformedSeverity
No response
Workaround/Solution
Clean up an existing datafile before fetching a v4 one.
Recent Change
No response
Conflicts
No response