# June Updates Check out what we've been doing at Terra over the month of June! ### New Integrations * Added integration with Renpho ### New Features * Added [POST nutrition](https://docs.tryterra.co/reference/post-nutrition-data) endpoint. Only implemented for Fitbit at the current time. * Added support for the nutrition endpoint to the Google Fit REST API integration ### Improvements * Completely rewrite the Garmin payload handler system to improve performance, maintainability, and query-ability * Completely rewrite the Polar daily data handler system to prevent extreme ratelimiting which was causing some users to never have data sent * Minor database optimisations to prevent various endpoints timing out prematurely * Changed authentication success/failure webhooks to run syncronously before being sent to the queue if a retry is necessary to prevent delays due to queue backlog ### Bugfixes * Minor fixes for authentication redirect URLs not being processed correctly under certain conditions * Fixed some fields not being correctly populated for the data generator * Fixed Garmin activity end time sometimes being before the end of the activity if it was paused at any point during the workout * Fixed Cronometer data sometimes not being sent as scheduled * Fix sensor activation time for freestyle libre being normalised incorrectly * Fix payload upload to s3 system sending webhooks with an incorrect HMAC signature header * Fix small normalisation bugs with various providers * Improve various webhook handlers which would sometimes not send data to all applicable users * Fix incorrect time normalisation for Fitbit causing the wrong timezones to be set ### [TerraiOS](https://docs.tryterra.co/reference/terra-ios-package) * Add ability to get data from Freestyle Libre Pro sensors using NFC * Add ability to activate Freestyle Libre 2 sensors over NFC * Added ability to use single-use authentication tokens when creating new SDK users in order to prevent your API key from being exposed * Background scheduler tasks have been added to ensure that no data will be missed even when the app has not been opened for longer than a day * Custom read and write permissions for Apple Health * Add facilities for the uploading of nutrition data to Apple Health * Mindfulness Data added ### [TerraRTiOS](https://docs.tryterra.co/reference/terrartios) * New iOS SDK that streams data in real time through our Websocket API * BLE Connection to heart rate monitor straps including Polar, Wahoo and more * BLE support for Xiaomi bands to allow streaming of heart rate, calories, steps, and distance * Bluetooth connection widget provided for easy BLE connection ### [TerraAndroid](https://docs.tryterra.co/reference/terraandroid-1) * Add ability to get data from Freestyle Libre Pro sensors using NFC * Add ability to activate Freestyle Libre 2 sensors over NFC * Added ability to use single-use authentication tokens when creating new SDK users in order to prevent your API key from being exposed * A Service class is used for the data scheduler to ensure the app can still send data even when not in the foreground. * Package distributed to the Maven central repository to improve ease of installation ### [TerraRTAndroid](https://docs.tryterra.co/reference/terrartandroid) * BLE support for Xiaomi bands to allow streaming of heart rate, calories, steps, and distance * Bluetooth Connection Widget provided for easy BLE connection ### [TerraFlutter](https://docs.tryterra.co/reference/flutter-sdk) * Flutter support for iOS and Android using TerraiOS and TerraAndroid * Installation through flutter pub from a single command --- # 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/general-updates/june-updates.md?ask= ``` 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.