I fixed this issue by overriding the MessagingService of the react-native-fcm library. This gives the effect of IntercomIntentService not being used since the push handling happens in the class OverriddenMessagingService (just an example name).

Example:

public class OverriddenMessagingService extends MessagingService {
    private static final String TAG = "OverriddenMessagingService";
    private final IntercomPushClient intercomPushClient = new IntercomPushClient();

    @Override
    public void onMessageReceived(RemoteMessage remoteMessage) {
        Map message = remoteMessage.getData();
        if (intercomPushClient.isIntercomPush(message)) {
            Log.d(TAG, "Intercom message received");
            intercomPushClient.handlePush(getApplication(), message);
        } else {
            super.onMessageReceived(remoteMessage);
        }
    }
}

@vvusts - ha, nope - I realised that a couple hours after I implemented this…

I moved the creation of the channels to native land and now I can. So in my MainApplication.java I now have:

    @Override
    public void onCreate() {
        // ...
        SoLoader.init(this, /* native exopackage */ false);
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
            int importance = NotificationManager.IMPORTANCE_HIGH;
            NotificationChannel intercomChannel = new NotificationChannel("intercom_chat_replies_channel", "Intercom Replies", importance);
            intercomChannel.setDescription("Replies from Support (Chat to us)");
            NotificationManager notificationManager = getSystemService(NotificationManager.class);
            assert notificationManager != null;
            notificationManager.createNotificationChannel(intercomChannel);
        }
    }

@jrbaudin I implemented the following and still could not get it working. Could you be more specific? Do I need to do any JS for this to work? Will using any of the libraries JS functions override what’s done here? Which server key did you use: legacy or standard? Did you specify a sender id? My FCM notifications are working from firebase, just not from Intercom. I’m using react-native-firebase, would make a difference in my overrides? They seem to have the same classes.

package com.my.app;

import io.invertase.firebase.messaging.*;
import android.content.Intent;
import android.os.Bundle;
import android.util.Log;
import io.intercom.android.sdk.push.IntercomPushClient;
import com.google.firebase.iid.FirebaseInstanceId;
import com.google.firebase.iid.FirebaseInstanceIdService;

public class MainInstanceIdService extends InstanceIdService {
  private final IntercomPushClient intercomPushClient = new IntercomPushClient();
  private static final String TAG = "InstanceIdService";

  /**
   * Called if InstanceID token is updated. This may occur if the security of
   * the previous token had been compromised. This call is initiated by the
   * InstanceID provider.
   */
  @Override
  public void onTokenRefresh() {
    // Get updated InstanceID token.
    String refreshedToken = FirebaseInstanceId.getInstance().getToken();
    intercomPushClient.sendTokenToIntercom(getApplication(), refreshedToken);
    Log.d(TAG, "Refreshed token: " + refreshedToken);

    // Broadcast refreshed token
    Intent i = new Intent("io.invertase.firebase.messaging.FCMRefreshToken");
    Bundle bundle = new Bundle();
    bundle.putString("token", refreshedToken);
    i.putExtras(bundle);
    sendBroadcast(i);
  }
}
///
package com.my.app;
import io.invertase.firebase.messaging.*;
import android.content.Intent;
import android.content.Context;
import io.intercom.android.sdk.push.IntercomPushClient;
import com.google.firebase.messaging.RemoteMessage;
import android.util.Log;
import java.util.Map;

public class MainMessagingService extends MessagingService {
    private static final String TAG = "MainMessagingService";
    private final IntercomPushClient intercomPushClient = new IntercomPushClient();

    @Override
    public void onMessageReceived(RemoteMessage remoteMessage) {
        Map message = remoteMessage.getData();
        if (intercomPushClient.isIntercomPush(message)) {
            Log.d(TAG, "Intercom message received");
            intercomPushClient.handlePush(getApplication(), message);
        } else {
            super.onMessageReceived(remoteMessage);
        }
    }
}

@vongohren had same problem on nativescript.

implementation 'io.intercom.android:intercom-sdk-base:6.+'

does not create notification channel for push notifications

implementation 'io.intercom.android:intercom-sdk:6.+'

solved the problem. Didn’t spot that sdk-base and sdk difference at first…

I would like to add one update to this.

Solution from @mtford90 works well. But later I found that Intercom Android SDK implements this on their own, since version 4.0.0 here changelog:

What fixed the same issue for me was using this sdk in my build.gradle

implementation 'io.intercom.android:intercom-sdk:5.+'

I removed the io.intercom.android:intercom-sdk-fcm:5.+ which was recommended in readme here.

After this it all worked out of the box.

@vvusts

import android.app.NotificationChannel;
import android.app.NotificationManager;

This + the solution in #208 helped me out. I’m using react-native-firebase and react-native-intercom with FCM. I had to add this MessagingService code, but also had to remove the <service android:name="io.invertase.firebase.messaging.RNFirebaseMessagingService"> <intent-filter> <action android:name="com.google.firebase.MESSAGING_EVENT" /> </intent-filter> </service> <service android:name="io.invertase.firebase.messaging.RNFirebaseInstanceIdService"> <intent-filter> <action android:name="com.google.firebase.INSTANCE_ID_EVENT"/> </intent-filter> </service> code in the manifest in favour of the manifest code specified in these issues.