Add the Extension
The simplest way to install and manage your AIR native extensions and libraries is to use the AIR Package Manager (apm). We highly recommend using apm, as it will handle downloading all required dependencies and manage your application descriptor (Android manifest additions, iOS info additions etc).
However you can choose to install it manually, as you would have done in the past.
Install
- APM
- Manual
Note: All of the commands below should be run in a terminal / command prompt in the root directory of your application, generally the level above your source directory.
If you don't have an APM project setup, expand the guide below to setup an APM project before installing the extension.
Setup APM
Install APM
If you haven't installed apm follow the install guide on airsdk.dev.
Setup an APM project
You will need an APM project for your application.
There are many ways to do this and for more options see the APM documentation. Here we will just initialise a new empty project:
apm init
Check your github token
We use github to secure our extensions so you must have created a github personal access token and configured apm to use it.
To do this create a token using this guide from github and then set it in your apm config using:
apm config set github_token ghp_XXXXXXXXXXXXXXXXXXXXXXXXXXXX
If you don't do this correctly you may find the install will fail.
Install the extension
Install the extension by running:
apm install com.distriqt.Health
If you are looking to use Google Fitness use the com.distriqt.Health-Fitness variant to ensure the dependencies for Google Fitness are installed.
This will download and install the extension, required assets, and all dependencies.
Once complete apm will have created something like the following file structure:
.
|____ ane
| |____ com.distriqt.Health.ane # Health extension
| |____ [dependencies]
|____ apm_packages # cache directory - ignore
|____ project.apm # apm project file
- Add the
anedirectory to your IDE. See the tutorials located here on adding an extension to your IDE.
We suggest you use the locations directly in your builds rather than copying the files elsewhere. The reason for this is if you ever go to update the extensions using apm that these updates will be pulled into your build automatically.
- You will need to set the configuration values for usage in the extension. Call the following to step through the configuration values for this extension:
apm project config set com.distriqt.Health
Google Fitness
If you are using Google Fitness, you will need to install the com.distriqt.Health-Fitness variant of the extension. This will ensure that the required dependencies for Google Fitness are installed.
The default com.distriqt.Health variant does not include the Google Fitness dependencies.
apm install com.distriqt.Health-Fitness
You must only install one of the variants, either com.distriqt.Health or com.distriqt.Health-Fitness, not both.
The following guide is used to manually install the extension, download dependencies and update the application descriptor. We highly recommend installing extensions using apm. Using apm will automate the installation and automatically handle updates and dependencies along with greatly simplifying the application descriptor generation.
First step is always to add the extension to your development environment. Download the extension from the repository and then follow the tutorial located here to add the extension to your development environment.
Dependencies
Many of our extensions use some common libraries, for example, the Android Support libraries.
We have to separate these libraries into separate extensions in order to avoid multiple versions of the libraries being included in your application and causing packaging conflicts. This means that you need to include some additional extensions in your application along with the main extension file.
You will add these extensions as you do with any other extension, and you need to ensure it is packaged with your application.
Core
The Core extension is required by this extension. You must include this extension in your application.
The Core extension doesn't provide any functionality in itself but provides support libraries and frameworks used by our extensions. It also includes some centralised code for some common actions that can cause issues if they are implemented in each individual extension.
You can access this extension here: https://github.com/distriqt/ANE-Core.
Android Support
The Android Support libraries encompass the Android Support, Android X and common Google libraries.
These libraries are specific to Android. There are no issues including these on all platforms, they are just required for Android.
This extension requires the following extensions:
androidx.appcompatandroidx.coreandroidx.emoji2androidx.vectordrawablecom.google.guavacom.jetbrains.kotlin
You can access these extensions here: https://github.com/distriqt/ANE-AndroidSupport.
If you are supporting Health Connect, you will need the following additional extensions:
If you are supporting Google Fitness, you will need the following additional extensions:
You will need to install the GoogleIdentity extension and sign in your user.
Application Descriptor
- APM
- Manual
Android Gradle Version
We have updated the required gradle version used to build your application to be higher than the default AIR currently uses (April 2025).
To specify a higher version add the following to your android node in your application descriptor:
<android>
<gradleVersion>8.9</gradleVersion>
<androidGradlePluginVersion>8.7.3</androidGradlePluginVersion>
...
</android>
If you don't do this you will see the following error when building your application:
Unexpected failure: Unable to run java: com.adobe.air.ADTException: gradle tool failed:
FAILURE: Build failed with an exception.
...
> BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 65
June 2025: This is not currently automatically handled by apm so you will need to add this manually to your application descriptor.
We are working on an update to handle this.
Add Android Permissions
You will need to add the Android permissions to your android manifest for the health data you require access to.
Firstly, generate an apm config for android:
apm generate config android
Then edit the file created at config/android/AndroidManifest.xml and add in the required permissions,
for example, to read and write the step data you need the following permissions:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools">
<uses-sdk android:minSdkVersion="26" android:targetSdkVersion="34" />
<!-- Health Connect Permissions -->
<uses-permission android:name="android.permission.health.READ_STEPS"/>
<uses-permission android:name="android.permission.health.WRITE_STEPS"/>
<!-- Google Fitness Permissions -->
<uses-permission android:name="android.permission.ACTIVITY_RECOGNITION"/>
</manifest>
Create Application Descriptor
Updating your application descriptor will insert the required extensionID's and generate the manifest and info additions for your application.
You update your application descriptor by running:
apm generate app-descriptor src/MyApp-app.xml
Change the path (src/MyApp-app.xml) to point to your application descriptor.
This will modify your application descriptor replacing the manifest additions and info additions with the ones generated from apm.
You should backup your application descriptor before running this command to ensure you don't lose any information.
If you need to insert custom data into these sections see the guides for Android and iOS
Extension IDs
The following should be added to your extensions node in your application descriptor to identify all the required ANEs in your application:
<extensions>
<extensionID>com.distriqt.Core</extensionID>
<extensionID>com.distriqt.Health</extensionID>
<extensionID>androidx.appcompat</extensionID>
<extensionID>androidx.core</extensionID>
<extensionID>androidx.emoji2</extensionID>
<extensionID>androidx.vectordrawable</extensionID>
<extensionID>com.google.guava</extensionID>
<extensionID>com.jetbrains.kotlin</extensionID>
<!-- If you are using Health Connect, you will need this extension -->
<extensionID>androidx.healthconnect</extensionID>
<!-- If you are using Google Fitness, you will need this extension -->
<extensionID>com.distriqt.playservices.Fitness</extensionID>
</extensions>
iOS
Info Additions
The following additions are for the InfoAdditions node of the iPhone section in your application descriptor:
<InfoAdditions><![CDATA[
<key>MinimumOSVersion</key>
<string>12.0</string>
<key>UIRequiredDeviceCapabilities</key>
<array>
<string>healthkit</string>
</array>
<key>NSHealthUpdateUsageDescription</key>
<string>App needs permission to save samples to the HealthKit store</string>
<key>NSHealthShareUsageDescription</key>
<string>App needs permission to read samples from the HealthKit store</string>
]]></InfoAdditions>
Entitlements
The following additions are for the Entitlements node of the iPhone section in your application descriptor:
<Entitlements><![CDATA[
<key>com.apple.developer.healthkit</key>
<true/>
<key>com.apple.developer.healthkit.access</key>
<array>
<string>health-records</string>
</array>
]]></Entitlements>
Android
Manifest Additions
The Health extension requires a few additions to the manifest to be able to start certain activities. You should add the listing below to your manifest.
Ensure you replace:
APPLICATION_PACKAGEwith your AIR application's Java package name, something likeair.com.distriqt.test. Generally this is your AIR application id prefixed byair.unless you have specified no air flair in your build options.
<manifest android:installLocation="auto">
<uses-permission android:name="android.permission.INTERNET"/>
<uses-sdk android:minSdkVersion="26" android:targetSdkVersion="34"/>
<queries>
<package android:name="com.google.android.apps.fitness"/>
<package android:name="com.google.android.apps.healthdata"/>
</queries>
<application>
<activity
android:name="com.distriqt.extension.health.PermissionsRationaleActivity"
android:exported="true"
android:enabled="true">
<intent-filter>
<action android:name="androidx.health.ACTION_SHOW_PERMISSIONS_RATIONALE" />
</intent-filter>
</activity>
<activity-alias
android:name="ViewPermissionUsageActivity"
android:exported="true"
android:targetActivity="com.distriqt.extension.health.PermissionsRationaleActivity"
android:permission="android.permission.START_VIEW_PERMISSION_USAGE">
<intent-filter>
<action android:name="android.intent.action.VIEW_PERMISSION_USAGE" />
<category android:name="android.intent.category.HEALTH_PERMISSIONS" />
</intent-filter>
</activity-alias>
<activity android:name="com.distriqt.core.auth.AuthorisationActivity" android:exported="false" android:theme="@android:style/Theme.Translucent.NoTitleBar"/>
</application>
</manifest>
Android Gradle Version
We have updated the required gradle version used to build your application to be higher than the default AIR currently uses (April 2025).
To specify a higher version add the following to your android node in your application descriptor:
<android>
<gradleVersion>8.9</gradleVersion>
<androidGradlePluginVersion>8.7.3</androidGradlePluginVersion>
...
</android>
If you don't do this you will see the following error when building your application:
Unexpected failure: Unable to run java: com.adobe.air.ADTException: gradle tool failed:
FAILURE: Build failed with an exception.
...
> BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 65
June 2025: This is not currently automatically handled by apm so you will need to add this manually to your application descriptor.
We are working on an update to handle this.
Permissions
In addition to the above you will need to add the permissions for the health data you require access to.
With Health Connect, to read and write the step data you need the following permissions:
<uses-permission android:name="android.permission.health.READ_STEPS"/>
<uses-permission android:name="android.permission.health.WRITE_STEPS"/>
With Google Fitness, you will need the following permission:
<uses-permission android:name="android.permission.ACTIVITY_RECOGNITION"/>
Checking for Support
You can use the isSupported flag to determine if this extension is supported on the current platform and device.
This allows you to react to whether the functionality is available on the device and provide an alternative solution if not.
if (Health.isSupported)
{
// Functionality here
}