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.facebook.Core
This will download and install the extension, required assets, and all dependencies.
Once complete apm
will have created something like the following file structure:
.
|____ assets
| |____ ios
| | |____ Frameworks
| | | |____ [dynamic frameworks]
|____ ane
| |____ com.distriqt.facebook.Core.ane # Facebook Core extension
| |____ [dependencies]
|____ apm_packages # cache directory - ignore
|____ project.apm # apm project file
Add the
ane
directory to your IDE. See the tutorials located here on adding an extension to your IDE.You will have an
assets
directory that contains required assets for the installed extensions. You must add the contents of theassets/ios
folder to the root of your iOS application package. (Theios
folder contains aFrameworks
folder with the required iOS dynamic frameworks).
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 some configuration items such as the Facebook application identifier. Call the following to step through the configuration values for this extension:
apm project config set com.distriqt.facebook.Core
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.
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 any of our extensions.
Core.init();
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.
Bolts
The Bolts extension is required by Facebook.
The Bolts extension doesn't provide any functionality in itself but supports some of our other extensions. It contains the Bolts framework.
You can access this extension here: https://github.com/distriqt/ANE-Bolts.
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.appcompat
- androidx.browser
- androidx.cardview
- androidx.core
- androidx.emoji2
- androidx.vectordrawable
- com.android.installreferrer
- com.jetbrains.kotlin
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 theandroidx
extensions listed above. This is the new version of the android support libraries and moving forward all our extensions will require AndroidX.
Application Descriptor
- APM
- Manual
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.facebook.Core</extensionID>
<extensionID>androidx.appcompat</extensionID>
<extensionID>androidx.browser</extensionID>
<extensionID>androidx.cardview</extensionID>
<extensionID>androidx.core</extensionID>
<extensionID>androidx.emoji2</extensionID>
<extensionID>androidx.vectordrawable</extensionID>
<extensionID>com.android.installreferrer</extensionID>
<extensionID>com.jetbrains.kotlin</extensionID>
</extensions>
Android
Manifest Additions
Add the following to your manifest additions in your application descriptor.
Ensure you replace:
APPLICATION_PACKAGE
with 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.- You will need to replace the instances of
FACEBOOK_APP_ID
,FACEBOOK_APP_NAME
andFACEBOOK_CLIENT_TOKEN
with the relevant settings from your Facebook app. See Get Started for details. - Ensure the
\u003
remains in front of the app id and client token (this ensures the value is treated as a string correctly).
<manifest android:installLocation="auto" >
<uses-sdk android:minSdkVersion="19" android:targetSdkVersion="31" />
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="com.google.android.gms.permission.AD_ID" />
<uses-permission android:name="com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE" />
<queries>
<package android:name="com.facebook.katana" />
<provider android:authorities="com.facebook.katana.provider.PlatformProvider" /> <!-- allows app to access Facebook app features -->
<provider android:authorities="com.facebook.orca.provider.PlatformProvider" /> <!-- allows sharing to Messenger app -->
</queries>
<application
android:appComponentFactory="androidx.core.app.CoreComponentFactory"
android:hardwareAccelerated="true">
<meta-data android:name="com.facebook.sdk.ApplicationId" android:value="\u003FACEBOOK_APP_ID"/>
<meta-data android:name="com.facebook.sdk.ClientToken" android:value="\u003FACEBOOK_CLIENT_TOKEN"/>
<meta-data android:name="com.facebook.sdk.AutoInitEnabled" android:value="false"/>
<meta-data android:name="com.facebook.sdk.AutoLogAppEventsEnabled" android:value="false"/>
<meta-data android:name="com.facebook.sdk.AdvertiserIDCollectionEnabled" android:value="false"/>
<activity
android:name="com.facebook.FacebookActivity"
android:configChanges="keyboard|keyboardHidden|screenLayout|screenSize|orientation"
android:theme="@style/com_facebook_activity_theme"
android:exported="false" />
<activity android:name="com.facebook.CustomTabMainActivity" android:exported="false" />
<activity
android:name="com.facebook.CustomTabActivity"
android:exported="true" >
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data
android:host="cct.APPLICATION_PACKAGE"
android:scheme="fbconnect" />
</intent-filter>
</activity>
<provider
android:name="com.facebook.internal.FacebookInitProvider"
android:authorities="APPLICATION_PACKAGE.FacebookInitProvider"
android:exported="false" />
<receiver
android:name="com.facebook.CurrentAccessTokenExpirationBroadcastReceiver"
android:exported="false" >
<intent-filter>
<action android:name="com.facebook.sdk.ACTION_CURRENT_ACCESS_TOKEN_CHANGED" />
</intent-filter>
</receiver>
<receiver
android:name="com.facebook.AuthenticationTokenManager$CurrentAuthenticationTokenChangedBroadcastReceiver"
android:exported="false" >
<intent-filter>
<action android:name="com.facebook.sdk.ACTION_CURRENT_AUTHENTICATION_TOKEN_CHANGED" />
</intent-filter>
</receiver>
</application>
</manifest>
iOS
Dynamic Frameworks
Facebook is based on a dynamic framework so you must include the framework and dependent swift libs in your application for signing by AIR.
To do this create a Frameworks
directory at the top / root level of your application and ensure it is packaged with your AIR application.
If should contain any of the files in the supplied Frameworks
directory (including dylib
and framework
directories) and any of the Facebook SDK components that you are using in your application.
The Core extension requires several frameworks so your Frameworks
directory should contain:
FBAEMKit.framework
FBSDKCoreKit.framework
FBSDKCoreKit_Basics.framework
Info Additions
The Facebook Core extension requires some additions to the iOS section of your application
descriptor XML file. These settings should be added or modified in the InfoAdditions
node,
under the iPhone
node.
Ensure you replace:
- You will need to replace the instances of
FACEBOOK_APP_ID
,FACEBOOK_APP_NAME
andFACEBOOK_CLIENT_TOKEN
with the relevant settings from your Facebook app. See Get Started for details.
This is the required additions for the InfoAdditions section:
<key>MinimumOSVersion</key>
<string>12.2</string>
<key>CFBundleURLTypes</key>
<array>
<dict>
<key>CFBundleURLSchemes</key>
<array>
<!-- Don't remove the 'fb' prefix -->
<string>fbFACEBOOK_APP_ID</string>
</array>
</dict>
</array>
<key>FacebookAppID</key>
<string>FACEBOOK_APP_ID</string>
<key>FacebookClientToken</key>
<string>FACEBOOK_CLIENT_TOKEN</string>
<key>FacebookDisplayName</key>
<string>FACEBOOK_APP_NAME</string>
<!-- OPTIONAL SETTINGS -->
<key>FacebookAutoInitEnabled</key>
<false/>
<key>FacebookAutoLogAppEventsEnabled</key>
<false/>
<key>FacebookAdvertiserIDCollectionEnabled</key>
<false/>
<key>NSAppTransportSecurity</key>
<dict>
<key>NSExceptionDomains</key>
<dict>
<key>facebook.com</key>
<dict>
<key>NSIncludesSubdomains</key>
<true/>
<key>NSThirdPartyExceptionRequiresForwardSecrecy</key>
<false/>
</dict>
<key>fbcdn.net</key>
<dict>
<key>NSIncludesSubdomains</key>
<true/>
<key>NSThirdPartyExceptionRequiresForwardSecrecy</key>
<false/>
</dict>
<key>akamaihd.net</key>
<dict>
<key>NSIncludesSubdomains</key>
<true/>
<key>NSThirdPartyExceptionRequiresForwardSecrecy</key>
<false/>
</dict>
</dict>
</dict>
<!-- Required to check availability and communicate with other Facebook applications -->
<key>LSApplicationQueriesSchemes</key>
<array>
<string>fb</string>
<string>fbapi</string>
<string>fbapi20130214</string>
<string>fbapi20130410</string>
<string>fbapi20130702</string>
<string>fbapi20131010</string>
<string>fbapi20131219</string>
<string>fbapi20140410</string>
<string>fbapi20140116</string>
<string>fbapi20150313</string>
<string>fbapi20150629</string>
<string>fbapi20160328</string>
<string>fbauth</string>
<string>fb-messenger-share-api</string>
<string>fbauth2</string>
<string>fbshareextension</string>
</array>
We also suggest adding the photo usage description string in case you will be sharing photos using the share dialogs:
<key>NSPhotoLibraryUsageDescription</key>
<string>Access to photo library is required to save images and videos.</string>
<key>NSPhotoLibraryAddUsageDescription</key>
<string>Access to photo library is required to save images and videos.</string>