-
Notifications
You must be signed in to change notification settings - Fork 37
[BUG] ODP is not integrated error is thrown after upgrading from 2.9.2 to 3.1.0 #260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm also seeing the same error log after upgrading. |
I've seen the same error upgrading to v3.1.0. However, you may want to recheck how you set the optimizely = createInstance({
// ...
odpOptions: {
disabled: true
}
}) You should see an Optimizely log saying this if it worked:
|
This is also how I resolved the issue. However, I’d expect ODP to be disabled by default without needing to provide that configuration. |
Disabling the |
Looks like this #262 would resolve the issue |
Thanks for the code review @kimyu92. We're working to get patch out shortly. |
Patch version 3.1.1 is out. An upgrade to 3.1.1 will fix the problem. |
Is there an existing issue for this?
SDK Version
3.1.0
Current Behavior
After upgrading from 2.9.2 to 3.1.0, a "ODP is not integrated" error is consistently thrown after experiment data is loaded:
Expected Behavior
"ODP is not integrated" Error is not thrown when upgrading from 2.9.2 to 3.11.0. If there are API changes that break for v2.9.2 consumers when upgrading, I'd expect a migration guide or instructions on how to handle/configure ODP in the optimizely provider.
https://github.com/optimizely/react-sdk/blob/master/CHANGELOG.md#300---january-24-2024
I've attempted to disable ODP, but the same error is thrown:
Steps To Reproduce
Unfortunately, I cannot afford the time to isolate the source of the error in a simplified project.
React Framework
v18.2.0
Browsers impacted
All that I've tested:
[email protected]
[email protected]
Link
No response
Logs
Severity
No response
Workaround/Solution
Wait to upgrade from v2.9.2 until breaking changes are documented and/or error no longer occurs.
Recent Change
No other changes to Optimizely configuration or data. Only updating the sdk.
Conflicts
No response
The text was updated successfully, but these errors were encountered: