docs: consolidate 6.x to 7.0.0 migration guide, deslop integration docs

MIGRATION.md's three overlapping lists (callback-removal prose, symbol table, alignment table) are replaced by one alphabetical Full API change reference table covering every affected symbol, plus a TOC and a tightened LLM-assistant prompt. Docs/RN_API.md gets an upgrading-from-6.x callout linking to MIGRATION.md, and its links into MIGRATION.md are repointed from anchors that never existed (table rows have no anchor) to real headings. The remaining Docs/*.md files get formatting cleanup and removal of stale 6.x-era examples, continuing the RPC-to-Plugin-API alignment doc pass from the previous commit.

Author: al-af

Docs/RN_API.md

@@ -19,7 +19,7 @@ Through a dedicated SDK API: Developers can pass Google's required consent data
 A CMP compatible with TCF v2.2/2.3 collects DMA consent data and stores it in NSUserDefaults (iOS) and SharedPreferences (Android). To enable the SDK to access this data and include it with every event, follow these steps:
 
 1. Call `appsFlyer.enableTCFDataCollection(true)`
-2. `init(devKey, appId)` and register listeners as usual (see [Initialization Flow](RN_API.md#initialization-flow)) — 7.0.0 always requires an explicit `start()` call, so there is no separate "manual start" mode to opt into.
+2. `init(devKey, appId)` and register listeners as usual (see [Initialization Flow](RN_API.md#initialization-flow)).
 3. Use the CMP to decide if you need the consent dialog in the current session to acquire the consent data. If you need the consent dialog move to step 4; otherwise move to step 5
 4. Get confirmation from the CMP that the user has made their consent decision and the data is available in NSUserDefaults/SharedPreferences
 5. Call `appsFlyer.start()` from inside `registerSessionReadyListener`'s callback, after the CMP decision is resolved
@@ -51,17 +51,18 @@ useEffect(() => {
 
 If your app does not use a TCF v2.2/2.3-compatible CMP, you must manually provide the consent data using the SDK API.
 
-How to Set Consent Data: </br>
-1.	Determine GDPR Applicability:
-    *	If GDPR applies, check whether consent data is already stored.
-    *	If not stored, show a consent dialog to obtain user consent.
-2.	Create an AppsFlyerConsent object with the relevant parameters.
-3.	Pass the consent data to the SDK using appsFlyer.setConsentData(consentData) inside `registerSessionReadyListener`'s callback, before calling `start()`.
-4.	Initialize the SDK with `appsFlyer.init(devKey, appId)` (see [Initialization Flow](RN_API.md#initialization-flow)).
+How to Set Consent Data:
+
+1. Determine GDPR Applicability:
+   - If GDPR applies, check whether consent data is already stored.
+   - If not stored, show a consent dialog to obtain user consent.
+2. Create an AppsFlyerConsent object with the relevant parameters.
+3. Pass the consent data to the SDK using appsFlyer.setConsentData(consentData) inside `registerSessionReadyListener`'s callback, before calling `start()`.
+4. Initialize the SDK with `appsFlyer.init(devKey, appId)` (see [Initialization Flow](RN_API.md#initialization-flow)).
 
 #### Setting Consent Data for Users
 
-<b>When GDPR Applies</b>
+##### When GDPR Applies
 
 If GDPR applies to the user, create an AppsFlyerConsent object with the user’s preferences.
 ```javascript
@@ -86,29 +87,16 @@ useEffect(() => {
 }, []);
 ```
 
-<b>When GDPR Does Not Apply</b>
-
-If GDPR does not apply to the user, simply mark it as such in the AppsFlyerConsent object.
-```javascript
-import appsFlyer, { AppsFlyerConsent } from 'react-native-appsflyer';
-
-useEffect(() => {
-    appsFlyer.init('UxXxXxXxXd', '41*****44').then(
-        res => console.log(res),
-        err => console.log(err)
-    );
-    appsFlyer.enableDebug(true);
+##### When GDPR Does Not Apply
 
-    appsFlyer.registerSessionReadyListener(() => {
-        // GDPR does not apply to the user
-        const consentData = new AppsFlyerConsent(false);
+If GDPR does not apply to the user, simply mark it as such in the AppsFlyerConsent object. Use the same initialization flow as above, but with a different consent constructor call:
 
-        // Send consent data to the SDK
-        appsFlyer.setConsentData(consentData);
+```javascript
+// GDPR does not apply to the user
+const consentData = new AppsFlyerConsent(false);
 
-        appsFlyer.start();
-    });
-}, []);
+appsFlyer.setConsentData(consentData);
+appsFlyer.start();
 ```
 
 ### Consent Object API
@@ -134,17 +122,8 @@ const consent2 = new AppsFlyerConsent(true, false, false, false);
 // Non-GDPR user
 const consent3 = new AppsFlyerConsent(false);
 
-// AppsFlyerConsent object support the following cases if they are needed.
+// Partial consent (only GDPR flag, other parameters optional)
 const consent4 = new AppsFlyerConsent(true);
-const consent5 = new AppsFlyerConsent(true, true);
-const consent6 = new AppsFlyerConsent(null, true, true, true);
-const consent7 = new AppsFlyerConsent(true, null, true, true);
-const consent8 = new AppsFlyerConsent(true, true, null, true);
-const consent9 = new AppsFlyerConsent(true, true, true, null);
-const consent10 = new AppsFlyerConsent(true, true, false, true);
-const consent11 = new AppsFlyerConsent(false, true, false, false);
-const consent12 = new AppsFlyerConsent(null, null, null, null);
-const consent13 = new AppsFlyerConsent();
 ```
 
 ### Removed API

Docs/RN_CMP.md

@@ -36,6 +36,18 @@ public class MainActivity extends ReactActivity {
  }
 ```
 
+**Cold-start deep links**: The native SDK inspects the launch Intent only after `init()` completes. For cold-start deep links (app not running when link is clicked), re-deliver them via `Linking.getInitialURL()` and `appsFlyer.performDeepLinking()` inside `init().then()`:
+
+```javascript
+appsFlyer.init(devKey, appId)
+  .then(async () => {
+    const url = await Linking.getInitialURL();
+    if (url) {
+      await appsFlyer.performDeepLinking(url, true);
+    }
+  });
+```
+
 ### App Links
 First, you need to generate SHA256 fingerprint, then add the following intent-filter to the relevant activity in your app’s manifest:
 ```xml
@@ -49,9 +61,11 @@ First, you need to generate SHA256 fingerprint, then add the following intent-fi
         android:scheme="https" />
 </intent-filter>
 ```
-For more on App Links check out the guide [here](https://dev.appsflyer.com/hc/docs/dl_android_init_setup#procedures-for-android-app-links).
+See the [guide](https://dev.appsflyer.com/hc/docs/dl_android_init_setup#procedures-for-android-app-links) for App Links setup.
 
 ### URI Scheme
+A URI scheme is a URL that leads users directly to the mobile app. When an app user enters a URI scheme in a browser address bar or clicks on a link based on a URI scheme, the app launches and the user is deep-linked.
+
 In your app’s manifest add the following intent-filter to your relevant activity:
 ```xml 
 <intent-filter>
@@ -64,10 +78,10 @@ In your app’s manifest add the following intent-filter to your relevant activi
         android:scheme="afshopapp" />
 </intent-filter>
 ```
-For more on URI Scheme check out the guide [here](https://dev.appsflyer.com/hc/docs/dl_android_init_setup#procedures-for-uri-scheme).
+For URI Scheme setup, see the [guide](https://dev.appsflyer.com/hc/docs/dl_android_init_setup#procedures-for-uri-scheme).
 
 ##  iOS Deeplink Setup
-In order to record retargeting and use the `registerDeepLinkListener`/UDL callback in iOS (`onAppOpenAttribution` was removed in 7.0.0 and merged into `registerDeepLinkListener` — see MIGRATION.md), the app needs to forward opened URLs / Universal Links / cold-start launch options to the native SDK. This is done entirely in your app's native **AppDelegate** — there is no JavaScript API for this (`handleOpenURL`/`handleOpenUrl`/`continueUserActivity`/`handleLaunchOptions` are not exposed by this plugin's JS surface):
+In order to record retargeting and use the `registerDeepLinkListener`/UDL callback in iOS (`onAppOpenAttribution` was removed in 7.0.0 and merged into `onDeepLink`, which was later renamed to `registerDeepLinkListener` — see MIGRATION.md), the app needs to forward opened URLs / Universal Links / cold-start launch options to the native SDK. This is done entirely in your app's native **AppDelegate** — there is no JavaScript API for this (`handleOpenURL`/`handleOpenUrl`/`continueUserActivity`/`handleLaunchOptions` are not exposed by this plugin's JS surface):
 
 ```swift
 import AppsFlyerLib
@@ -94,7 +108,7 @@ func application(_ application: UIApplication,
 
 `AppsFlyerLib` is already available as a transitive dependency of this plugin (via the vendored `AppsFlyerRPC` pod) — no extra `pod` entry is needed to `import AppsFlyerLib` in your own AppDelegate.
 
-**Expo apps**: the `openURL`/`continueUserActivity` forwarding above is auto-injected into your generated AppDelegate by this plugin's config plugin at `expo prebuild` time (see [Expo Deep Link Integration](/Docs/RN_ExpoDeepLinkIntegration.md)) — you don't need to add it by hand. `handleLaunchOptions` isn't auto-injected yet; add it manually if you need cold-start launch options forwarded.
+**Expo apps**: the `openURL`/`continueUserActivity` and `handleLaunchOptions` forwarding above is auto-injected into your generated AppDelegate by this plugin's config plugin at `expo prebuild` time (see [Expo Deep Link Integration](/Docs/RN_ExpoDeepLinkIntegration.md)) — you don't need to add it by hand for either ObjC or Swift AppDelegate templates.
 
 ### Universal Links
 Universal Links link between an iOS mobile app and an associate website/domain, such as AppsFlyer’s OneLink domain (xxx.onelink.me). To do so, it is required to:
@@ -115,12 +129,9 @@ Universal Links link between an iOS mobile app and an associate website/domain,
 </plist>
 ```
 
-For more on Universal Links check out the guide [here](https://dev.appsflyer.com/hc/docs/dl_ios_init_setup#procedures-for-ios-universal-links).
+For more on Universal Links, check the [guide](https://dev.appsflyer.com/hc/docs/dl_ios_init_setup#procedures-for-ios-universal-links).
 
 ### URI Scheme
-A URI scheme is a URL that leads users directly to the mobile app.
-When an app user enters a URI scheme in a browser address bar box, or clicks on a link based on a URI scheme, the app launches and the user is deep-linked.
-
 To configure it you will have to:
 
 1. Add a unique url identifier in the URL types entry in the app's `info.plist`
@@ -149,4 +160,4 @@ example of a URL scheme configuration in the `info.plist`:
 </plist>
 ```
 
-For more on URI Scheme check out the guide [here](https://dev.appsflyer.com/hc/docs/dl_ios_init_setup#procedures-for-uri-scheme).
+For URI Scheme configuration, see the [guide](https://dev.appsflyer.com/hc/docs/dl_ios_init_setup#procedures-for-uri-scheme).

Docs/RN_DeepLinkIntegrate.md

@@ -10,12 +10,6 @@ hidden: false
 
 ESP (Email Service Provider) support allows AppsFlyer to handle deep links that are wrapped by email service providers. When users click links in emails, ESP services often wrap the original URL with their own tracking domains. This can break deep linking functionality. ESP support resolves these wrapped URLs to extract the original deep link.
 
-### How ESP Works:
-1. **Email Campaign**: Your email contains a deep link to your app
-2. **ESP Wrapping**: Email provider wraps your link with their tracking domain
-3. **User Clicks**: User clicks the wrapped link from their email
-4. **ESP Resolution**: AppsFlyer resolves the wrapped URL to get the original link
-5. **Decision**: If original link is a OneLink → continue deep linking; if web URL → open in browser
 
 ## 🚀 Prerequisites
 
@@ -106,7 +100,7 @@ public class AppDelegate: ExpoAppDelegate {
 }
 ```
 
-See [Deep linking integration](RN_DeepLinkIntegrate.md#ios-deeplink-setup) for the full native pattern (this plugin's Expo config plugin auto-injects the `openURL`/`continueUserActivity` calls above at `expo prebuild` time — `handleLaunchOptions` is not auto-injected yet).
+See [Deep linking integration](RN_DeepLinkIntegrate.md#ios-deeplink-setup) for the full native pattern (this plugin's Expo config plugin auto-injects the `openURL`/`continueUserActivity` and `handleLaunchOptions` calls above at `expo prebuild` time).
 
 ---
 
@@ -243,17 +237,15 @@ import appsFlyer from 'react-native-appsflyer';
  * This MUST be called before AppsFlyer SDK initialization
  */
 const configureESPDomains = () => {
-  console.log('🔗 Configuring ESP domains:', ESP_DOMAINS);
+  console.log('Configuring ESP domains:', ESP_DOMAINS);
 
-  appsFlyer.setResolveDeepLinkURLs(
-    ESP_DOMAINS,
-    (result) => {
-      console.log('✅ ESP domains configured successfully:', result);
-    },
-    (error) => {
-      console.error('❌ ESP domain configuration failed:', error);
-    }
-  );
+  appsFlyer.setResolveDeepLinkURLs(ESP_DOMAINS)
+    .then((result) => {
+      console.log('ESP domains configured successfully:', result);
+    })
+    .catch((error) => {
+      console.error('ESP domain configuration failed:', error);
+    });
 };
 ```
 
@@ -266,11 +258,11 @@ const configureESPDomains = () => {
  * Main ESP deep link handler
  */
 const handleEspDeepLink = useCallback((deepLinkData: any) => {
-    console.log('🔗 Deep Link Received:', deepLinkData);
+    console.log('Deep Link Received:', deepLinkData);
 
     // Simply stringify and display the entire deep link data
     const formattedData = JSON.stringify(deepLinkData, null, 2);    
-    console.log('📱 Deep Link Data:', formattedData);
+    console.log('Deep Link Data:', formattedData);
 
     let actualDeepLinkData = deepLinkData;
 
@@ -320,8 +312,7 @@ const handleEspDeepLink = useCallback((deepLinkData: any) => {
                     } else {
                       console.log('[AFSDK] The ESP link is NOT a OneLink link. It will be opened in a browser');
                       console.log('[AFSDK] ESP marks to divert the link to the browser');
-                      console.log('URL to open:', espUrl.toString());                
-                      console.log('📱 Would open in browser:', espUrl.toString());
+                      console.log('URL to open:', espUrl.toString());
                     }
                   } else {
                     console.log('[AFSDK] No host found in the ESP URL');
@@ -345,10 +336,10 @@ const handleEspDeepLink = useCallback((deepLinkData: any) => {
         }
       } else {
         console.log('[AFSDK] The original_link is not found');
-        console.log('📋 Regular Deep Link Data:', actualDeepLinkData.data);
+        console.log('Regular Deep Link Data:', actualDeepLinkData.data);
       }
     }
-  });
+  }, []);
 ```
 
 ### Step 4: SDK Initialization with ESP
@@ -360,7 +351,7 @@ import { useEffect } from 'react';
 import { Platform } from 'react-native';
 
 const initializeAppsFlyer = () => {
-  console.log('🚀 Initializing AppsFlyer with ESP support...');
+  console.log('Initializing AppsFlyer with ESP support...');
 
   // 1. Configure ESP domains FIRST
   configureESPDomains();
@@ -371,10 +362,10 @@ const initializeAppsFlyer = () => {
   // 3. Set up conversion data listener
   appsFlyer.registerConversionListener(
     (res) => {
-      console.log('📊 Conversion Data:', res);
+      console.log('Conversion Data:', res);
     },
     (error) => {
-      console.error('❌ Conversion Data Error:', error);
+      console.error('Conversion Data Error:', error);
     }
   );
 
@@ -387,10 +378,10 @@ const initializeAppsFlyer = () => {
 
   appsFlyer.init(devKey, "YOUR_IOS_APP_ID").then(
     () => {
-      console.log("✅ AppsFlyer SDK initialized successfully!");
+      console.log("AppsFlyer SDK initialized successfully!");
     },
     (err) => {
-      console.error("❌ AppsFlyer SDK initialization error:", err);
+      console.error("AppsFlyer SDK initialization error:", err);
     }
   );
 };
@@ -407,75 +398,27 @@ useEffect(() => {
 
 ### Common Android Issues
 
-**1. Deep links open Google Play instead of app:**
-- Remove `android:autoVerify="true"` from intent filters
-- Test with ADB for direct app opening
-- Ensure app is installed and intent filters are correct
+For general Android configuration issues (manifest merging, package attribute deprecation, autoVerify behavior, backup rules), refer to the [known-issues knowledge base](../Docs/RN_API.md) and [AppsFlyer Android SDK documentation](https://dev.appsflyer.com/hc/docs/install-android-sdk).
 
-**2. Email deep links redirect to Play Store (Domain Disabled):**
+**ESP-Specific: Domain Verification Issues**
 
-This is a common issue where clicking deep links from emails opens the Play Store instead of your app. This happens when the domain is disabled in Android's app link settings.
+When deep links from emails open the Play Store instead of your app, the domain may be disabled in Android's app link settings.
 
 **Diagnosis:**
 ```bash
-# Check if your app's domain is disabled
 adb shell pm get-app-links com.yourcompany.yourapp
 ```
 
-Look for your domain in the "Selection state" → "Disabled" section.
-
 **Solution:**
 ```bash
-# Enable domain for your app (replace with your actual package name and domain)
+# Enable domain for your app
 adb shell pm set-app-links-user-selection --package com.yourcompany.yourapp --user 0 true your-onelink-domain.onelink.me
 
-# Verify the fix
-adb shell pm get-app-links com.yourcompany.yourapp
-```
-
-**Testing:**
-```bash
-# Test deep link after fix
+# Test the fix
 adb shell am force-stop com.yourcompany.yourapp
 adb shell am start -W -a android.intent.action.VIEW -d "https://your-onelink-domain.onelink.me/test"
 ```
 
-**Production Note:** This is a testing solution. For production apps, consider:
-- Domain verification (requires access to domain)
-- User education about setting app as default handler
-- Fallback handling for when app isn't the default handler
-
-**3. Manifest merger conflicts:**
-```xml
-<!-- Add tools namespace and replace directive -->
-<manifest xmlns:tools="http://schemas.android.com/tools">
-  <application android:allowBackup="false" tools:replace="android:allowBackup">
-```
-See [AppsFlyer Android SDK documentation](https://dev.appsflyer.com/hc/docs/install-android-sdk#backup-rules) for more details.
-
-**4. Package attribute deprecated:**
-- Remove `package="com.yourapp"` from AndroidManifest.xml
-- Use `namespace` in build.gradle instead
-
-**5. Build Cache Issues:**
-
-If experiencing persistent build failures, perform a complete clean build:
-```bash
-# Clean everything
-rm -rf node_modules
-rm -rf ios/Pods
-rm -rf android/.gradle
-rm -rf android/app/build
-rm -rf android/build
-
-# Reinstall dependencies
-npm install
-cd ios && pod install && cd ..
-
-# Clean build
-npx expo run:android / ios --clear
-```
-
 ### Common iOS Issues
 
 **1. Universal Links not working:**