- Check that the SDK instance is created from the correct SDK key (it should be the one for the environment you’re changing in the app or API)
- Check the polling update interval. If it’s large, perhaps the new datafile hasn’t yet been requested.
- You can customize the URL from which the datafile is requested (see specific SDK docs for details on how to configure this).
- External tools can sometimes help (for example, this package global-agent for Node.js allows setting a global proxy for all http requests in a Node.js process).
- Datafile management (and event batching as well) starts a background thread, process, or timer (language / platform dependent).
- To stop the background thread, instances must be closed before being disposed of; otherwise they may leak memory.
- Check for ad blockers or cross-origin request blockers. These could block or modify datafile requests made by the SDK, leading to errors.
- Some messages occur only at the DEBUG level.
Updated over 3 years ago