We have renamed the following APIs:

| Old API | New API |
| ------------------------------|-------------------------------|
| trackEvent | logEvent |
| startTracking | start |
| stopTracking | stop |
| isTrackingStopped | isStopped |
| setCustomerIdAndTrack | startWithCUID |
| validateAndTrackInAppPurchase | validateAndLogInAppPurchase |

And removed the following ones:

- trackAppLaunch -> no longer needed. See new init guide
- sendDeepLinkData -> no longer needed

If you have used 1 of the removed APIs, please check the integration guide for the updated instructions

Supported platforms:

- Android
- iOS 12+

Based on:

- iOS AppsFlyerSDK **v6.14.3**
- Android AppsFlyerSDK **v6.14.0**

Built with:

- SWF-version = 44
- AIR SDK version = 50.2.3

---

If the following was not added automatically please add it to the APP_NAME-app.xml:

```

com.appsflyer.adobeair

```

- On AppsFlyer's dashboard you will need to add "air." prefix to the package name as this is added automatically by Air. For example - an app with the package name "**com.test.android**" , should set the app id on AppsFlyer's Dashboard as "**air.com.test.android**".

- Add the following permissions to Android Manifest (in the app description `APP_NAME-app.xml`):
```

```
- Add the following metatag to Android Manifest within the application tag (in the app description `APP_NAME-app.xml`):
``

As a result, you should see your Manifest like this:


**IMPORTANT If you use AIR SDK < v33.1.1.856**

Due to some limitations in the [ADT](https://help.adobe.com/en_US/air/build/WS5b3ccc516d4fbf351e63e3d118666ade46-7fd9.html)
bundled with AIR SDK < 33.1.1.856, after APK is built it is missing some important files.

To add those files (with the help of **automated** script):

1. Place into single directory of your choice:
- apk file
- keystore that was used to sign the apk
- [af_apk_fix.sh script](https://github.com/AppsFlyerSDK/AdobeAirExtension-AppsFlyer/blob/master/bin/af_apk_fix.sh)

2. Run `./af_apk_fix.sh` and enter requested info when prompted

Here is what the script is doing. In case of any issues you can perform those steps **manually**:

1. Decode the apk using [apktool](https://ibotpeaches.github.io/Apktool/). This will create app_name folder.
`apktool d app_name.apk`
2. Download
the [AppsFlyer SDK jar/aar](https://repo.maven.apache.org/maven2/com/appsflyer/af-android-sdk/6.5.4/af-android-sdk-6.5.4.aar)
of the same version that was used in the apk
3. Extract files `a-` and `b-` from the jar (by renaming jar into a zip) and place them into the folder with the
decompiled apk to `app_name/unknown/com/appsflyer/internal`

4. Edit `apktool.yml` by adding these lines under `unknownFiles:` like in the screenshot below:
```
com/appsflyer/internal/b-: '0'
com/appsflyer/internal/a-: '0'
```


5. Build the apk back (will appear under `app_name/dist` folder)
`apktool b app`

6. Zipalign the apk
`zipalign -p -f -v 4 app_name/dist/app_name.apk app_name/dist/app_name-aligned.apk`

7. Sign the apk
`apksigner sign -v --ks myKeystore.jks --ks-key-alias myKey --out app_name/dist/app_name-aligned-signed.apk app_name/dist/app_name-aligned.apk`

8. Verify signature
`apksigner verify app_name/dist/app_name-aligned-signed.apk`

9. Verify zipalignment
`zipalign -c -v 4 app_name/dist/app_name-aligned-signed.apk`

10. Your apk `app_name/dist/app_name-aligned-signed.apk` is ready to use!

If you use Strict mode ANE, make sure not to call any IDFA related APIs listed below. They are still present in the ActionScript, but will cause an app to crash if invoked.

- `waitForATTUserAuthorization(timeout:int):void;`

---

```
import AppsFlyerInterface;
```

Construct the AppsFlyer interface:

```
private static var appsFlyer: AppsFlyerInterface;
appsFlyer = new AppsFlyerInterface();
```

(Optional) If you want to perform deep linking or access AppsFlyer conversion data from the application, register Conversion Listener:

```
appsFlyer.registerConversionListener();
```

Set the Developer key and iOS app ID and Initialise the SDK:

```
appsFlyer.init("DevKey", "iOSAppID");
```

Initialise session reporting (automatically report app launches and background-to-foreground transitions) with DevKey and iOS app ID:

```
appsFlyer.start("DevKey", "iOSAppID");
```

### Note:
If you don't target iOS as a platform, specifying `iOSAppID` ID is not required

---

**iOS:** Using `URI schemes`. For additional reading on URI schemes in iOS: https://help.adobe.com/en_US/air/build/WSfffb011ac560372f7e64a7f12cd2dd1867-8000.html#WS901d38e593cd1bac354f4f7b12e260e3e67-8000

**More on DeepLinks and AppsFlyer:** [OneLink™ Overview](https://support.appsflyer.com/hc/en-us/articles/115005248543-OneLink-Overview)

---

To explicitly send these IDs to AppsFlyer, developers can use the following APIs and place it before initialising the SDK.

If the app does NOT contain Google Play Services, the IMEI and Android ID are collected by the SDK. However, **apps with Google play services should avoid IMEI collection as this is in violation of the Google Play policy**.

#### Enable / Disable IMEI collection (disabled by default)

```
appsFlyer.setCollectIMEI(bool);
```

#### Manually setting IMEI Data

```
appsFlyer.setImeiData("imeiString");
```

#### Enable / Disable Android ID collection (disabled by default)

```
appsFlyer.setCollectAndroidID(bool);
```

#### Manually setting Android ID Data

```
appsFlyer.setAndroidIdData("AndroidIDString");
```

---

```
appsFlyer.setUserEmails("example@example.com");
```

```
appsFlyer.setCurrency("USD");
```

```
appsFlyer.stop();
```

```
appsFlyer.setDebug(bool);
```

**Important :** do not release the application to the AppStore / Google Play with debug logs enabled.

---