@iterable/react-native-sdk's android/build.gradle hard-pins the native Android SDK to com.iterable:iterableapi:3.6.2:
dependencies {
implementation "com.facebook.react:react-android"
implementation "org.jetbrains.kotlin:kotlin-stdlib:$kotlin_version"
api "com.iterable:iterableapi:3.6.2"
}
This is true even in the latest published wrapper version (3.1.0). However, iterable api's own changelog shows the fix for this exact bug landed in 3.6.6: "Fixed push notifications killing the existing activity when opened." So every app using @iterable/react-native-sdk today is still shipping the broken native behavior, four patch releases behind the fix.
Environment
@iterable/react-native-sdk: 3.0.1 (also reproduced against 3.1.0's build.gradle, same pin)
com.iterable:iterableapi(transitively resolved): 3.6.2
React Native: 0.85.3 (New Architecture / Fabric enabled)
Expo SDK: 56
HostActivity:android:launchMode="singleTask"
Expected behavior
Tapping a push notification while the app is already running should bring the existing MainActivity instance to the front via onNewIntent(), per the singleTask launch mode declared in the manifest.
Actual behavior
Tapping the notification intermittently causes Android to create a new task and a new MainActivity instance (onCreate fires with a new taskId/instance hash) instead of reusing the existing one. Because the app runs on the New Architecture (JS engine is Application-scoped rather than Activity-scoped), the JS context and React state survive, but the user sees the native splash screen flash again, which reads as an unexpected "app reload."
Please bump the pinned com.iterable:iterableapi version in android/build.gradle to ≥3.6.6 (or track latest) so RN apps get the activity-destruction fix.
@iterable/react-native-sdk's android/build.gradle hard-pins the native Android SDK to com.iterable:iterableapi:3.6.2:
This is true even in the latest published wrapper version (3.1.0). However, iterable api's own changelog shows the fix for this exact bug landed in 3.6.6: "Fixed push notifications killing the existing activity when opened." So every app using
@iterable/react-native-sdktoday is still shipping the broken native behavior, four patch releases behind the fix.Environment
@iterable/react-native-sdk: 3.0.1(also reproduced against 3.1.0's build.gradle, same pin)com.iterable:iterableapi(transitively resolved): 3.6.2
React Native: 0.85.3 (New Architecture / Fabric enabled)
Expo SDK: 56
HostActivity:android:launchMode="singleTask"
Expected behavior
Tapping a push notification while the app is already running should bring the existing MainActivity instance to the front via onNewIntent(), per the singleTask launch mode declared in the manifest.
Actual behavior
Tapping the notification intermittently causes Android to create a new task and a new MainActivity instance (onCreate fires with a new taskId/instance hash) instead of reusing the existing one. Because the app runs on the New Architecture (JS engine is Application-scoped rather than Activity-scoped), the JS context and React state survive, but the user sees the native splash screen flash again, which reads as an unexpected "app reload."
Please bump the pinned com.iterable:iterableapi version in android/build.gradle to ≥3.6.6 (or track latest) so RN apps get the activity-destruction fix.