Guard deconstructRegistration against null Registration (#520691) (#451)

Intercom.client().fetchLoggedInUserAttributes() returns null when no user
is logged in (e.g. after the OS kills and restarts the process, clearing
the native session). Both the oldarch and newarch IntercomModule pass that
return value straight into IntercomHelpers.deconstructRegistration(), which
immediately calls registration.getEmail() and throws a fatal
NullPointerException on the JS bridge thread.

Return an empty map when registration is null, matching the iOS bridge,
which resolves an empty dictionary for the same "no logged-in user" case.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: imSzukala

android/src/main/java/com/intercom/reactnative/IntercomHelpers.java

@@ -246,8 +246,15 @@ public static String getValueAsStringForKey(ReadableMap map, String key) {
     return value;
   }
 
-  public static WritableMap deconstructRegistration(Registration registration) {
+  public static WritableMap deconstructRegistration(@Nullable Registration registration) {
     WritableMap registrationMap = Arguments.createMap();
+    if (registration == null) {
+      // Intercom.client().fetchLoggedInUserAttributes() returns null when no user is
+      // logged in (e.g. after the OS kills and restarts the process, clearing the session).
+      // Return an empty map to match the iOS bridge, which resolves an empty dictionary
+      // for the same "no logged-in user" case instead of crashing.
+      return registrationMap;
+    }
     if (registration.getEmail() != null) {
       registrationMap.putString("email", registration.getEmail());
     }