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.
This ANE currently requires at least AIR 33+. This is required in order to support versions of Android > 9.0 (API 28). We always recommend using the most recent build with AIR especially for mobile development where the OS changes rapidly.
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.
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:
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.GoogleIdentity
This will download and install the extension, required assets, and all dependencies.
apm will have created something like the following file structure:
| |____ com.distriqt.GoogleIdentity.ane # GoogleIdentity 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 some configuration information from your Google Identity setup. Call the following to step through the configuration values for this extension:
apm project config set com.distriqt.GoogleIdentity
The following guide is used to manually install the extension, download dependencies and update the application descriptor. We highly recommend installing extensions 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.
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.
The Core extension is required by this extension. You must include this extension in your application.
This extension requires you call the
init() function at some point early in your application, generally at the same time as the initialisation of this extension. If you are using other extensions that also require the Core extension, you only need to initialise it once, before initialising the other extensions.
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.
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:
You can access these extensions here: https://github.com/distriqt/ANE-AndroidSupport.
Note: if you have been using the older
com.distriqt.androidsupport.*(Android Support) extensions you should remove these extensions and replace it with the
androidxextensions listed above. This is the new version of the android support libraries and moving forward all our extensions will require AndroidX.
Google Play Services
This extension requires usage of certain aspects of the Google Play Services client library. The client library is available as a series of extensions that you add into your applications packaging options. Each separate extension provides a component(s) from the Play Services client library and are used by different extensions. These client libraries aren't packaged with this extension as they are used by multiple ANEs and separating them will avoid conflicts, allowing you to use multiple extensions in the one application.
This extension requires the following Google Play Services:
You must include the above native extensions in your application along with this extension, and you need to ensure they are packaged with your application.
You can access the Google Play Services client library extensions here: https://github.com/distriqt/ANE-GooglePlayServices.
Note: The Google Play Services and Android Support ANEs are only required on Android devices. There are no issues packaging these extensions with all platforms as there are default implementations available which will allow your code to package without errors however if you are only building an iOS application feel free to remove the Google Play Services and Android Support ANEs from your application.
Due to several of our ANE's using the Square open source libraries the libraries have been separated into a separate ANEs allowing you to avoid conflicts and duplicate definitions. This means that you need to include the some of the square native extensions in your application along with this extension.
You will add these extensions as you do with any other ANE, and you need to ensure it is packaged with your application.
This ANE requires the following Square extensions:
You can access these extensions here: https://github.com/distriqt/ANE-SquareLibs.
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
You should backup your application descriptor before running this command to ensure you don't lose any information.
The following should be added to your
extensions node in your application descriptor to identify all the required ANEs in your application:
Making requests and accessing the Google Identity functionality requires the some additional permissions, so these must also be declared in the manifest. Additionally you will need to add the activities to the manifest as in the section below:
<uses-sdk android:minSdkVersion="19" android:targetSdkVersion="31"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<meta-data android:name="com.google.android.gms.version" android:value="@integer/google_play_services_version" />
Accessing the Google Identity functionality requires some additions to the InfoAdditions on iOS.
This allows callbacks from external applications that may handle signin and sign outs. You should
URL_NAME in the additions with the ones you created when setting
up your application in the Google developer console.
URL_SCHEME should be your reversed ios client id, along the lines of the following:
URL_NAME should be your application identifier, eg:
See the example application for our test application implementation.
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.
// Functionality here