Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In
`@android/app/src/main/java/chat/rocket/reactnative/notification/CustomPushNotification.java`:
- Around line 249-257: The code is adding bundle entries to notificationMessages
(keyed by notId) even for notifications that are later suppressed in foreground;
update the block around notificationMessages.get(notId).add(bundle) to first
check the suppression flag on the bundle (e.g.,
bundle.getBoolean("notificationLoaded", false) or the foreground-suppression
flag used later) and only add and call postNotification(Integer.parseInt(notId))
when the bundle is not suppressed; keep the verbose Log.d(TAG, ...) calls but
move them inside the guarded branch so suppressed notifications are neither
queued nor cause postNotification to run.
- Around line 51-91: The static field isAppInForeground is accessed from
multiple threads without synchronization; make it thread-safe by replacing the
plain boolean with a thread-safe construct (e.g.,
java.util.concurrent.atomic.AtomicBoolean) and update all usages: initialize a
private static final AtomicBoolean isAppInForeground = new AtomicBoolean(false),
change setAppInForeground(...) to call isAppInForeground.set(inForeground) and
change isAppInForeground() to return isAppInForeground.get(); ensure any other
direct reads/writes to the old boolean are updated to use the AtomicBoolean
methods (references: isAppInForeground field, setAppInForeground method,
isAppInForeground() method).

---

Nitpick comments:
In `@android/app/src/main/java/chat/rocket/reactnative/MainActivity.kt`:
- Around line 38-48: The current foreground/background tracking in MainActivity
via onResume/onPause (which calls CustomPushNotification.setAppInForeground) can
misfire during activity-to-activity transitions; replace or supplement this with
a process-level lifecycle observer using
androidx.lifecycle.ProcessLifecycleOwner: create a LifecycleObserver (or
implement DefaultLifecycleObserver) that calls
CustomPushNotification.setAppInForeground(true/false) on onStart/onStop
(process-level), register it in the Application class (e.g., in onCreate) so
state changes reflect the whole app lifecycle rather than MainActivity
transitions, and remove or keep MainActivity.onResume/onPause only if you need
activity-specific behaviour.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@android/app/src/main/java/chat/rocket/reactnative/MainActivity.kt`:
- Around line 38-48: The current MainActivity onResume/onPause usage toggles
CustomPushNotification.setAppInForeground and should be replaced with
process-level lifecycle tracking: remove or stop using MainActivity.onResume()
and onPause() to set the flag and instead register a ProcessLifecycleOwner
observer (e.g., implement DefaultLifecycleObserver or LifecycleObserver) that
calls CustomPushNotification.setAppInForeground(true) on onStart/onResume and
setAppInForeground(false) on onStop/onPause at the application/process level;
attach the observer via
ProcessLifecycleOwner.get().getLifecycle().addObserver(...) during app
initialization (Application.onCreate or MainActivity setup) so the flag reflects
the entire app visibility rather than a single Activity.

In
`@android/app/src/main/java/chat/rocket/reactnative/notification/CustomPushNotification.java`:
- Around line 292-297: The current early return when isAppInForeground() is true
drops notifications; modify the block in CustomPushNotification so it either (A)
only suppresses the native notification if the payload's conversationId matches
the currently open conversation (compare payload.get("conversationId") against
your active convo accessor, e.g., getActiveConversationId()), or (B) before
returning forward the full payload into the app's foreground notification
handler (invoke the existing JS bridge/handler used for in-app notifications,
e.g., sendEventToJS or handleInAppNotification(payload)) so messages received
while the app is foregrounded are delivered to the JS layer instead of being
discarded. Ensure you use isAppInForeground() and the payload/conversationId
fields already available in this class to implement the chosen behavior and
remove the unconditional return.

---

Outside diff comments:
In
`@android/app/src/main/java/chat/rocket/reactnative/notification/CustomPushNotification.java`:
- Around line 50-91: The static boolean isAppInForeground can be cached across
threads; make its visibility thread-safe by adding the volatile modifier to its
declaration (change "private static boolean isAppInForeground" to "private
static volatile boolean isAppInForeground") so reads in
FirebaseMessagingService.onMessageReceived() observe updates made by
MainActivity via setAppInForeground(); keep the existing setAppInForeground()
and isAppInForeground() methods unchanged.