React Native
Welcome to the Flagship React Native SDK documentation!
The following article will guide you through the steps to get Flagship up and running on your React Native app using our client library with preconfigured methods to implement the Decision API.
Wants to have a look at the GitHub repo? Link here.
Feel free to contact us if you have any questions regarding this documentation.
Release notes
Improved
- Usage data collection process
Fixed
- Fixed a typo error in the
DecisionMode
property value of the usage tracking hit. - Fixed Intl property error
Updated
- @flagship.io/react-sdk dependency to version 3.3.2
Fixed
- Usage tracking collection issue
Updated
- @flagship.io/react-sdk dependency to version 3.3.1
Added
- Collecting developer usage tracking data:
- The SDK now collects troubleshooting data, which will help us find implementation issues
- The SDK now collects usage data, which will help us improve our product
disableDeveloperUsageTracking
property in config object.- Experience continuity in bucketing mode
Updated
- @flagship.io/react-sdk dependency to version 3.3.0
Added
- campaignName, variationGroupName and variationName in Flag metadata
Updated
- @flagship.io/react-sdk dependency to version 3.2.4
Added
fetchFlagsBufferingTime
props in config object.trackingManagerConfig
props in config object.- New warning logs
Deprecated
trackingMangerConfig
props of config object.
Updated
- @flagship.io/react-sdk dependency to version 3.2.3
Added
qt
field in activate batch. It represents the time delta (in milliseconds) between when the hit reported occurred and the time it was sent.
Updated
- @flagship.io/react-sdk dependency to version 3.2.2
Improved
- SDK logs
Updated
- @flagship.io/react-sdk dependency to version 3.2.0
Added
- Third party integration in bucketing mode
Fixed
- Experience continuous issue
Added
- OnVisitorExposed callback in config object
Deprecated
- onUserExposure property in SDK
- flag.userExposure method
Changed
- logLevel for not-consent mode and panic mode
Updated
- @flagship.io/react-sdk dependency to version 3.1.2
Added
- exports field in package.json
Fixed
- default logs manager timestamp
Updated
- @flagship.io/react-sdk dependency to version 3.1.1
Added
- Hits are now sent with a batch processing system see
- trackingMangerConfig props of FlagshipProvider
- DecisionMode.DECISION_API enum in decisionMode props of FlagshipProvider
- close method in useFlagship hook
Changed
- Interface IHitCacheImplementation
Removed
- activateDeduplicationTime props from FlagshipProvider
Deprecated
- DecisionMode.API use DecisionMode.DECISION_API instead of
Updated
- @flagship.io/react-sdk dependency to version 3.1.0
Added
- onLog props in SDK Config
Updated
- @flagship.io/react-sdk dependency to version 3.0.13
Added
- visitor_consent key in the body of the campaign request
Removed
- sendContextEvent query param from the campaign request
Fixed
- When the envId or apiKey credentials are false / empty / null and the loadingComponent props is set, SDK still shows the loadingComponent instead of child component
Updated
- @flagship.io/react-sdk dependency to version 3.0.12
Added
- onUserExposure property in SDK Config
Updated
- @flagship.io/react-sdk dependency to version 3.0.9
Fixed
- When flag value from Flagship is
false
or0
, Flag.getValue() always returns the default value instead of flag value
Updated
- @flagship.io/react-sdk dependency to version 3.0.8
Changed
- Event hit property value can now only accept an integer and must not be a negative value
Updated
- @flagship.io/react-sdk dependency to version 3.0.7
Fixed
- flagsData property typo issue from FlagsData to flagsData
Updated
- deprecated fields message
- @flagship.io/react-sdk to version 3.0.5
Fixed
- Predefined context OS_VERSION_CODE type issue
Added
- useFlagship().fetchFlags method
- useFlagship().getFlag method
- useFlagship().setConsent method
- useFlagship().authenticate method
- useFlagship().unauthenticate method
- Flag class
- FlagMetadata class
- Managing visitor cache
- SDK Status / Status changed callback.
- Visitor consent.
- Predefined context.
- Custom log manager
Deprecated
- useFlagship().synchronizeModifications method
- useFlagship().getModification method
- useFlagship().getModificationInfo method
- useFlagship().activateModifications method
Changed
- useFlagship().hit.send and useFlagship().hit.sendMultiple signature
removed
- Props enableConsoleLogs of FlagshipProvider
- Props activateNow of FlagshipProvider
- Props enableSafeMode of FlagshipProvider
- Props enableErrorLayout of FlagshipProvider
- Props nodeEnv of FlagshipProvider
Updated
- @flagship.io/react-sdk to version 2.1.11
Fixed
- React-17 and above issue
Updated 6 months ago