# June Update 2025

Check out what we've been doing at Terra over the month of June 2025!

## Backend 💾

### Features

* Added InBody Integration
* Rouvy now returns total calories burnt
* Added separate meals for nutrition data in Google Fit
* Added new micronutrients to Apple Health nutrition data
* Added updating planned workouts continuously (TrainingPeaks / Garmin)

### Bug fixes

* Fixed a bug where Fitbit net calories burnt could be negative
* Fixed an issue where HEALTH\_CONNECT users were not getting deauth webhooks
* Fixed an issue with Komoot where authentications were failing

***

## SDK 📱

### [TerraiOS](ref:reference-ios-sdk)

* Fixed an issue with Sleep where old Watch OS versions (pre REM/CORE/DEEP era) were not getting total in bed time correctly
* Updated Activity Type mapping

### TerraAndroid

* Added manual upload type detection

### Terra React

* Our package now supports Expo plugin from version 1.8.0 onwards

### Terra API SDK Client

* We released a new major version of the [Python SDK](https://github.com/tryterra/terra-client-python) and [Javascript SDK](https://github.com/tryterra/terra-client-js) now powered by [Fern's](https://buildwithfern.com/) SDK generation. These updates deliver significantly enhanced type safety, robust model validation, and improved developer experience across both language ecosystems.

## MCP :desktop:

### Terra Config MCP

* We released [Terra Config MCP](https://github.com/tryterra/terramcp)

### Terra Knowledge MCP

* We released [Terra knowledge MCP](https://github.com/tryterra/terra-knowledge-mcp)

***

## Frontend📺

### Dashboard

* Build with Terra AI!
  * We have released a new product where you can get our AI to integrate Terra directly into your project for you. Check it out [here](https://dashboard.tryterra.co/dashboard/ai)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/changelog/2025/readme-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.