ROOK SDK 4.2.0 LTS: More control, consistent events, and AI Skills

We're releasing , a new stable version of our SDKs focused on giving development teams more control over health data extraction while making integrations easier to implement and maintain.

This release introduces

Alongside this LTS release, ROOK React Native SDK 5.2.0 is also available. It includes the same capabilities introduced with SDK 4.2.0 LTS, with extended compatibility for React Native versions up to 0.83. For implementation details and version-specific changes, review the official ROOK SDK documentation and the React Native SDK changelog.

Previously, ROOK SDK integrations retrieved a predefined historical data window at a client-level.

With SDK 4.2.0 LTS, clients can configure how much historical data should be retrieved from supported Health Kit sources, from .

This provides more flexibility depending on your product experience and data requirements.

Considerations:

The SDK periodically checks the configured historical window so changes can also be reflected for existing users.

: The permission is now included in the SDK manifest. If your app doesn't use extended historical data, you can remove this permission to avoid unnecessary policy requirements when publishing your app. Learn more

Integrating ROOK with AI coding tools is now easier.

Alongside our standard SDK documentation, ROOK now provides designed to give AI coding assistants clearer implementation context.

These resources are available across supported ROOK SDKs, including:

Development teams can provide these files to their preferred AI coding tools to get more contextual assistance with setup, configuration, permissions, synchronization, and common implementation flows.

The goal is simple:

Learn more

We've updated how behave to make them consistent with other cumulative events such as Steps and Calories.

Instead of treating every synchronization as an isolated value, each generated event now represents the .

For example, if hydration data increases throughout the day, subsequent events reflect the updated daily accumulated amount.

This creates a more predictable event model across ROOK and simplifies how applications consume continuously updated daily metrics.

If your application currently processes Hydration or Nutrition events, we recommend reviewing this behavior when migrating to 4.2.0.

Sleep data can continue changing after the first synchronization of the day.

SDK 4.2.0 improves how ROOK detects these updates by periodically checking for changes to previously generated .

When new information is detected for a sleep session, ROOK can process and deliver an updated version of the summary instead of waiting until the following day.

This is particularly useful when the underlying health platform adds or modifies sleep information after the initial synchronization.

It depends on the features your application uses. We recommend reviewing the migration documentation if you process Hydration or Nutrition events, rely on a specific historical data window, and consume updated Sleep Summaries.

Yes. If the configured historical window is increased, the SDK may retrieve additional available historical data for existing users.

No. Updating is optional, but we recommend using a supported LTS version to continue receiving full support and bug fixes.

Each LTS release has its own. After that period, regular maintenance and bug fixes end, although critical or high-impact issues may still be addressed.