Releases: Countly/countly-sdk-web
Releases · Countly/countly-sdk-web
Countly Web SDK 23.6.2
-
Adding app version information to every request
-
Mitigated an issue where if a long numerical device ID was changed while SDK was running at multiple tabs, it was parsed
Countly Web SDK 23.6.1
- Mitigated an issue where numerical device IDs were parsed at the initialization
Countly Web SDK 23.6.0
- Added a new flag, 'loadAPMScriptsAsync', which can load the APM related scripts automatically for Async implementations
- Adding SDK health check requests after init
- Adding remaining request queue size information to every request
- Fixed a bug where unnecessary device ID merge information was sent to the server
Countly Web SDK 23.2.2
- Default max segmentation value count changed from 30 to 100
Countly Web SDK 23.02.1
- Mitigated an issue that could have caused view IDs to be terminated prematurely when using manual sessions and end_session was called abruptly
Countly Web SDK 23.02.0
- Events are now recorded with an internal ID.
- Mitigated an issue where users could have truncate an internal event key
- Mitigated an issue where SDK was reporting empty scroll values
- Mitigated an issue that caused the device changes, after init, to not reflect on memory
- Fixed a bug where previous session cookie persisted even when the 'clear_stored_id' flag was set to true
Countly Web SDK 22.06.5
- SDK now adds userAgent string to each request to prevent proxy related issues
- Added a method to cancel timed events manually
- Fixed a race condition bug where a recorded event would have the wrong user properties in the drill database on the server. Now event queue is emptied (formed into a request) before recording any user profile changes
Countly Web SDK 22.06.4
- Fixed an issue with remote configs not working without a parameter
Countly Web SDK 22.06.3
- Fixed an issue that arose when sending crashes through a gateway. User agent information is now sent as part of the request.
Countly Web SDK 22.06.2
- ! Minor breaking change ! If no domain whitelist is provided for the heatmaps the SDK will fallback to your server url
- Fixed a bug where heatmap files were susceptible to DOM XSS
- Users can now input their domain whitelist for heatmaps feature during init
- Implementing new Remote Config/AB testing API:
- Added an init time flag to enable/disable new remote config API (default: disabled)
- Added a new call to opt in users to the A/B testing for the given keys
- Added an init time flag to enable/disable automatically opting in users for A/B testing while fetching remote config (with new RC API)(default: enabled)