Add preferAppsFlyerBackupRules flag for Expo Android manifest

Add opt-in flag to control backup rules handling. Default respects app's rules;
when enabled, removes app's backup rules to use AppsFlyer SDK's built-in rules.

Author: al-af

Docs/RN_ExpoInstallation.md

@@ -25,7 +25,8 @@ expo install react-native-appsflyer
         "react-native-appsflyer",
         {
           "shouldUseStrictMode": false,          // optional – kids-apps strict mode
-          "shouldUsePurchaseConnector": true     // NEW – enables Purchase Connector
+          "shouldUsePurchaseConnector": true,    // optional – enables Purchase Connector
+          "preferAppsFlyerBackupRules": false    // optional – use AppsFlyer SDK backup rules (default: false)
         }
       ]
     ],
@@ -42,8 +43,40 @@ expo install react-native-appsflyer
     ],
 ...
 ```
-### Fix for build failure with RN 0.76 and Expo 52
-To ensure seamless integration of the AppsFlyer plugin in your Expo-managed project, it’s essential to handle modifications to the AndroidManifest.xml correctly. Since direct edits to the AndroidManifest.xml aren’t feasible in the managed workflow, you’ll need to create a custom configuration to include the necessary changes.
+### Backup Rules Configuration (Android)
+
+The AppsFlyer SDK includes built-in backup rules in its Android manifest to ensure accurate install/reinstall detection. By default, the plugin respects your app's backup rules and does not modify them.
+
+**Default Behavior** (`preferAppsFlyerBackupRules: false` or omitted):
+- Your app's `android:dataExtractionRules` and `android:fullBackupContent` attributes are left untouched
+- You maintain full control over your app's backup policy
+- No manifest merge conflicts occur
+
+**Opt-in Behavior** (`preferAppsFlyerBackupRules: true`):
+- If your app defines backup rules, they will be removed to let AppsFlyer SDK's built-in rules take precedence
+- This ensures AppsFlyer SDK's backup rules are used, which may improve install/reinstall detection accuracy
+- Use this flag if you want AppsFlyer SDK to manage backup rules for you
+
+**When to use `preferAppsFlyerBackupRules: true`:**
+- You want AppsFlyer SDK to handle backup rules automatically
+- You're experiencing issues with install/reinstall detection that may be related to backup rules
+- You don't have specific backup requirements for your app
+
+**Example configuration:**
+```json
+{
+  "expo": {
+    "plugins": [
+      [
+        "react-native-appsflyer",
+        {
+          "preferAppsFlyerBackupRules": true
+        }
+      ]
+    ]
+  }
+}
+```
 
 ### Handling dataExtractionRules Conflict
 
@@ -123,3 +156,11 @@ Setting `"shouldUsePurchaseConnector": true` will:
 
 * **iOS** – add the `PurchaseConnector` CocoaPod automatically  
 * **Android** – add `appsflyer.enable_purchase_connector=true` to `gradle.properties`
+
+### Plugin Options Summary
+
+| Option | Type | Default | Description |
+|-------|------|---------|-------------|
+| `shouldUseStrictMode` | boolean | `false` | Enable strict mode for kids apps |
+| `shouldUsePurchaseConnector` | boolean | `false` | Enable Purchase Connector support |
+| `preferAppsFlyerBackupRules` | boolean | `false` | Remove app's backup rules to use AppsFlyer SDK's built-in rules (Android only) |

expo/withAppsFlyerAndroid.js

@@ -13,53 +13,87 @@ function addPurchaseConnectorFlag(config) {
   });
 }
 
-// withCustomAndroidManifest.js
-function withCustomAndroidManifest(config) {
-  return withAndroidManifest(config, async (config) => {
+// Opt-in backup rules handling
+function withCustomAndroidManifest(config, { preferAppsFlyerBackupRules = false } = {}) {
+  return withAndroidManifest(config, async (cfg) => {
     console.log('[AppsFlyerPlugin] Starting Android manifest modifications...');
-    
-    const androidManifest = config.modResults;
+
+    const androidManifest = cfg.modResults;
     const manifest = androidManifest.manifest;
-    
+
+    if (!manifest || !manifest.$ || !manifest.application || !manifest.application[0]) {
+      console.warn('[AppsFlyerPlugin] Unexpected manifest structure; skipping modifications');
+      return cfg;
+    }
+
     // Ensure xmlns:tools is present in the <manifest> tag
     if (!manifest.$['xmlns:tools']) {
       manifest.$['xmlns:tools'] = 'http://schemas.android.com/tools';
       console.log('[AppsFlyerPlugin] Added xmlns:tools namespace');
     }
 
     const application = manifest.application[0];
+    const appAttrs = application.$ || {};
+
+    const hasDataExtractionRules = appAttrs['android:dataExtractionRules'] !== undefined;
+    const hasFullBackupContent = appAttrs['android:fullBackupContent'] !== undefined;
+
+    if (!preferAppsFlyerBackupRules) {
+      // Default: do not touch backup attributes at all
+      if (hasDataExtractionRules || hasFullBackupContent) {
+        console.log(
+          '[AppsFlyerPlugin] App defines backup attributes; leaving them untouched (preferAppsFlyerBackupRules=false)'
+        );
+      } else {
+        console.log(
+          '[AppsFlyerPlugin] App does not define backup attributes; no changes required (preferAppsFlyerBackupRules=false)'
+        );
+      }
+      console.log('[AppsFlyerPlugin] Android manifest modifications completed');
+      return cfg;
+    }
 
-    // Add tools:replace attribute for dataExtractionRules and fullBackupContent
-    // This allows AppsFlyer SDK's built-in backup rules to take precedence over
-    // conflicting rules in the app's manifest (see: https://dev.appsflyer.com/hc/docs/install-android-sdk#backup-rules)
-    const existingReplace = application['$']['tools:replace'];
-    if (existingReplace) {
-      // Add to existing tools:replace if not already present
-      const replaceAttrs = existingReplace.split(',').map(s => s.trim());
-      if (!replaceAttrs.includes('android:dataExtractionRules')) {
-        replaceAttrs.push('android:dataExtractionRules');
+    // preferAppsFlyerBackupRules === true
+    if (hasDataExtractionRules || hasFullBackupContent) {
+      // Remove conflicting attributes from app's manifest
+      // This allows AppsFlyer SDK's built-in backup rules to be used instead.
+      if (hasDataExtractionRules) {
+        delete appAttrs['android:dataExtractionRules'];
+        console.log(
+          '[AppsFlyerPlugin] Removed android:dataExtractionRules to use AppsFlyer SDK rules (preferAppsFlyerBackupRules=true)'
+        );
       }
-      if (!replaceAttrs.includes('android:fullBackupContent')) {
-        replaceAttrs.push('android:fullBackupContent');
+
+      if (hasFullBackupContent) {
+        delete appAttrs['android:fullBackupContent'];
+        console.log(
+          '[AppsFlyerPlugin] Removed android:fullBackupContent to use AppsFlyer SDK rules (preferAppsFlyerBackupRules=true)'
+        );
       }
-      application['$']['tools:replace'] = replaceAttrs.join(', ');
     } else {
-      application['$']['tools:replace'] = 'android:dataExtractionRules, android:fullBackupContent';
+      console.log(
+        '[AppsFlyerPlugin] App does not define backup attributes; no conflict with AppsFlyer SDK (preferAppsFlyerBackupRules=true)'
+      );
     }
 
     console.log('[AppsFlyerPlugin] Android manifest modifications completed');
-    
-    return config;
+    return cfg;
   });
 }
 
-module.exports = function withAppsFlyerAndroid(config, { shouldUsePurchaseConnector = false } = {}) {
+// Main plugin export
+module.exports = function withAppsFlyerAndroid(
+  config,
+  {
+    shouldUsePurchaseConnector = false,
+    preferAppsFlyerBackupRules = false,
+  } = {}
+) {
   if (shouldUsePurchaseConnector) {
     config = addPurchaseConnectorFlag(config);
-  } 
-  // Apply Android manifest modifications to resolve backup rules conflicts with AppsFlyer SDK
-  // This ensures AppsFlyer SDK's built-in backup rules take precedence (see issue #631)
-  config = withCustomAndroidManifest(config);
-  
+  }
+
+  config = withCustomAndroidManifest(config, { preferAppsFlyerBackupRules });
+
   return config;
-};
+};