Closed haroldteramotosonos closed 8 months ago
Hi @haroldteramotosonos thanks for raising the ticket. Which initialization approach did you follow? I mean synchronous or asynchronous.
We use synchronous initialization. Apologies for missing that information.
We call the initialize() API like following, which defaults the updateConfigOnNewDatafile
as false
.
client = manager.initialize(context, R.raw.optimizely_bundled_datafile)
I just checked the Swift SDK documentation and I see this in the doc.
If you have datafile polling enabled, the Swift SDK automatically updates when a new datafile is detected to ensure that you are always working with the latest datafile.
However, on the Android documentation, this behavior is not documented. Android Usage Notes
Could this be a documentation error, rather than the software defect?
Hi @haroldteramotosonos, I really appreciate your effort. You are correct. If the datafileDownloadInterval
value is greater than 0, then datafileDownloadEnabled
becomes true, and the SDK automatically downloads the latest data file.
We will update our doc very soon.
Thank you.
Thank you @muzahidul-opti for the clarification! I will close this issue.
Is there an existing issue for this?
SDK Version
3.13.4
Current Behavior
Initializing OptimizelyManager.initialize with
updateConfigOnNewDatafile
set tofalse
is ignored byDefaultDatafileHandler
. DefaultDatafileHandler will still callenableUpdateConfigOnNewDatafile()
regardless of the value ofupdateConfigOnNewDatafile
and updates the configuration when the new datafile is downloaded.Expected Behavior
When
updateConfigOnNewDatafile
set tofalse
, configuration is not updated as stated in the documentation.Steps To Reproduce
updateConfigOnNewDatafile
set tofalse
Expected:
Actual:
Link
No response
Logs
No response
Severity
Minor issue
Workaround/Solution
Workaround that we implemented: Subclass from
DefaultDatafileHandler
and overrode enableUpdateConfigOnNewDatafile() and make it a no-op.Recent Change
No response
Conflicts
No response