Releases: Kameleoon/client-react
Releases · Kameleoon/client-react
React/React Native SDK 7.5.3
Bug fixes
UserAgent
was not exported from SDK
React/React Native SDK 7.5.2
Bug fixes
Custom Data Condition
now handles index0
properly
React/React Native SDK 7.5.1
Bug fixes
- Multiple
Real Time Update
connections are no longer created Custom Data Condition
now handles all exceptions properly
React/React Native SDK 7.5.0
Bug fixes
- Empty Custom Data is now sending activity tracking event
Features
- Added Cross Device Custom Data Synchronization capabilities
React/React Native SDK 7.4.1
Bug fixes
- The returned function of
useFlush
now sends offline tracking requests even if there's no new data to track. - Timestamps for offline requests are set correctly.
React/React Native SDK 7.4.0
React/React Native SDK 7.3.2
Bug fixes
- Added exports for following types:
client-react
Bug fixes
- Tracking data duplication
client-react
Bug fixes
- Improve error handling for
getRemoteVisitorData
- Visitor code is now validated correctly in every method that uses it.
- Result bundle is now compatible with systems not using
ESM
andCommonJS
. It's minimized and uses code splitting forcrypto-js
sha256
function. - Parameter
revenue
forConversion
is now optional. - Each visitor can now only have one type of associated
Kameleoon Data Type
, except forCustomData
, that a visitor can have one percustomDataIndex
.
Features
- New conditions are now supported:
Device
,Browser
,SDKLanguage
,Page Title
,Page View
,Visitor Code
,Conversion
. See the full list of supported conditions. Browser
now has new optional parameterversion
.flushData
visitorCode
parameter is now optional.- Custom data that is marked as
local only
on Kameleoon Platform is now only used for targeting (not flushed with tracking requests).
client-react
Bug fixes
- Empty visitor code is no more allowed
- Incorrect tracking body upon triggering an experiment