@loyalytics/swan-react-native-sdk 2.1.3-beta.2 → 2.1.3-beta.3

package/lib/commonjs/version.js

@@ -8,5 +8,5 @@ exports.SDK_VERSION = void 0;
 // This file is generated from package.json version during build.
 // See scripts/generate-version.js
 
-const SDK_VERSION = exports.SDK_VERSION = '2.1.3-beta.2';
+const SDK_VERSION = exports.SDK_VERSION = '2.1.3-beta.3';
 //# sourceMappingURL=version.js.map

package/lib/module/version.js

@@ -4,5 +4,5 @@
 // This file is generated from package.json version during build.
 // See scripts/generate-version.js
 
-export const SDK_VERSION = '2.1.3-beta.2';
+export const SDK_VERSION = '2.1.3-beta.3';
 //# sourceMappingURL=version.js.map

package/lib/typescript/commonjs/src/version.d.ts

@@ -1,2 +1,2 @@
-export declare const SDK_VERSION = "2.1.3-beta.2";
+export declare const SDK_VERSION = "2.1.3-beta.3";
 //# sourceMappingURL=version.d.ts.map

package/lib/typescript/module/src/version.d.ts

@@ -1,2 +1,2 @@
-export declare const SDK_VERSION = "2.1.3-beta.2";
+export declare const SDK_VERSION = "2.1.3-beta.3";
 //# sourceMappingURL=version.d.ts.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@loyalytics/swan-react-native-sdk",
-  "version": "2.1.3-beta.2",
+  "version": "2.1.3-beta.3",
   "description": "React Native SDK for Swan",
   "source": "./src/index.tsx",
   "main": "./lib/commonjs/index.js",
@@ -23,7 +23,6 @@
     "ios",
     "cpp",
     "scripts",
-    "docs",
     "*.podspec",
     "react-native.config.json",
     "!ios/build",
@@ -214,9 +213,6 @@
     "@react-native-async-storage/async-storage": "2.2.0",
     "@react-native-community/geolocation": "^3.4.0",
     "@react-native-community/netinfo": "^11.0.0",
-    "expo": "~52.0.47",
-    "react": "*",
-    "react-native": "*",
     "react-native-base64": "^0.2.1",
     "react-native-device-info": "^14.0.1",
     "react-native-shared-group-preferences": "^1.1.24",

package/docs/IOS_NOTIFICATION_EXTENSION_SETUP.md

@@ -1,335 +0,0 @@
-# iOS Notification Service Extension Setup
-
-## Overview
-
-The Swan SDK's Notification Service Extension enables:
-- ✅ **Delivery tracking** when app is killed or in background
-- ✅ **Rich media support** (images in notifications)
-- ✅ **Reliable ACKs** even when app is not running
-
-This extension is **required for iOS** to track push notification delivery in all app states.
-
----
-
-## Why is this needed?
-
-### The iOS Limitation
-
-On iOS, when your app is in background or killed state and receives a push notification with a visible alert, React Native's `setBackgroundMessageHandler` **is NOT called**. This is fundamental iOS behavior, not a bug.
-
-**What this means:**
-- ❌ No delivery tracking when app is killed
-- ❌ No custom notification display logic in background
-- ❌ No image processing without extension
-
-### The Solution: Notification Service Extension
-
-A Notification Service Extension is a separate iOS app extension that:
-- ✅ Runs in a **separate process** from your main app
-- ✅ Intercepts **all incoming notifications** before they're displayed
-- ✅ Has **30 seconds** to process the notification
-- ✅ Can send delivery ACKs, download images, and modify content
-
-**Industry standard:** Firebase, OneSignal, CleverTap, Airship all use this approach.
-
----
-
-## Installation
-
-### Step 1: Install Dependencies
-
-```bash
-npm install react-native-shared-group-preferences
-cd ios && pod install && cd ..
-```
-
-**Why needed:** Share credentials between app and extension.
-
----
-
-### Step 2: Configure in Xcode
-
-#### 2.1 Add Extension Target
-
-1. Open `ios/*.xcworkspace` in Xcode
-2. Go to **File → New → Target**
-3. Choose **"Notification Service Extension"**
-4. **Product Name:** `SwanNotificationServiceExtension`
-5. **Language:** Swift
-6. Click **Finish**
-7. When prompted "Activate scheme?", click **Cancel**
-
-#### 2.2 Configure App Groups
-
-**App Groups** allow the main app and extension to share credentials.
-
-##### Main App Target
-
-1. Select your **main app target** (e.g., `YourApp`)
-2. Go to **"Signing & Capabilities"** tab
-3. Click **"+ Capability"**
-4. Search for and add **"App Groups"**
-5. Click **"+"** under App Groups
-6. Enter: `group.swan.sdk.notifications`
-7. Click **OK**
-
-##### Extension Target
-
-1. Select **SwanNotificationServiceExtension** target
-2. Go to **"Signing & Capabilities"** tab
-3. Click **"+ Capability"**
-4. Search for and add **"App Groups"**
-5. Click **"+"** under App Groups
-6. Enter: `group.swan.sdk.notifications` (**MUST match main app!**)
-7. Click **OK**
-
-**⚠️ IMPORTANT:** Both targets must have the **exact same** App Group ID.
-
-#### 2.3 Verify Bundle Identifier
-
-1. Select **SwanNotificationServiceExtension** target
-2. Go to **"General"** tab
-3. Check **Bundle Identifier**: Should be `com.yourcompany.app.SwanNotificationServiceExtension`
-4. Make sure it's a **child** of your main app's bundle ID
-
----
-
-### Step 3: Run Setup Script
-
-Now that the extension target is created, run the setup script to copy the Swan implementation files. This will overwrite the default files created by Xcode.
-
-```bash
-node node_modules/swan-react-native-sdk/scripts/setup-ios-extension.js
-```
-
-**What it does:**
-- Copies extension files to `ios/SwanNotificationServiceExtension/`
-- Validates dependencies
-- Ensures the correct implementation is in place
-
----
-
-### Step 4: Testing
-
-### Build and Archive
-
-```bash
-# Clean build
-cd ios
-rm -rf build
-xcodebuild clean -workspace YourApp.xcworkspace -scheme YourApp
-
-# Build
-xcodebuild -workspace YourApp.xcworkspace -scheme YourApp -configuration Release
-
-# Archive (for TestFlight or Ad Hoc)
-xcodebuild -workspace YourApp.xcworkspace -scheme YourApp -configuration Release archive
-```
-
-### Test on Real Device
-
-**IMPORTANT:** Push notifications don't work on iOS Simulator!
-
-1. Archive your app (Product → Archive in Xcode)
-2. Export to device or upload to TestFlight
-3. Install on a real iOS device
-4. Send a test notification
-5. Check Xcode **Device Console** for logs
-
-### Expected Logs
-
-When extension receives a notification:
-
-```
-[SwanSDK Extension] Notification Service Extension triggered
-[SwanSDK Extension] Request identifier: 1234567890
-[SwanSDK Extension] UserInfo: {...}
-[SwanSDK Extension] Found messageId in gcm.message_id: 0:1234567890
-[SwanSDK Extension] Sending delivery ACK for messageId: 0:1234567890
-[SwanSDK Extension] Credentials loaded - appId: YOUR_APP_ID
-[SwanSDK Extension] ACK payload: {...}
-[SwanSDK Extension] ACK response status: 200
-[SwanSDK Extension] ✅ Delivery ACK sent successfully
-```
-
-If image is present:
-```
-[SwanSDK Extension] Downloading notification image: https://example.com/image.png
-[SwanSDK Extension] ✅ Image downloaded successfully
-```
-
-### View Logs on Real Device
-
-**Option 1: Xcode Device Console**
-1. Connect device via USB
-2. Xcode → Window → Devices and Simulators
-3. Select your device
-4. Click **"Open Console"**
-5. Filter by "SwanSDK Extension"
-
-**Option 2: Console.app (macOS)**
-1. Open Console app on Mac
-2. Select your connected device
-3. Search for "SwanSDK Extension"
-
----
-
-## Troubleshooting
-
-### Extension logs don't appear
-
-**Symptom:** No `[SwanSDK Extension]` logs when notification arrives
-
-**Possible causes:**
-
-1. **Missing mutable-content: 1**
-   - Check FCM payload includes `mutable-content: 1` in APNS
-   - Without it, iOS won't trigger the extension
-
-2. **App Groups not configured**
-   - Verify both targets have "App Groups" capability
-   - Verify App Group ID is `group.swan.sdk.notifications` in BOTH targets
-   - IDs must match exactly (no typos!)
-
-3. **Extension not included in build**
-   - In Xcode, go to Product → Scheme → Edit Scheme
-   - Check that SwanNotificationServiceExtension is included
-
-4. **Testing on simulator**
-   - Push notifications don't work on iOS Simulator
-   - Test on a real device
-
-### Extension runs but no ACK sent
-
-**Symptom:** See extension logs but backend doesn't receive ACK
-
-**Possible causes:**
-
-1. **Credentials not saved to App Group**
-   - Ensure SDK is initialized: `SwanSDK.init({ appId: '...' })`
-   - Credentials are saved automatically on init
-   - Check logs for: `[SharedCredentials] ✅ Credentials saved to iOS App Group`
-
-2. **App Group ID mismatch**
-   - Extension uses `group.swan.sdk.notifications` by default
-   - If you changed it, update `NotificationService.swift` line 143
-
-3. **Network issue**
-   - Extension has only 30 seconds to complete
-   - Check device has internet connection
-
-### Images not appearing
-
-**Symptom:** Notification arrives but image doesn't display
-
-**Possible causes:**
-
-1. **Image URL invalid**
-   - Check image URL is accessible (try in browser)
-   - Must be HTTPS (HTTP won't work)
-
-2. **Image format unsupported**
-   - Supported: JPEG, PNG, GIF
-   - Max size: 10MB (iOS limit)
-
-3. **mutable-content missing**
-   - Extension won't run without `mutable-content: 1`
-
-### Build errors
-
-**Error:** `No such module 'UserNotifications'`
-- Solution: Make sure deployment target is iOS 10.0+
-
-**Error:** `Use of undeclared type 'UNNotificationServiceExtension'`
-- Solution: Verify extension target is set to iOS 10.0+ deployment target
-
-**Error:** `Could not find or use auto-linked library 'swiftFoundation'`
-- Solution: Add `use_frameworks!` to Podfile
-
-**Error:** `CocoaPods Error: Unable to find compatibility version string for object version '70'`
-- Solution: In Xcode, select your Project (blue icon) → Build Settings (or Info) → Project Format. Change it to **Xcode 16.0-compatible** or later.
-
----
-
-## Customization
-
-### Custom App Group ID
-
-If you want to use a different App Group ID:
-
-1. **In Xcode:** Update App Groups in both targets to use your custom ID (e.g., `group.com.yourcompany.app`)
-
-2. **In SDK:** Configure before calling `SwanSDK.init()`:
-
-```typescript
-import { SharedCredentialsManager } from 'swan-react-native-sdk';
-
-// Set custom App Group ID BEFORE SDK init
-SharedCredentialsManager.setAppGroupId('group.com.yourcompany.app');
-
-// Then initialize SDK
-await SwanSDK.init({ appId: 'YOUR_APP_ID' });
-```
-
-3. **In Extension:** Update `NotificationService.swift`:
-
-```swift
-let appGroupId = "group.com.yourcompany.app"
-```
-
-
-
-## FAQs
-
-### Q: Do I need to modify the extension code?
-
-**A:** No. The extension works out of the box. Only modify if you need custom App Group ID.
-
-### Q: Will this increase my app size?
-
-**A:** Minimally. The extension adds ~50KB to your IPA.
-
-### Q: Does this affect app performance?
-
-**A:** No. The extension runs in a separate process and only when notifications arrive.
-
-### Q: Can I test without archiving?
-
-**A:** Yes, but you must run on a real device. Push doesn't work on simulator.
-
-### Q: What if I already have a Notification Service Extension?
-
-**A:** You'll need to merge Swan's code into your existing extension. The key parts are:
-1. Reading credentials from App Group
-2. Sending delivery ACK
-3. Downloading images
-
-### Q: Do I need this for Android?
-
-**A:** No. Android data-only push notifications work without an extension. This is iOS-only.
-
----
-
-## Support
-
-If you encounter issues:
-
-1. Check logs in Xcode Device Console
-2. Verify all steps in this guide
-3. Test with the provided FCM payload example
-4. Check that App Group IDs match in both targets
-
-For detailed debugging, enable verbose logging:
-- Main app: `SwanSDK.setLoggingEnabled(true)`
-- Extension: Logs are always enabled, check Device Console
-
----
-
-## Summary
-
-✅ **Install:** `npm install react-native-shared-group-preferences`
-✅ **Xcode:** Add extension target + configure App Groups
-✅ **Run:** `node node_modules/swan-react-native-sdk/scripts/setup-ios-extension.js`
-✅ **Test:** Archive and test on real device
-
-That's it! Your iOS notifications now have reliable delivery tracking and rich media support. 🎉

package/docs/SDK_INDUSTRY_REVIEW_REPORT.md

@@ -1,347 +0,0 @@
-# Swan React Native SDK - Industry Standards Review Report
-
-**Prepared for:** Senior Stakeholders
-**Date:** February 12, 2026
-**SDK Version:** 2.1.1
-**Review Scope:** Architecture, reliability, and industry benchmarking against CleverTap, MoEngage, OneSignal, and Braze SDKs
-
----
-
-## Executive Summary
-
-The Swan React Native SDK has undergone a significant architectural overhaul and **now follows industry-standard patterns used by CleverTap, MoEngage, OneSignal, and Braze**. The core architecture — offline-first event queuing with SQLite, non-blocking initialization, data-only push notifications, and state machine-driven flows — is **solid and production-grade**.
-
-Three issues identified during this review (API timeout bug, unprofessional database naming, and queue size limit) have been **fixed as part of this review** (PR #22). The only remaining area for future consideration is payload compression alignment (LZW64 vs industry-standard gzip), which is functional but non-standard.
-
-**Overall Assessment: 9/10** — Production-ready, industry-aligned architecture.
-
----
-
-## 1. Architecture Comparison Matrix
-
-| Capability | Swan SDK | CleverTap | MoEngage | OneSignal | Braze |
-|---|---|---|---|---|---|
-| **Offline Event Queuing** | SQLite | SQLite | SQLite | SQLite | SQLite + SharedPrefs |
-| **Non-blocking Init** | ~100ms | Yes | Yes | Yes (~8ms main thread) | Yes |
-| **Event Batching** | 10 events / 30s | 10-50 events / 15-60s | Similar | Similar | Similar |
-| **Exponential Backoff** | 2s, 4s, 8s (3 retries) | Yes | Yes | Yes | Yes |
-| **Data-only Push** | Yes (FCM + Notifee) | Supported | Supported | Supported | Supported |
-| **Payload Compression** | LZW64 (custom) | gzip | gzip | gzip | gzip |
-| **State Machines** | 3 (Device/Auth/Push) | Internal | Internal | Internal | Internal |
-| **Android Notification Channels** | 5 predefined | Yes | Yes | Yes | Yes |
-| **iOS App Group (NES)** | Yes | Yes | Yes | No | Yes |
-| **Queue Size Limits** | 5,000 events | ~10,000 | ~10,000 | Similar | Similar |
-| **Provider Abstraction** | Yes (interface) | N/A (native) | N/A (native) | N/A (native) | N/A (native) |
-| **Session Management** | 20-min window | 20-min window | 30-min window | Similar | Similar |
-| **API Timeout** | 10s | Varies | Varies | Varies | Varies |
-
----
-
-## 2. What Swan SDK Does RIGHT (Industry-Aligned)
-
-### 2.1 SQLite for Event Persistence — Industry Standard
-
-**Verdict: Correct choice. Same as CleverTap and MoEngage.**
-
-SQLite is the de facto standard for mobile SDK event queuing. All major customer engagement platforms use it:
-
-- **CleverTap**: Uses SQLite for event storage on both Android and iOS
-- **MoEngage**: Uses SQLite for offline event persistence
-- **Braze**: Uses SQLite combined with SharedPreferences
-- **Segment**: Uses SQLite for their analytics queue
-
-**Why SQLite is the right choice:**
-- ACID-compliant transactions prevent data loss during app crashes
-- Handles concurrent read/write safely
-- Zero-configuration, embedded, no server needed
-- Battle-tested on billions of mobile devices
-- Survives app kills and restarts (unlike in-memory stores)
-
-**Swan's implementation is solid:**
-- Proper table schema with indexes on `status`, `priority`, and `timestamp` (`EventQueueManager.ts:54-79`)
-- Atomic SELECT + UPDATE in `dequeue()` to prevent duplicate processing (`EventQueueManager.ts:147-209`)
-- Stale event recovery for events stuck in `sending` state after app crash (`EventQueueManager.ts:416-451`)
-- Queue size enforcement with oldest-first eviction (`EventQueueManager.ts:373-409`)
-
-> **To answer the client's question directly:** Yes, we use SQLite — the same database that CleverTap, MoEngage, Braze, Segment, and essentially every serious mobile SDK uses for event persistence. It is the industry standard.
-
-### 2.2 Non-blocking Initialization — Matches OneSignal Best Practice
-
-**Verdict: Excellent. Better than many competitor implementations.**
-
-Swan SDK init completes in ~100ms. Device registration, push setup, and location updates all run in the background without blocking the host app.
-
-For comparison:
-- **OneSignal** recently refactored their init to reduce main thread time from ~49ms to ~8ms — Swan's approach of moving everything off the critical path is the same philosophy
-- **CleverTap** also uses non-blocking init with background device registration
-- **CleverTap** has historically suffered from ANR (Application Not Responding) bugs caused by blocking initialization — Swan avoids this entirely
-
-**Swan's phased initialization:**
-```
-Phase 1: Core infrastructure (SQLite + EventQueue) — synchronous, ~50ms
-Phase 2: Device registration — BACKGROUND, non-blocking
-Phase 3: Push notifications — BACKGROUND, non-blocking
-Phase 4: Location update — BACKGROUND, non-blocking
-Phase 5: Deep link listeners — non-blocking
-```
-
-This is clean, well-ordered, and follows the principle of "fast init, eventual consistency."
-
-### 2.3 Data-Only Push Architecture — Industry-Leading Approach
-
-**Verdict: Premium-tier architecture, same as Braze.**
-
-Swan uses data-only FCM messages exclusively, displayed via Notifee. This is the same architecture used by:
-
-- **Braze**: Data-only push as the recommended approach
-- **MoEngage**: Data-only messages with custom display
-- **CleverTap**: Data-only with custom notification rendering
-- **OneSignal**: Hybrid approach but recommends data-only for advanced use
-
-**Benefits achieved by Swan:**
-- Single code path for foreground/background/killed states
-- Firebase `messageId` used as Notifee notification ID for accurate click tracking
-- No duplicate notifications (a common bug with notification+data mixed payloads)
-- Full control over notification appearance in all app states
-
-The `sdkCapabilities.dataOnlyPush` flag sent during push subscription is a smart backward-compatibility mechanism that allows the backend to gracefully support both old and new SDK versions.
-
-### 2.4 State Machine Architecture — Better Than Industry Average
-
-**Verdict: Above industry standard for React Native SDKs.**
-
-Swan uses three explicit state machines:
-
-| State Machine | States | Purpose |
-|---|---|---|
-| `DeviceStateMachine` | UNINITIALIZED → REGISTERING → REGISTERED/FAILED | Prevents duplicate registrations |
-| `AuthStateMachine` | LOGGED_OUT → LOGGING_IN → LOGGED_IN → LOGGING_OUT | Prevents concurrent login/logout |
-| `PushStateMachine` | DISABLED → INITIALIZING → READY → TOKEN_PENDING → ACTIVE | Manages push lifecycle |
-
-Most competitor SDKs use boolean flags internally. State machines are **more robust** because:
-- They make impossible states unrepresentable
-- Race conditions are eliminated by design
-- State transitions are logged and debuggable
-
-### 2.5 Profile Switching with Queue Flush — Correctly Handles CDID Boundaries
-
-**Verdict: Critical feature, correctly implemented.**
-
-Before login/logout, Swan flushes the event queue to ensure all events tagged with the old CDID are sent before switching profiles. This is the same approach used by CleverTap and MoEngage.
-
-```
-Login flow:
-1. Flush existing queue (old CDID)
-2. Send login event directly (bypass queue)
-3. Update stored CDID
-4. Re-sync push subscription with new CDID
-5. Subsequent events use new CDID
-```
-
-### 2.6 Additional Industry-Aligned Features
-
-- **Notification Channels**: 5 predefined Android channels (transactional, alerts, promotional, general, default) — matches Android 8+ best practices
-- **iOS App Group + Notification Service Extension**: Enables delivery ACK when app is killed — same as CleverTap and Braze
-- **Provider Abstraction**: `PushNotificationProvider` interface allows swapping Firebase for other providers — good extensibility
-- **Deep Link Attribution**: Automatic tracking of `swan_` prefixed UTM parameters — matches industry campaign attribution patterns
-- **Session Management**: 20-minute inactivity window — matches CleverTap's default
-
----
-
-## 3. Issues Found and Resolved
-
-### 3.1 FIXED: Timeout Value Mismatch (Bug)
-
-**Severity: High | Type: Bug | Status: FIXED in PR #22**
-
-The code comment said "10s timeout" but the actual value was 40,000ms (40 seconds):
-
-```typescript
-// BEFORE (src/index.tsx:1238)
-timeoutId = setTimeout(() => controller.abort(), 40000); // 10s timeout
-
-// AFTER (FIXED)
-timeoutId = setTimeout(() => controller.abort(), 10000); // 10s timeout
-```
-
-This meant users were waiting 4x longer than expected when the API was unreachable. Now correctly times out after 10 seconds as documented.
-
-### 3.2 FIXED: Database Named "test.db"
-
-**Severity: Medium | Type: Unprofessional | Status: FIXED in PR #22**
-
-```typescript
-// BEFORE (src/index.tsx:925)
-this.db = SQLite.openDatabase('test.db', '1.0', '', 1);
-
-// AFTER (FIXED)
-this.db = SQLite.openDatabase('swan_sdk.db', '1.0', '', 1);
-```
-
-The production database was named `test.db`. Now named `swan_sdk.db`, matching industry convention (CleverTap uses `clevertap.db`, MoEngage uses `moengage_db`).
-
-### 3.3 FIXED: Queue Size Limit Increased
-
-**Severity: Low | Type: Configuration | Status: FIXED in PR #22**
-
-```typescript
-// BEFORE (BatchConfig.ts:25)
-maxQueueSize: 1000,
-
-// AFTER (FIXED)
-maxQueueSize: 5000,
-```
-
-Increased from 1,000 to 5,000 events. This provides better coverage for prolonged offline periods (flights, poor connectivity areas) while remaining memory-efficient.
-
----
-
-## 4. Remaining Considerations
-
-### 4.1 LOW: LZW64 vs gzip Compression
-
-**Severity: Low | Industry Gap: Minor | Status: Not critical**
-
-Swan uses a custom LZW64 compression implementation (`lzw64_encode` in `index.tsx:1174-1206`). The industry standard is **gzip**:
-
-- **CleverTap**: gzip
-- **Braze**: gzip
-- **MoEngage**: gzip
-- **Segment**: gzip
-
-LZW64 is not inherently wrong, but:
-- Custom compression algorithms are harder to debug
-- gzip has better tooling support (every HTTP server/proxy understands it)
-- The custom implementation lacks error handling for edge cases
-
-**Recommendation:** Consider migrating to gzip in a future release. This is functional as-is and does not affect reliability. Low priority.
-
-### 4.2 NOTE: Encryption at Rest — Not Required for Current Data
-
-**Context: Addressed during review, deliberately deprioritized.**
-
-Competitor SDKs (CleverTap, Braze, MoEngage) use AES-256 encryption at rest. Swan uses Base64 encoding. However, **Swan does not store PII on-device**. The only data stored locally is:
-
-| Data | Type | PII? |
-|------|------|------|
-| Device ID | SDK-generated UUID | No |
-| CDID | Backend-assigned device identifier | No |
-| App ID | Configuration value | No |
-| FCM Push Token | Firebase token | No |
-| Event Queue | Event names + properties + timestamps | No* |
-| isProduction | Boolean flag | No |
-
-*Event properties depend on what the host app passes to `trackEvent()`. The SDK itself does not add PII.
-
-**Why encryption is not critical for Swan:**
-- No names, emails, passwords, or phone numbers are stored
-- All stored values are opaque system identifiers (UUIDs, tokens)
-- The worst-case scenario on a rooted device is access to identifiers that aren't useful on their own
-- Competitor SDKs encrypt because they store user profile data (email, phone, attributes) on-device — Swan doesn't
-
-**If asked by a client's security team:** "We don't store PII on-device. All locally stored values are opaque system identifiers (UUIDs, device tokens) with no personal data. Encryption at rest can be added in a future version if the SDK begins caching user profile attributes."
-
----
-
-## 5. Reliability Assessment
-
-### 5.1 What Happens in Each Failure Scenario
-
-| Scenario | Behavior | Rating |
-|---|---|---|
-| **App crash during event send** | Stale events recovered to `pending` on next init | Excellent |
-| **Network goes offline** | Events queue in SQLite, flush on network restore | Excellent |
-| **Device registration fails** | Retry on network restore, events queue locally | Good |
-| **App killed in background** | SQLite persists events, recovered on relaunch | Excellent |
-| **Login during offline** | Login fails (direct API call), events stay queued | Acceptable |
-| **Push notification when app killed** | Notifee displays via background handler, ACK sent directly | Excellent |
-| **Queue overflow** | Oldest events dropped, newest preserved (5,000 limit) | Good |
-| **Server returns partial failure** | Failed events retry individually with backoff | Excellent |
-| **API timeout** | Aborts after 10 seconds, retries with backoff | Good |
-
-### 5.2 Data Loss Risk Assessment
-
-| Risk | Mitigation | Residual Risk |
-|---|---|---|
-| Events lost during crash | SQLite transactions + stale recovery | Very Low |
-| Events lost during offline | Persistent SQLite queue | Very Low |
-| Events lost on queue overflow | 5,000 event limit with oldest-first eviction | Very Low |
-| Events permanently failed | 3 retries + 7-day cleanup | Low |
-| Credentials lost | AsyncStorage persistence | Very Low |
-
----
-
-## 6. Key Talking Points for Client Conversations
-
-### "Is offline-first architecture an industry standard?"
-
-> **Yes, absolutely.** Every major customer engagement SDK — CleverTap, MoEngage, Braze, OneSignal, Segment, Amplitude, Mixpanel — uses offline-first architecture with local event queuing. It is the universally accepted best practice because:
-> 1. Mobile networks are unreliable by nature
-> 2. Users expect apps to work instantly, not wait for network calls
-> 3. Data loss is unacceptable for analytics and attribution
-> 4. Battery efficiency requires batched network calls, not individual requests
-
-### "Which database do you use?"
-
-> **SQLite** — the same database used by CleverTap, MoEngage, Braze, Segment, and virtually every major mobile SDK. SQLite is embedded in every iOS and Android device, provides ACID transactions (meaning no data loss even during crashes), and handles millions of events reliably. Our implementation includes proper indexes, atomic dequeue operations, stale event recovery, and queue size management.
-
-### "How do you ensure events aren't lost?"
-
-> Our event pipeline has multiple layers of protection:
-> 1. **Immediate SQLite persistence**: Events are written to disk the moment they're tracked
-> 2. **Atomic status transitions**: Events move through `pending → sending → sent/failed` atomically
-> 3. **Crash recovery**: Events stuck in `sending` state are automatically recovered on next app launch
-> 4. **Retry with exponential backoff**: Failed events retry 3 times with 2s/4s/8s delays
-> 5. **Network-aware flushing**: Events automatically send when network restores
-> 6. **Queue overflow protection**: If the queue fills up (5,000 events), oldest events are evicted to make room for newer ones
-
-### "How does your push notification architecture work?"
-
-> We use **data-only FCM messages** — the same architecture used by Braze, MoEngage, and CleverTap. This gives us:
-> - **Reliable click tracking**: We set notification ID = Firebase messageId for accurate delivery/click attribution
-> - **Consistent behavior**: Same code path in foreground, background, and killed states
-> - **No duplicate notifications**: A common bug with mixed notification+data payloads that we avoid entirely
-> - **Full customization**: Rich notifications with images, channels, and custom actions
-> - **iOS delivery tracking**: Notification Service Extension with App Group sharing enables delivery ACK even when the app is killed
-
-### "How does your SDK compare to CleverTap/MoEngage?"
-
-> Swan SDK follows the same core architectural patterns:
-> - **Same database** (SQLite) for event persistence
-> - **Same offline-first approach** with local queuing and network-aware flushing
-> - **Same push architecture** (data-only FCM with custom display)
-> - **Same session management** (20-minute inactivity window, matching CleverTap)
-> - **Better state management** (explicit state machines vs boolean flags used by most competitors)
-> - **Better initialization** (non-blocking ~100ms init, avoiding ANR issues that have historically affected CleverTap)
-
-### "Do you store any user data on-device?"
-
-> We do not store PII (Personally Identifiable Information) on-device. The only locally stored data consists of opaque system identifiers — device IDs, session tokens, and the event queue. No names, emails, phone numbers, or personal attributes are cached locally. All user data lives server-side.
-
----
-
-## 7. Summary of Actions Taken
-
-| # | Item | Status | PR |
-|---|---|---|---|
-| 1 | Fix timeout bug (40s → 10s) | **FIXED** | #22 |
-| 2 | Rename database (test.db → swan_sdk.db) | **FIXED** | #22 |
-| 3 | Increase queue limit (1,000 → 5,000) | **FIXED** | #22 |
-| 4 | Evaluate gzip compression | Deferred | Future consideration |
-| 5 | Encryption at rest | Not required | No PII stored on-device |
-
----
-
-## 8. Conclusion
-
-The Swan React Native SDK v2.1 is a **well-architected, production-ready SDK** that follows the same fundamental patterns as CleverTap, MoEngage, OneSignal, and Braze. The offline-first architecture with SQLite, non-blocking initialization, state machine-driven flows, and data-only push notifications are all industry best practices.
-
-Three issues identified during this review have been fixed immediately (PR #22). The remaining consideration (LZW64 vs gzip compression) is a future optimization, not a reliability concern.
-
-The client's concern about "offline-first not being industry standard" is **factually incorrect** — it is the universal standard. Every major SDK in this space uses this exact pattern. The Swan SDK's architecture is not only industry-standard but in some areas (state machines, non-blocking init, data-only push) is **above the industry average** for React Native SDKs.
-
-**Final Assessment: 9/10** — Production-ready, industry-aligned, with targeted improvements already applied.
-
----
-
-*Report prepared through comprehensive code review and competitive analysis against CleverTap, MoEngage, OneSignal, and Braze SDKs.*

package/docs/Swan_Push_Notifications.postman_collection.json

@@ -1,330 +0,0 @@
-{
-	"info": {
-		"_postman_id": "swan-push-notifications-v1",
-		"name": "Swan SDK — Push Notifications",
-		"description": "Complete collection for testing all Swan SDK push notification types across Android and iOS.\n\n## Setup\n1. Set `project_id` to your Firebase project ID\n2. Set `fcm_token` to the device's FCM token\n3. Set `access_token` by running: `gcloud auth print-access-token`\n\n## How it works\n- All requests use the FCM v1 HTTP API\n- Variables are shared across all requests\n- Just update the token and send",
-		"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
-	},
-	"variable": [
-		{
-			"key": "project_id",
-			"value": "loyalytics-app",
-			"type": "string"
-		},
-		{
-			"key": "fcm_token",
-			"value": "<PASTE_DEVICE_FCM_TOKEN_HERE>",
-			"type": "string"
-		},
-		{
-			"key": "access_token",
-			"value": "<PASTE_GCLOUD_ACCESS_TOKEN_HERE>",
-			"type": "string"
-		},
-		{
-			"key": "fcm_url",
-			"value": "https://fcm.googleapis.com/v1/projects/{{project_id}}/messages:send",
-			"type": "string"
-		}
-	],
-	"item": [
-		{
-			"name": "Android",
-			"item": [
-				{
-					"name": "Standard Push",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"title\": \"Your order has shipped!\",\n      \"body\": \"Track your package #ABC123\",\n      \"channelId\": \"swan_transactional\",\n      \"route\": \"/orders/123\"\n    },\n    \"android\": {\n      \"priority\": \"high\"\n    }\n  }\n}"
-						}
-					}
-				},
-				{
-					"name": "Standard Push — With Image",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"title\": \"Summer Sale!\",\n      \"body\": \"50% off everything\",\n      \"channelId\": \"swan_promotional\",\n      \"route\": \"/sales/summer\",\n      \"image\": \"https://picsum.photos/id/1/1024/512\"\n    },\n    \"android\": {\n      \"priority\": \"high\"\n    }\n  }\n}"
-						}
-					}
-				},
-				{
-					"name": "Carousel — Manual / Standard",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"notificationType\": \"carousel\",\n      \"carouselMode\": \"manual\",\n      \"carouselVariant\": \"standard\",\n      \"title\": \"Weekend Flash Sale\",\n      \"body\": \"Swipe to explore deals!\",\n      \"defaultRoute\": \"/collections/weekend-sale\",\n      \"channelId\": \"swan_notifications\",\n      \"carouselItems\": \"[{\\\"imageUrl\\\":\\\"https://picsum.photos/id/1/720/360\\\",\\\"title\\\":\\\"Summer Collection\\\",\\\"body\\\":\\\"50% off\\\",\\\"route\\\":\\\"/product/summer\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/20/720/360\\\",\\\"title\\\":\\\"New Arrivals\\\",\\\"body\\\":\\\"Just dropped\\\",\\\"route\\\":\\\"/product/new\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/30/720/360\\\",\\\"title\\\":\\\"Best Sellers\\\",\\\"body\\\":\\\"Top picks\\\",\\\"route\\\":\\\"/product/best\\\"}]\"\n    },\n    \"android\": {\n      \"priority\": \"high\"\n    }\n  }\n}"
-						}
-					}
-				},
-				{
-					"name": "Carousel — Manual / Filmstrip",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"notificationType\": \"carousel\",\n      \"carouselMode\": \"manual\",\n      \"carouselVariant\": \"filmstrip\",\n      \"title\": \"Trending Now\",\n      \"body\": \"See what's popular\",\n      \"defaultRoute\": \"/trending\",\n      \"channelId\": \"swan_notifications\",\n      \"carouselItems\": \"[{\\\"imageUrl\\\":\\\"https://picsum.photos/id/40/720/360\\\",\\\"title\\\":\\\"Watches\\\",\\\"body\\\":\\\"From $99\\\",\\\"route\\\":\\\"/product/watches\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/50/720/360\\\",\\\"title\\\":\\\"Sneakers\\\",\\\"body\\\":\\\"New colors\\\",\\\"route\\\":\\\"/product/sneakers\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/60/720/360\\\",\\\"title\\\":\\\"Bags\\\",\\\"body\\\":\\\"Premium leather\\\",\\\"route\\\":\\\"/product/bags\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/70/720/360\\\",\\\"title\\\":\\\"Sunglasses\\\",\\\"body\\\":\\\"UV protection\\\",\\\"route\\\":\\\"/product/sunglasses\\\"}]\"\n    },\n    \"android\": {\n      \"priority\": \"high\"\n    }\n  }\n}"
-						}
-					}
-				},
-				{
-					"name": "Carousel — Auto Scroll",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"notificationType\": \"carousel\",\n      \"carouselMode\": \"auto\",\n      \"carouselVariant\": \"standard\",\n      \"carouselInterval\": \"4000\",\n      \"title\": \"Flash Deals\",\n      \"body\": \"Auto-scrolling deals!\",\n      \"defaultRoute\": \"/deals\",\n      \"channelId\": \"swan_notifications\",\n      \"carouselItems\": \"[{\\\"imageUrl\\\":\\\"https://picsum.photos/id/10/720/360\\\",\\\"title\\\":\\\"Deal 1\\\",\\\"body\\\":\\\"60% off\\\",\\\"route\\\":\\\"/deal/1\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/11/720/360\\\",\\\"title\\\":\\\"Deal 2\\\",\\\"body\\\":\\\"Buy 1 Get 1\\\",\\\"route\\\":\\\"/deal/2\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/12/720/360\\\",\\\"title\\\":\\\"Deal 3\\\",\\\"body\\\":\\\"Free shipping\\\",\\\"route\\\":\\\"/deal/3\\\"}]\"\n    },\n    \"android\": {\n      \"priority\": \"high\"\n    }\n  }\n}"
-						}
-					}
-				},
-				{
-					"name": "Silent Push",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"silent\": \"true\",\n      \"action\": \"sync_config\"\n    },\n    \"android\": {\n      \"priority\": \"high\"\n    }\n  }\n}"
-						}
-					}
-				}
-			]
-		},
-		{
-			"name": "iOS",
-			"item": [
-				{
-					"name": "Standard Push",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"title\": \"Your order has shipped!\",\n      \"body\": \"Track your package #ABC123\",\n      \"route\": \"/orders/123\"\n    },\n    \"apns\": {\n      \"headers\": {\n        \"apns-push-type\": \"alert\",\n        \"apns-priority\": \"10\"\n      },\n      \"payload\": {\n        \"aps\": {\n          \"content-available\": 1\n        }\n      }\n    }\n  }\n}"
-						}
-					}
-				},
-				{
-					"name": "Standard Push — With Image",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"title\": \"Summer Sale!\",\n      \"body\": \"50% off everything\",\n      \"route\": \"/sales/summer\",\n      \"image\": \"https://picsum.photos/id/1/1024/512\"\n    },\n    \"apns\": {\n      \"headers\": {\n        \"apns-push-type\": \"alert\",\n        \"apns-priority\": \"10\"\n      },\n      \"payload\": {\n        \"aps\": {\n          \"content-available\": 1\n        }\n      }\n    }\n  }\n}"
-						}
-					}
-				},
-				{
-					"name": "Carousel — Manual / Standard",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"notificationType\": \"carousel\",\n      \"carouselMode\": \"manual\",\n      \"carouselVariant\": \"standard\",\n      \"title\": \"Weekend Flash Sale\",\n      \"body\": \"Swipe to explore deals!\",\n      \"defaultRoute\": \"/collections/weekend-sale\",\n      \"channelId\": \"swan_notifications\",\n      \"carouselItems\": \"[{\\\"imageUrl\\\":\\\"https://picsum.photos/id/1/720/360\\\",\\\"title\\\":\\\"Summer Collection\\\",\\\"body\\\":\\\"50% off\\\",\\\"route\\\":\\\"/product/summer\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/20/720/360\\\",\\\"title\\\":\\\"New Arrivals\\\",\\\"body\\\":\\\"Just dropped\\\",\\\"route\\\":\\\"/product/new\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/30/720/360\\\",\\\"title\\\":\\\"Best Sellers\\\",\\\"body\\\":\\\"Top picks\\\",\\\"route\\\":\\\"/product/best\\\"}]\"\n    },\n    \"apns\": {\n      \"headers\": {\n        \"apns-push-type\": \"alert\",\n        \"apns-priority\": \"10\"\n      },\n      \"payload\": {\n        \"aps\": {\n          \"mutable-content\": 1,\n          \"category\": \"swan_carousel\",\n          \"alert\": {\n            \"title\": \"Weekend Flash Sale\",\n            \"body\": \"Swipe to explore deals!\"\n          }\n        }\n      }\n    }\n  }\n}"
-						}
-					}
-				},
-				{
-					"name": "Carousel — Manual / Filmstrip",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"notificationType\": \"carousel\",\n      \"carouselMode\": \"manual\",\n      \"carouselVariant\": \"filmstrip\",\n      \"title\": \"Trending Now\",\n      \"body\": \"See what's popular\",\n      \"defaultRoute\": \"/trending\",\n      \"channelId\": \"swan_notifications\",\n      \"carouselItems\": \"[{\\\"imageUrl\\\":\\\"https://picsum.photos/id/40/720/360\\\",\\\"title\\\":\\\"Watches\\\",\\\"body\\\":\\\"From $99\\\",\\\"route\\\":\\\"/product/watches\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/50/720/360\\\",\\\"title\\\":\\\"Sneakers\\\",\\\"body\\\":\\\"New colors\\\",\\\"route\\\":\\\"/product/sneakers\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/60/720/360\\\",\\\"title\\\":\\\"Bags\\\",\\\"body\\\":\\\"Premium leather\\\",\\\"route\\\":\\\"/product/bags\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/70/720/360\\\",\\\"title\\\":\\\"Sunglasses\\\",\\\"body\\\":\\\"UV protection\\\",\\\"route\\\":\\\"/product/sunglasses\\\"}]\"\n    },\n    \"apns\": {\n      \"headers\": {\n        \"apns-push-type\": \"alert\",\n        \"apns-priority\": \"10\"\n      },\n      \"payload\": {\n        \"aps\": {\n          \"mutable-content\": 1,\n          \"category\": \"swan_carousel\",\n          \"alert\": {\n            \"title\": \"Trending Now\",\n            \"body\": \"See what's popular\"\n          }\n        }\n      }\n    }\n  }\n}"
-						}
-					}
-				},
-				{
-					"name": "Carousel — Auto Scroll",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"notificationType\": \"carousel\",\n      \"carouselMode\": \"auto\",\n      \"carouselVariant\": \"standard\",\n      \"carouselInterval\": \"4000\",\n      \"title\": \"Flash Deals\",\n      \"body\": \"Auto-scrolling deals!\",\n      \"defaultRoute\": \"/deals\",\n      \"channelId\": \"swan_notifications\",\n      \"carouselItems\": \"[{\\\"imageUrl\\\":\\\"https://picsum.photos/id/10/720/360\\\",\\\"title\\\":\\\"Deal 1\\\",\\\"body\\\":\\\"60% off\\\",\\\"route\\\":\\\"/deal/1\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/11/720/360\\\",\\\"title\\\":\\\"Deal 2\\\",\\\"body\\\":\\\"Buy 1 Get 1\\\",\\\"route\\\":\\\"/deal/2\\\"},{\\\"imageUrl\\\":\\\"https://picsum.photos/id/12/720/360\\\",\\\"title\\\":\\\"Deal 3\\\",\\\"body\\\":\\\"Free shipping\\\",\\\"route\\\":\\\"/deal/3\\\"}]\"\n    },\n    \"apns\": {\n      \"headers\": {\n        \"apns-push-type\": \"alert\",\n        \"apns-priority\": \"10\"\n      },\n      \"payload\": {\n        \"aps\": {\n          \"mutable-content\": 1,\n          \"category\": \"swan_carousel\",\n          \"alert\": {\n            \"title\": \"Flash Deals\",\n            \"body\": \"Auto-scrolling deals!\"\n          }\n        }\n      }\n    }\n  }\n}"
-						}
-					}
-				},
-				{
-					"name": "Silent Push",
-					"request": {
-						"method": "POST",
-						"header": [
-							{
-								"key": "Authorization",
-								"value": "Bearer {{access_token}}"
-							},
-							{
-								"key": "Content-Type",
-								"value": "application/json"
-							}
-						],
-						"url": {
-							"raw": "{{fcm_url}}",
-							"host": ["{{fcm_url}}"]
-						},
-						"body": {
-							"mode": "raw",
-							"raw": "{\n  \"message\": {\n    \"token\": \"{{fcm_token}}\",\n    \"data\": {\n      \"silent\": \"true\",\n      \"action\": \"sync_config\"\n    },\n    \"apns\": {\n      \"headers\": {\n        \"apns-push-type\": \"background\",\n        \"apns-priority\": \"5\"\n      },\n      \"payload\": {\n        \"aps\": {\n          \"content-available\": 1\n        }\n      }\n    }\n  }\n}"
-						}
-					}
-				}
-			]
-		}
-	]
-}

package/docs/deep-link-attribution.md

@@ -1,281 +0,0 @@
-# Deep Link Attribution Tracking
-
-Track campaign clicks from email, SMS, and WhatsApp to measure which campaigns drive app engagement.
-
-## Overview
-
-When your marketing team sends emails, SMS, or WhatsApp messages containing links to your app, the Swan SDK automatically detects these clicks and reports them to the Swan backend for campaign attribution. This enables funnel tracking: **link click → app open → add to cart → purchase**.
-
-**No code changes required.** The SDK handles everything automatically after `init()`. Your existing deep link routing continues to work as-is — the SDK only adds silent attribution tracking on top.
-
-## How It Works
-
-```
-User receives email/SMS/WhatsApp with campaign link
-         ↓
-User taps link → App opens via deep link
-         ↓
-React Native Linking API fires → Swan SDK intercepts
-         ↓
-SDK checks for swan_ parameters in the URL
-         ↓
-  ┌─ swan_ params found → Send click ACK to Swan backend
-  └─ No swan_ params → Ignore (not a Swan campaign link)
-         ↓
-App's existing deep link routing handles navigation (unaffected)
-```
-
-The SDK supports both:
-- **Warm start** — app is already running in the background
-- **Cold start** — app is launched from a killed state via the deep link
-
-## Prerequisites
-
-For the SDK to receive deep links, your app must be configured to handle them at the platform level. Most React Native apps that support any form of deep linking already have this set up.
-
-### Android
-
-Add intent filters to your `AndroidManifest.xml` inside the `<activity>` tag for `MainActivity`:
-
-**Custom scheme** (e.g., `yourapp://products/123`):
-
-```xml
-<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:scheme="yourapp" />
-</intent-filter>
-```
-
-**HTTPS App Links** (e.g., `https://yourstore.com/products/123`):
-
-```xml
-<intent-filter android:autoVerify="true">
-    <action android:name="android.intent.action.VIEW" />
-    <category android:name="android.intent.category.DEFAULT" />
-    <category android:name="android.intent.category.BROWSABLE" />
-    <data android:scheme="https" android:host="yourstore.com" />
-</intent-filter>
-```
-
-> For HTTPS App Links, you also need to host a Digital Asset Links file at `https://yourstore.com/.well-known/assetlinks.json`. See the [Android App Links documentation](https://developer.android.com/training/app-links) for details.
-
-### iOS
-
-**Custom scheme:**
-
-Add your URL scheme in Xcode: **Target → Info → URL Types → Add URL Scheme** (e.g., `yourapp`).
-
-Or in `Info.plist`:
-
-```xml
-<key>CFBundleURLTypes</key>
-<array>
-    <dict>
-        <key>CFBundleURLSchemes</key>
-        <array>
-            <string>yourapp</string>
-        </array>
-    </dict>
-</array>
-```
-
-**AppDelegate setup:**
-
-Ensure your `AppDelegate.mm` passes URLs to React Native (this is included by default in most React Native projects):
-
-```objc
-- (BOOL)application:(UIApplication *)application
-            openURL:(NSURL *)url
-            options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options
-{
-  return [RCTLinkingManager application:application openURL:url options:options];
-}
-
-// For Universal Links
-- (BOOL)application:(UIApplication *)application
-    continueUserActivity:(nonnull NSUserActivity *)userActivity
-      restorationHandler:(nonnull void (^)(NSArray<id<UIUserActivityRestoring>> * _Nullable))restorationHandler
-{
-  return [RCTLinkingManager application:application
-                   continueUserActivity:userActivity
-                     restorationHandler:restorationHandler];
-}
-```
-
-**Universal Links** (e.g., `https://yourstore.com/products/123`):
-
-1. Add the Associated Domains entitlement in Xcode: `applinks:yourstore.com`
-2. Host an `apple-app-site-association` file at `https://yourstore.com/.well-known/apple-app-site-association`
-
-See the [Apple Universal Links documentation](https://developer.apple.com/documentation/xcode/supporting-universal-links-in-your-app) for details.
-
-### Expo
-
-Add the `scheme` property to your `app.json`:
-
-```json
-{
-  "expo": {
-    "scheme": "yourapp"
-  }
-}
-```
-
-Then run `npx expo prebuild` to regenerate native projects.
-
-## Campaign URL Format
-
-For attribution tracking to work, the backend must append Swan parameters to the campaign links before sending them. The SDK looks for query parameters prefixed with `swan_`.
-
-### Required Parameters
-
-| Parameter | Description | Example |
-|-----------|-------------|---------|
-| `swan_comm_id` | Communication ID (generated by Swan before sending) | `swan_comm_id=comm_abc123` |
-
-### Optional Parameters
-
-| Parameter | Description | Example |
-|-----------|-------------|---------|
-| `swan_link_id` | Identifies which link within the message was clicked (useful for emails with multiple CTAs) | `swan_link_id=hero_banner` |
-
-### Example Campaign URLs
-
-**Email with multiple links:**
-```
-https://yourstore.com/sale?swan_comm_id=email_001&swan_link_id=hero_banner
-https://yourstore.com/products/shoes?swan_comm_id=email_001&swan_link_id=category_cta
-https://yourstore.com/cart?swan_comm_id=email_001&swan_link_id=footer_link
-```
-
-**SMS with single link:**
-```
-https://yourstore.com/offer/50off?swan_comm_id=sms_002
-```
-
-**WhatsApp with custom scheme:**
-```
-yourapp://products/flash-sale?swan_comm_id=wa_003&swan_link_id=buy_now
-```
-
-> URLs without `swan_comm_id` are silently ignored by the SDK — there is zero overhead for non-campaign links.
-
-## Integration
-
-**No code changes required.** The SDK sets up deep link listeners automatically during `init()`. As long as:
-
-1. Your app's platform configuration handles deep links (see Prerequisites above)
-2. Campaign URLs include `swan_comm_id` as a query parameter
-
-...the SDK will automatically track clicks and send them to the Swan backend.
-
-```javascript
-import SwanEcomSDK from '@loyalytics/swan-react-native-sdk';
-
-// This is all you need — deep link tracking is included automatically
-const sdk = SwanEcomSDK.getInstance('YOUR_APP_ID', {
-  isProduction: true,
-});
-```
-
-Your existing deep link navigation code continues to work unchanged. The SDK does not interfere with routing — it only reads the URL parameters for attribution.
-
-## Backend Webhook Payload
-
-When a campaign deep link is clicked, the SDK sends a click acknowledgment to the Swan webhook endpoint. The payload includes:
-
-```json
-{
-  "commId": "email_001",
-  "appId": "your-app-id",
-  "CDID": "customer-device-id",
-  "event": "clicked",
-  "deviceId": "device-id",
-  "type": "deepLink",
-  "linkId": "hero_banner"
-}
-```
-
-| Field | Always present | Description |
-|-------|---------------|-------------|
-| `commId` | Yes | The `swan_comm_id` from the URL |
-| `type` | Yes | Always `"deepLink"` — distinguishes from push notification clicks |
-| `event` | Yes | Always `"clicked"` |
-| `linkId` | Only if `swan_link_id` was in the URL | Identifies which specific link was clicked |
-| `appId` | Yes | Your app ID |
-| `CDID` | Yes | Customer device ID (logged-in user) or generated anonymous ID |
-| `deviceId` | Yes | Device identifier |
-
-## Testing
-
-### Android
-
-```bash
-# Campaign link with all parameters
-adb shell am start -a android.intent.action.VIEW \
-  -d "yourapp://products/123?swan_comm_id=test_001&swan_link_id=cta1"
-
-# Campaign link without link ID (single-link SMS)
-adb shell am start -a android.intent.action.VIEW \
-  -d "yourapp://offer?swan_comm_id=test_002"
-
-# Non-campaign link (should be silently ignored)
-adb shell am start -a android.intent.action.VIEW \
-  -d "yourapp://products/123?utm_source=google"
-```
-
-### iOS Simulator
-
-```bash
-# Campaign link with all parameters
-xcrun simctl openurl booted \
-  "yourapp://products/123?swan_comm_id=test_001&swan_link_id=cta1"
-
-# Campaign link without link ID
-xcrun simctl openurl booted \
-  "yourapp://offer?swan_comm_id=test_002"
-
-# Non-campaign link (should be silently ignored)
-xcrun simctl openurl booted \
-  "yourapp://products/123?utm_source=google"
-```
-
-### Expected Log Output
-
-Enable SDK logging to verify attribution tracking:
-
-```javascript
-SwanEcomSDK.setLoggingEnabled(true);
-```
-
-**Campaign link detected:**
-```
-[SwanSDK] Deep link received (warm start): yourapp://products/123?swan_comm_id=test_001&swan_link_id=cta1
-[SwanSDK] Deep link attribution: found SWAN parameters: {"swan_comm_id":"test_001","swan_link_id":"cta1"}
-[SwanSDK] Notification ACK queued: test_001 clicked
-```
-
-**Non-campaign link (no output):**
-```
-[SwanSDK] Deep link received (warm start): yourapp://products/123?utm_source=google
-```
-No further logs — the SDK silently ignores it.
-
-## FAQ
-
-**Q: Do I need to change any code in my app?**
-No. The SDK handles deep link attribution automatically. Your existing navigation and deep link routing remains unchanged.
-
-**Q: What if my app already uses React Navigation's deep linking?**
-That's fine. The SDK uses `Linking.addEventListener` to listen for URLs, which works alongside React Navigation's `linking` configuration. Both receive the URL — React Navigation handles routing, the SDK handles attribution.
-
-**Q: What happens if the user clicks a link but is offline?**
-The click event is queued in the SDK's local SQLite database and sent to the backend when the network is restored.
-
-**Q: Does this add any overhead for non-campaign links?**
-Negligible. The SDK checks for `swan_` prefixed parameters in the URL query string. If none are found, it returns immediately with no further processing.
-
-**Q: What SDK version is required?**
-Deep link attribution tracking is available from version **2.1.0** onwards.