@attentive-mobile/attentive-react-native-sdk 2.0.0-beta.8 → 2.0.1

package/README.md

@@ -109,6 +109,7 @@ class MainApplication : Application(), ReactApplication {
             .applicationContext(this)
             .domain("YOUR_ATTENTIVE_DOMAIN")
             .mode(AttentiveConfig.Mode.PRODUCTION) // or Mode.DEBUG for testing
+            .notificationIconId(R.drawable.ic_stat_notification)
             .skipFatigueOnCreatives(false)
             .logLevel(AttentiveLogLevel.VERBOSE)
             .build()
@@ -120,6 +121,30 @@ class MainApplication : Application(), ReactApplication {
 }
 ```
 
+##### Android notification small icon
+
+Android requires push notifications to use a small status-bar icon. If `notificationIconId` is not set, the Attentive Android SDK uses its default fallback icon. To use your app's branding, add a notification small icon resource to your host app and pass its resource ID during native initialization.
+
+Add the icon to your Android app's drawable resources:
+
+```text
+android/app/src/main/res/drawable/ic_stat_notification.png
+```
+
+Use a white-only transparent PNG designed for Android notification status bars. Do not use the full-color launcher icon from `mipmap-*`, because Android masks small notification icons and it can render poorly.
+
+Then add the icon to your existing `AttentiveConfig.Builder()` chain in `MainApplication.kt` before `build()`:
+
+```text
+android/app/src/main/java/<your-package>/MainApplication.kt
+```
+
+```kotlin
+.notificationIconId(R.drawable.ic_stat_notification)
+```
+
+`MainApplication.kt` is host-app code, not generated by this SDK at runtime. If `R.drawable.ic_stat_notification` does not resolve, confirm the drawable file name matches exactly and that you are referencing your app module's `R` class.
+
 After the native initialization, all other SDK operations (`identify`, `recordAddToCartEvent`, `recordPurchaseEvent`, etc.) are called from TypeScript as normal on both platforms.
 
 > **Tip:** If you see `[AttentiveSDK] recordAddToCartEvent failed — SDK may not be initialized` in your Android logcat, it means `AttentiveSdk.initialize()` was not called from native code before the event was recorded. Check your `Application.onCreate()` setup.
@@ -281,57 +306,45 @@ identify({ email: 'user@example.com', clientUserId: 'id-123' });
 
 #### Push notifications on Android (FCM)
 
-On Android, FCM token registration and push notification handling are managed natively in Kotlin/Java. This gives you full control over the Firebase Messaging lifecycle and ensures events are tracked before the React Native bridge initialises.
+The Attentive Android SDK registers its own `FirebaseMessagingService` automatically — **you do not need to create a subclass**. As long as your app is registered with Firebase and includes a valid `google-services.json`, the SDK handles FCM token registration and foreground push delivery for you. Follow the [Firebase Android setup guide](https://firebase.google.com/docs/cloud-messaging/android/client) to add FCM to your project.
+
+##### If you already have a FirebaseMessagingService subclass
 
-Add Firebase Cloud Messaging to your app following the [Firebase Android setup guide](https://firebase.google.com/docs/cloud-messaging/android/client), then handle token registration and notification events in your native `FirebaseMessagingService`:
+If your app has an existing `FirebaseMessagingService` subclass for other purposes, route Attentive messages through to the SDK:
 
 ```kotlin
 import com.attentive.androidsdk.AttentiveSdk
 import com.google.firebase.messaging.FirebaseMessagingService
 import com.google.firebase.messaging.RemoteMessage
 
-class AttentiveMessagingService : FirebaseMessagingService() {
-
-    override fun onNewToken(token: String) {
-        super.onNewToken(token)
-        // Register the FCM token with the Attentive SDK
-        AttentiveSdk.registerDeviceToken(token)
-    }
+class YourFirebaseMessagingService : FirebaseMessagingService() {
 
     override fun onMessageReceived(remoteMessage: RemoteMessage) {
         super.onMessageReceived(remoteMessage)
-        // Handle foreground push delivery
-        AttentiveSdk.handleForegroundPush(remoteMessage.data)
+        if (AttentiveSdk.isAttentiveFirebaseMessage(remoteMessage)) {
+            AttentiveSdk.sendNotification(remoteMessage)
+        }
+        // Handle your own messages below...
     }
 }
 ```
 
-For notification opens (when the user taps a push notification), handle the intent in your main `Activity`:
+##### Notification opens (singleTask apps)
+
+React Native apps use `singleTask` launch mode by default. When a push notification is tapped while the app is in the background, Android delivers the intent via `onNewIntent()` rather than recreating the activity. Override `onNewIntent` in your `MainActivity` so the SDK can detect the notification tap:
 
 ```kotlin
-import com.attentive.androidsdk.AttentiveSdk
+import android.content.Intent
 
 class MainActivity : ReactActivity() {
 
-    override fun onResume() {
-        super.onResume()
-        intent?.let { AttentiveSdk.handlePushOpen(it) }
+    override fun onNewIntent(intent: Intent?) {
+        super.onNewIntent(intent)
+        intent?.let { setIntent(it) }
     }
 }
 ```
 
-Declare the service in your `AndroidManifest.xml`:
-
-```xml
-<service
-    android:name=".AttentiveMessagingService"
-    android:exported="false">
-    <intent-filter>
-        <action android:name="com.google.firebase.MESSAGING_EVENT" />
-    </intent-filter>
-</service>
-```
-
 Refer to the [Attentive Android SDK documentation](https://github.com/attentive-mobile/attentive-android-sdk) for the full list of native APIs available for push notification integration.
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@attentive-mobile/attentive-react-native-sdk",
-  "version": "2.0.0-beta.8",
+  "version": "2.0.1",
   "description": "React Native Module for the Attentive SDK",
   "main": "lib/commonjs/index",
   "module": "lib/module/index",
@@ -16,6 +16,10 @@
     "*.podspec",
     "!lib/typescript/example",
     "!ios/build",
+    "!ios/Pods",
+    "!ios/Podfile.lock",
+    "!ios/*.xcworkspace",
+    "!**/xcuserdata",
     "!android/build",
     "!android/gradle",
     "!android/gradlew",
@@ -111,7 +115,7 @@
   "release-it": {
     "git": {
       "commitMessage": "chore: release ${version}",
-      "tagName": "v${version}"
+      "tagName": "${version}"
     },
     "npm": {
       "publish": true