5.1.0

Added:

• QA Assistant for React Native : Introduced ABTastyQAProvider and useABTastyQA hook to enable QA mode in mobile
  apps. Integrates an event bus with message handling and cleanup logic for seamless QA workflows.
• Forced variation support in QA mode : Added allocation and (un)allocation of forced variations, allowing QA teams
  to manually assign visitors to specific campaign variations.
• visitorVariationState initialization : Properly initialized for both QA and non-QA modes in FlagshipProvider.

Fixed:

• README branding and links updated to reflect current AB Tasty / Flagship identity.

5.0.3

Fixed

• Fixed useFlagship() hook flagsStatus object mutation issue that prevented React's useEffect from detecting changes. The flagsStatus object's properties (status, reason) were being mutated in place rather than creating a new object reference, causing React's shallow comparison in dependency arrays to fail. The object now returns a new reference when inner values change, ensuring proper reactivity.

5.0.2

Fixed

• Segment hit collection: Resolved API format issue in bucketing mode where context values weren't properly serialized as strings, causing hits to be rejected by the collection endpoint

5.0.1

Fixed

• React Native Integration — Resolved compatibility issue between the Flagship SDK and React Intl/FormatJS. The SDK now properly handles conflicts with babel-plugin-formatjs, which was incorrectly identifying SDK objects as incomplete message descriptors, causing "[React Intl] Message Descriptors require an id or defaultMessage" errors.

5.0.0

We're excited to announce Flagship SDK v5.0.0, featuring significant improvements in performance, capabilities, and developer experience across all supported runtime environments.

Added

• Emotion AI Integration — Utilize powerful emotion analysis capabilities to understand user reactions and tailor experiences based on emotional responses, enabling more empathetic and responsive applications.
• Batch Limit for Activate Hits — Implemented a fixed maximum limit on activate hits per batch, significantly reducing network overhead while maintaining analytics accuracy.
• reuseVisitorIds pros which controls whether the SDK saves visitor IDs in local storage for reuse across sessions.

Improved

• Enhanced Tree Shaking — Reduced bundle size through improved code splitting and dependency management, ensuring you only load what you need for your specific implementation.

Changed

• Contextual Segment Hits — In bucketing mode, segment hits are now only sent when the visitor context has been updated, reducing unnecessary network requests and improving performance.
• Naming Clarity — Renamed FetchFlagsStatus to FlagsStatus for improved API clarity and consistency throughout the SDK.

For migration assistance and detailed documentation, please refer to our official documentation.

4.1.0-beta.0

Add

• Emotion AI
• Limit the maximum number of activate hits per batch
• reuseVisitorIds props. If it is set to true, the SDK will save the visitor ID and/or anonymous ID and reuse it for the next session if visitorId is not set, to maintain cross-session visitor experience.

Change

• The Flagship.start method is now asynchronous
• Segment hits in bucketing can be sent only when the visitor context has been updated

4.0.1

Fixed

• Visitor multiple authentication

4.0.0

Add

• QA assistant tool
• Visitor Status
• Flag status
• Visitor.getFlags method
• The onSdkStatusChanged props of FlagshipProvider

Change

• useFsFlag hook
• visitor.getFlag method signature
• Flag.getValue method signature
• ThehasConsented key of visitorData props is now mandatory
• SDK status enum

Remove

• From visitor instance (modifications, getFlagsDataArray, getModificationsArray, getModification, getModificationSync, getModificationInfo, getModificationInfoSync, synchronizeModifications, activateModification, getAllFlagsData, getModificationsForCampaign, and getFlatsDataForCampaign)
• From FlagshipProvider (enableClientCache and statusChangedCallback)

3.3.2

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

3.3.1

Fixed

• Usage tracking collection issue

Updated

• @flagship.io/react-sdk dependency to version 3.3.1