Release v7.0.2

.af-e2e/test-plan.json

@@ -34,16 +34,16 @@
       "checks": [
         {
           "id": "sdk_started",
-          "description": "startSDK was called",
+          "description": "start was called",
           "type": "log_contains",
-          "pattern": "[AF_QA][startSDK] result:",
+          "pattern": "[AF_QA][start] result:",
           "fail_action": "abort"
         },
         {
           "id": "is_first_launch_true",
-          "description": "onInstallConversionData fires with is_first_launch=true",
+          "description": "registerConversionListener fires with is_first_launch=true",
           "type": "log_contains",
-          "pattern": "[AF_QA][CALLBACK][onInstallConversionData]",
+          "pattern": "[AF_QA][CALLBACK][registerConversionListener]",
           "payload_check": {"field": "is_first_launch", "expected": "true"},
           "fail_action": "abort"
         },
@@ -65,7 +65,7 @@
           "id": "get_sdk_version",
           "description": "getSDKVersion returns a value",
           "type": "log_contains",
-          "pattern": "[AF_QA][getSDKVersion] result:",
+          "pattern": "[AF_QA][getSdkVersion] result:",
           "fail_action": "fail"
         },
         {
@@ -106,16 +106,16 @@
         },
         {
           "id": "on_deep_linking_callback",
-          "description": "onDeepLinking fires (NOT_FOUND expected on clean launch)",
+          "description": "onDeepLinking fires (NOT_FOUND expected on clean launch) — iOS always invokes this callback on cold launch even with no deep link; Android's SDK only invokes it when an actual deep link is present, so this warns instead of fails on Android",
           "type": "log_contains",
           "pattern": "[AF_QA][CALLBACK][onDeepLinking]",
-          "fail_action": "fail"
+          "fail_action": "warn"
         },
         {
           "id": "no_fatal_errors",
           "description": "No fatal exceptions or SDK errors in logs",
           "type": "absent",
-          "patterns": ["Fatal Exception", "FATAL", "[AF_QA][startSDK] error:", "response code:4", "response code:5"],
+          "patterns": ["Fatal Exception", "FATAL", "[AF_QA][start] error:", "response code:4", "response code:5"],
           "fail_action": "fail"
         }
       ]
@@ -293,6 +293,7 @@
       "scenario_ref": "E2E-005",
       "description": "Fresh install. Verify setCustomerUserId, setCurrencyCode, setAdditionalData propagate correctly. Identity-check event receives HTTP 200. is_first_launch=true still fires.",
       "requires_fresh_install": true,
+      "requires_device_identity_reset": true,
       "wait_after_launch_sec": 420,
       "checks": [
         {
@@ -326,9 +327,9 @@
         },
         {
           "id": "is_first_launch_true",
-          "description": "onInstallConversionData still fires with is_first_launch=true",
+          "description": "registerConversionListener still fires with is_first_launch=true",
           "type": "log_contains",
-          "pattern": "[AF_QA][CALLBACK][onInstallConversionData]",
+          "pattern": "[AF_QA][CALLBACK][registerConversionListener]",
           "payload_check": {"field": "is_first_launch", "expected": "true"},
           "fail_action": "fail"
         },
@@ -352,9 +353,19 @@
       "checks": [
         {
           "id": "stop_true",
-          "description": "stop(true) readback present",
+          "description": "stop(true) resolves null — the void-RPC success value on both platforms",
           "type": "log_contains",
-          "pattern": "[AF_QA][stop] result: true",
+          "pattern": "[AF_QA][stop(true)] result: null",
+          "fail_action": "fail"
+        },
+        {
+          "id": "stop_no_error_payload",
+          "description": "Neither stop call forwarded an RPC error through its single callback",
+          "type": "absent",
+          "patterns": [
+            "[AF_QA][stop(true)] result: {\"code\"",
+            "[AF_QA][stop(false)] result: {\"code\""
+          ],
           "fail_action": "fail"
         },
         {
@@ -366,9 +377,9 @@
         },
         {
           "id": "stop_false",
-          "description": "stop(false) readback present",
+          "description": "stop(false) resolves null — the void-RPC success value on both platforms",
           "type": "log_contains",
-          "pattern": "[AF_QA][stop] result: false",
+          "pattern": "[AF_QA][stop(false)] result: null",
           "fail_action": "fail"
         },
         {

.af-smoke/rc-test-plan.json

@@ -34,16 +34,16 @@
       "checks": [
         {
           "id": "sdk_started",
-          "description": "startSDK returns a result",
+          "description": "start returns a result",
           "type": "log_contains",
-          "pattern": "[AF_QA][startSDK] result:",
+          "pattern": "[AF_QA][start] result:",
           "fail_action": "abort"
         },
         {
           "id": "conversion_data",
-          "description": "onInstallConversionData callback fires",
+          "description": "registerConversionListener callback fires",
           "type": "log_contains",
-          "pattern": "[AF_QA][CALLBACK][onInstallConversionData]",
+          "pattern": "[AF_QA][CALLBACK][registerConversionListener]",
           "fail_action": "fail"
         },
         {
@@ -139,9 +139,9 @@
       "checks": [
         {
           "id": "sdk_started",
-          "description": "startSDK returns a result on fresh install",
+          "description": "start returns a result on fresh install",
           "type": "log_contains",
-          "pattern": "[AF_QA][startSDK] result:",
+          "pattern": "[AF_QA][start] result:",
           "fail_action": "abort"
         },
         {

.claude/commands/release-check.md

@@ -18,7 +18,7 @@ Verify all release checkpoints. Report as a pass/fail checklist.
    - `package.json` version
    - `react-native-appsflyer.podspec` s.version
    - `ios/RNAppsFlyer.h` kAppsFlyerPluginVersion
-   - `android/.../RNAppsFlyerConstants.java` PLUGIN_VERSION
+   - `android/.../RNAppsFlyerConstants.kt` PLUGIN_VERSION
 
 2. **CHANGELOG** — `CHANGELOG.md` has an entry for the current version at the top.
 

.claude/commands/version-bump.md

@@ -18,7 +18,7 @@ Bump the plugin version to `$ARGUMENTS` across all 4 files that must stay in syn
 1. `package.json` — `"version": "X.Y.Z"`
 2. `react-native-appsflyer.podspec` — `s.version = 'X.Y.Z'`
 3. `ios/RNAppsFlyer.h` — `kAppsFlyerPluginVersion = @"X.Y.Z"`
-4. `android/src/main/java/com/appsflyer/reactnative/RNAppsFlyerConstants.java` — `PLUGIN_VERSION = "X.Y.Z"`
+4. `android/src/main/java/com/appsflyer/reactnative/RNAppsFlyerConstants.kt` — `PLUGIN_VERSION = "X.Y.Z"`
 
 ### Steps
 

.claude/rules/bridge-patterns.md

@@ -1,60 +1,100 @@
 ---
 paths:
-  - "index.js"
-  - "index.d.ts"
+  - "index.ts"
+  - "src/NativeAppsFlyer.ts"
+  - "src/rn-transport.ts"
 ---
 
 # Bridge patterns — JS ↔ native contract
 
-Scope: `index.js`, `index.d.ts`, and any file that calls `NativeModules.RNAppsFlyer` or `NativeModules.PCAppsFlyer`.
+Scope: `index.ts`, `src/NativeAppsFlyer.ts`, `src/rn-transport.ts`. All native calls go through the single TurboModule entry point `NativeAppsFlyer.executeRpc(requestJson)` — no bespoke per-feature native methods.
 
-## 1. Three API patterns coexist
+Method dispatch, per-platform wire method-name/param resolution, and event demuxing live in `@appsflyer-sdk/js-core-plugin`, not this repo. This repo's only glue is `src/rn-transport.ts`'s `RNTransport`, implementing `RpcTransport`:
 
-| Pattern | When used | Detection |
-|---------|-----------|-----------|
-| Dual callback/promise | `initSdk`, `logEvent` | `if (success && error)` routes to `*WithCallBack`; otherwise `*WithPromise` |
-| Callback-only | Most config methods (`setCustomerUserId`, `stop`, `setCurrencyCode`) | Optional callback; defaults to `console.log` fallback |
-| Event emitter | Deep linking, conversion data, purchase validation | `appsFlyerEventEmitter.addListener(eventName, handler)` |
+| `RpcTransport` member | Implementation |
+|---|---|
+| `call<T>(method, params)` | Serializes to `executeRpc`'s request JSON, parses the response, resolves with `data` or rejects with `error` |
+| `subscribe(listener)` | Wraps `NativeEventEmitter` on the shared `RNAppsFlyer_rpcEvent` event name |
 
-When adding a new method, match the pattern of similar methods. Do not mix patterns within a single method.
+`index.ts` constructs `AppsFlyerSDK` with an `RNTransport` instance, exports it (`export const AppsFlyer = sdk`), and re-exports everything from `@appsflyer-sdk/js-core-plugin` (`export * from "@appsflyer-sdk/js-core-plugin"`).
 
-## 2. Callback-to-native routing
+## RPC request/response shape
 
-```js
-// Dual pattern — index.js
-if (success && error) {
-  RNAppsFlyer.initSdkWithCallBack(options, success, error);
-} else {
-  return RNAppsFlyer.initSdkWithPromise(options);
-}
+Every call serializes to:
+```json
+{ "method": "methodName", "params": { ... } }
+```
+
+Every response resolves (never rejects for native-side outcomes) as:
+```json
+{ "success": true, "data": <any> }
+// or
+{ "success": false, "error": { "code": <number>, "message": "<string>" } }
+```
+
+`RNTransport.call` unwraps this: resolves with `data` on success, rejects with `error` on failure. Android's `error.code` is a distinct number per failure class (e.g. `404` = `RpcErrorCodes.METHOD_NOT_FOUND`) — iOS error codes aren't cross-checked against this numbering, don't assume parity.
+
+The TurboModule Promise itself only rejects if the call never reaches native at all.
+
+## Event channel contract
+
+Async native events (conversion data, deep link, session ready) arrive via `NativeEventEmitter` on a single shared event name (`RNAppsFlyer_rpcEvent` on both platforms). `RNTransport.subscribe` forwards the raw envelope to `@appsflyer-sdk/js-core-plugin`, which owns the demuxing into:
+- `onConversionDataSuccess` / `onConversionDataFail`
+- `onDeepLinkReceived` (iOS) / `onDeepLinking` (Android) — normalized to one JS-facing shape
+- `onSessionReady` — fires once `registerSessionReadyListener` is registered and native signals readiness. `isSessionReady` is a separate one-off Promise query for current state, not a replacement.
+
+The raw `origin`/`timestamp` envelope fields are stripped before handing `data` to app callbacks. No `supportedEvents` array under TurboModules.
+
+## Listener registration order
+
+Registration calls are init-order-independent by design on both platforms — each just assigns a delegate/callback on the persistent native SDK singleton. Only `start`/`logEvent` require `init` to have run first.
+
+Exceptions (native side effects — see `known-issues-kb.md` for root cause):
+
+| Listener | Call order | Why |
+|---|---|---|
+| `registerSessionReadyListener` | called synchronously (no `.then()`) | avoids a TOCTOU race with `init()` |
+| `registerDeepLinkListener` | before `init()`, both platforms | Android drops any pre-registration deep-link result with zero buffering |
+| `registerConversionListener` | either order | plain delegate assignment, no side effect |
+
+### Canonical call order
+
+```
+registerDeepLinkListener → init → (config setters) → registerConversionListener → registerSessionReadyListener(() => start())
 ```
 
-The native side has **separate methods** for callback vs promise variants. Adding a new dual method requires implementing both on iOS (`RCT_EXPORT_METHOD`) and Android (`@ReactMethod`).
+Register synchronously, not inside `init(...).then()` — deferring into the promise callback delays the one callback that triggers `start()`.
 
-## 3. Event emitter contract
+No JS-side buffer exists for these RPCs — don't add one without confirming an actual native regression first (see `known-issues-kb.md`'s "listener-registration buffer removed" entry).
 
-- Events arrive as **JSON strings** from native — always parsed with `JSON.parse` on the JS side
-- Parse failures produce `AFParseJSONException` objects (not proper Error subclasses)
-- Native must serialize data to JSON string **before** calling `sendEventWithName:body:` (iOS) or `sendEvent` (Android)
-- Supported event names are declared in iOS `supportedEvents` and must match exactly on both platforms:
-  `onAttributionFailure`, `onAppOpenAttribution`, `onInstallConversionFailure`, `onInstallConversionDataLoaded`, `onDeepLinking`, `onValidationResult`
+### Deterministic ordering after start()
 
-## 4. Listener registration order
+`registerSessionReadyListener`'s callback is the only place to call `start()`. It fires asynchronously, so code written after the registration call in source order runs *before* it, not after. Wrap in a Promise to run app logic strictly after `start()`:
 
-`onDeepLink` (and `onInstallConversionData`, `onAppOpenAttribution`) must be registered **before** `initSdk`. The native SDK fires these callbacks immediately after initialization — if the JS listener isn't attached yet, events are lost silently.
+```js
+function startWhenSessionReady() {
+  return new Promise((resolve, reject) => {
+    AppsFlyer.registerSessionReadyListener(() => {
+      AppsFlyer.start().then(resolve, reject);
+    });
+  });
+}
+// ... init() + listener registration (not awaited) ...
+await startWhenSessionReady();
+```
 
-This is the #1 source of GitHub issues (#650, #647, #630, #305, #292). Always validate listener timing in code review.
+This only reorders app-controlled code — there's no timeout/fallback if `onSessionReady` never fires.
 
-## 5. No transpilation
+`onAppOpenAttribution`, `onAttributionFailure`, `performOnAppAttribution` are removed in 7.0.0 — use `onDeepLinking` instead (see MIGRATION.md).
 
-`index.js` ships as-is via npm — no Babel, no bundler. Write only syntax that Metro and Node can consume directly. The file uses ES module `export` syntax with CommonJS-compatible patterns.
+## No transpilation
 
-## 6. Named exports
+`index.ts` ships as-is via npm — no Babel, no bundler, no separate `index.js`/`index.d.ts`. Only syntax Metro and Node can consume directly.
 
-Current named exports from `index.js`: `AppsFlyerConsent`, `AFParseJSONException`, `AFPurchaseType`, `MEDIATION_NETWORK`, `StoreKitVersion`, `AppsFlyerPurchaseConnector`, `AppsFlyerPurchaseConnectorConfig`.
+## Named exports
 
-Adding a new named export changes the public API surface — requires a minor version bump and matching `index.d.ts` update.
+`AFInAppEventType`, `AFPurchaseType`, `MEDIATION_NETWORK`, `StoreKitVersion`, `AppsFlyerPurchaseConnector`, `AppsFlyerPurchaseConnectorConfig`, plus everything `@appsflyer-sdk/js-core-plugin` exports (including `AppsFlyerConsent`). Adding a new named export requires a version bump.
 
-## 7. Default callback fallback
+## PurchaseConnector
 
-Many methods use `(result) => console.log(result)` as the default callback when none is provided. This leaks to production logs. Prefer silent no-ops for new methods, or document the logging behavior explicitly.
+`PCAppsFlyer` still uses the legacy `NativeModules` bridge — out of scope for the TurboModule rewrite. Don't touch `PurchaseConnector/` when working on RPC/TurboModule changes.

.claude/rules/expo-config.md

@@ -5,56 +5,43 @@ paths:
 
 # Expo config plugin rules
 
-Scope: `expo/` directory — `withAppsFlyer.js`, `withAppsFlyerIos.js`, `withAppsFlyerAndroid.js`.
+Scope: `expo/withAppsFlyer.js`, `withAppsFlyerIos.js`, `withAppsFlyerAndroid.js`. These run at `expo prebuild` time to modify native project files; the host app must have New Architecture enabled (not enforced by the plugin itself).
 
-## 1. Config plugin structure
+## Structure
 
 ```
 expo/
 ├── withAppsFlyer.js          ← Entry point, composes iOS + Android plugins
-├── withAppsFlyerIos.js       ← Modifies AppDelegate for deep link handling
-├── withAppsFlyerAndroid.js   ← Modifies AndroidManifest.xml
-└── withAppsFlyerAppDelegate.js ← AppDelegate code injection
+├── withAppsFlyerIos.js       ← Modifies AppDelegate (ObjC + Swift) + Podfile
+└── withAppsFlyerAndroid.js   ← Modifies AndroidManifest.xml
 ```
 
-These are Expo Config Plugins — they run at `expo prebuild` time to modify native project files.
+## Swift AppDelegate support
 
-## 2. Swift AppDelegate problem (critical, unresolved)
+`withAppsFlyerIos.js`'s `modifySwiftAppDelegate` string-matches Expo's default Swift AppDelegate template (`didFinishLaunchingWithOptions`/`openURL`/`continueUserActivity`) and injects `handleLaunchOptions`/`handleOpen`/`continueUserActivity` calls via `AppsFlyerAttribution.shared` (one `import react_native_appsflyer`, no `AppsFlyerLib` import needed). `modifyObjcAppDelegate` handles the legacy ObjC template the same way.
 
-Starting with Expo SDK 52 / RN 0.76, the default AppDelegate is **Swift** (not Objective-C). The plugin's `withAppsFlyerAppDelegate.js` modifies ObjC code and **fails silently** on Swift AppDelegates (#638, #620).
+Both matchers are exact-string-match against one template shape — if Expo/RN changes the default AppDelegate boilerplate, the matcher silently misses (falls through to `WarningAggregator.addWarningIOS`, not a build failure) instead of adapting. Re-verify the matched strings against a fresh `expo prebuild` output whenever bumping the supported Expo SDK version.
 
-Until this is fixed:
-- Do not assume AppDelegate is ObjC in config plugin code
-- Test with both `expo prebuild` (Swift default) and legacy ObjC projects
-- This is the #1 Expo compatibility blocker
+## Manifest merge is not idempotent
 
-## 3. Manifest merge duplication
+`withAppsFlyerAndroid.js` appends `tools:replace` entries to `AndroidManifest.xml` without checking for existing entries — repeated `expo prebuild` (without `--clean`) duplicates them and breaks the Android build. Always check if the entry exists before appending.
 
-`withAppsFlyerAndroid.js` appends `tools:replace` entries to `AndroidManifest.xml`. Running `expo prebuild` multiple times (without `--clean`) causes **duplicate entries** that break the Android build (#672).
+## Expo Go incompatibility
 
-Fix pattern: always check if the entry exists before appending. Use idempotent modifications.
+Requires native modules unavailable in Expo Go — only works in development builds (`eas build --profile development`) or bare workflow.
 
-## 4. Expo Go incompatibility
+## No test coverage
 
-The plugin requires native modules unavailable in Expo Go. Only works in development builds (`eas build --profile development`) or bare workflow. This is documented but users miss it repeatedly (#542).
+Zero test coverage on the config plugins. Manual test with `expo prebuild --clean` on both platforms after any change.
 
-## 5. No test coverage
+## Peer dependency
 
-The Expo config plugins have **zero test coverage**. When modifying these files, manual testing with `expo prebuild --clean` on both platforms is required. Consider adding unit tests that mock the Expo config plugin API.
+`expo` is an optional peer dependency — guard all Expo-specific imports/config so the plugin works without Expo installed.
 
-## 6. Peer dependency
-
-`expo` is declared as an optional peer dependency. The plugin must work without Expo installed — guard all Expo-specific imports and config.
-
-## 7. Testing changes
+## Testing changes
 
 ```bash
-# Clean prebuild (recommended)
 cd demos/demo && npx expo prebuild --clean
-
-# Verify Android manifest
 cat android/app/src/main/AndroidManifest.xml | grep -A5 "appsflyer"
-
-# Verify iOS AppDelegate
-cat ios/demo/AppDelegate.m  # or AppDelegate.swift for Expo 52+
+cat ios/demo/AppDelegate.swift  # or AppDelegate.m pre-Expo-52
 ```