Adding Push Notifications (V2)

Adding Push Notifications To Your Application

Introduction

Push notifications are a core part of the experience for a messaging app. Users often need to be notified of new messages and old notifications sometimes need to be updated silently.

This guide details how to add push notifications to your app.

You can read more about Stream’s push delivery logic.

Setup FCM

To integrate push notifications in your Flutter app, you need to use the package firebase_messaging.

Follow the Firebase documentation to set up the plugin for Android and iOS.

Once that’s done, FCM should be able to send push notifications to your devices.

Integration With Stream

Step 1 - Get the Firebase Credentials

These credentials are the private key file for your service account, in firebase console.

To generate a private key file for your service account, in the Firebase console:

• Open Settings > Service Accounts.

• Click Generate New Private Key, then confirm by clicking Generate Key.

• Securely store the JSON file containing the key.

This JSON file contains the credentials which needs to be uploaded to Stream’s server as explained in next step.

Step 2 - Upload the Firebase Credentials to Stream

You can upload your Firebase credentials using either the dashboard or the app settings API (available only in backend SDKs).

Using the Stream Dashboard

1. Go to the Chat Overview page on Stream Dashboard

2. Enable Firebase Notification toggle on Chat Overview

3. Enter your Firebase Credentials and press "Save".

Using the API

You can also enable Firebase notifications and upload the Firebase credentials using one of our server SDKs.

For example, using the JavaScript SDK:

const client = StreamChat.getInstance('api_key', 'api_secret');
client.updateAppSettings({
  push_config: {
    version: 'v2'
  },
  firebase_config: {
    credentials_json: fs.readFileSync(
      './firebase-credentials.json',
      'utf-8',
    ),
 });

Registering a Device With Stream Backend

Once you configure a Firebase server key and set it up on Stream dashboard then a device that is supposed to receive push notifications needs to be registered on the Stream backend. This is usually done by listening for Firebase device token updates and passing them to the backend as follows:

firebaseMessaging.onTokenRefresh.listen((token) {
      client.addDevice(token, PushProvider.firebase);
});

Push Notifications v2 also supports specifying a name to the push device tokens you register. By setting the optional pushProviderName parameter in the addDevice call you can support different configurations between the device and the PushProvider.

firebaseMessaging.onTokenRefresh.listen((token) {
      client.addDevice(token, PushProvider.firebase, pushProviderName: 'my-custom-config');
});

Receiving Notifications

Push notifications behave a bit differently depending on whether you are using iOS or Android. See here to understand the difference between notification and data payloads.

iOS

On iOS we send both a notification and a data payload. This means you don’t need to do anything special to get the notification to show up. However, you might want to handle the data payload to perform some logic when the user taps on the notification.

To update the template, you can use a backend SDK. For example, using the JavaScript SDK:

const client = StreamChat.getInstance(‘api_key’, ‘api_secret’);
const apn_template = `{
	"aps": {
		"alert": {
			"title": "New message from {{ sender.name }}",
			"body": "{{ truncate message.text 2000 }}"
		},
		"mutable-content": 1,
		"category": "stream.chat"
	},
	"stream": {
		"sender": "stream.chat",
      "type": "message.new",
      "version": "v2",
      "id": "{{ message.id }}",
      "cid": "{{ channel.cid }}"
	}
}`;

client.updateAppSettings({
  firebase_config: {
    apn_template,
 });

Android

On Android we send only a data payload. This gives you more flexibility and lets you decide what to do with the notification.

For example, you can listen and generate a notification from them.

To generate a notification when a data-only message is received and the app is in background:

Future<void> onBackgroundMessage(RemoteMessage message) async {
  final chatClient = StreamChatClient(apiKey);

  chatClient.connectUser(
    User(id: userId),
    userToken,
    connectWebSocket: false,
  );

  handleNotification(message, chatClient);
}

void handleNotification(
  RemoteMessage message,
  StreamChatClient chatClient,
) async {

  final data = message.data;

  if (data['type'] == 'message.new') {
    final flutterLocalNotificationsPlugin = await setupLocalNotifications();
    final messageId = data['id'];
    final response = await chatClient.getMessage(messageId);

    flutterLocalNotificationsPlugin.show(
      1,
      'New message from ${response.message.user.name} in ${response.channel.name}',
      response.message.text,
      NotificationDetails(
          android: AndroidNotificationDetails(
        'new_message',
        'New message notifications channel',
      )),
    );
  }
}

FirebaseMessaging.onBackgroundMessage(onBackgroundMessage);

In the above example, you get the message details using the getMessage method and then you use the flutter_local_notifications package to show the actual notification.

Using a Template on Android

It’s still possible to add a notification payload to Android notifications. You can do so by adding a template using a backend SDK. For example, using the JavaScript SDK:

const client = StreamChat.getInstance(‘api_key’, ‘api_secret’);
const notification_template = `
{
    "title": "{{ sender.name }} @ {{ channel.name }}",
    "body": "{{ message.text }}",
    "click_action": "OPEN_ACTIVITY_1",
    "sound": "default"
}`;

client.updateAppSettings({
  firebase_config: {
    notification_template,
 });

Possible Issues

Make sure to read the general push notification docs in order to avoid known gotchas that may make your relationship with notifications difficult 😢.

Testing if Push Notifications are Setup Correctly

If you’re not sure whether you’ve set up push notifications correctly, for example, you don’t always receive them, or they don’t work reliably, then you can follow these steps to make sure your configuration is correct and working:

1. Clone our repository for push testing: git clone git@github.com:GetStream/chat-push-test.git
2. cd flutter
3. In that folder run flutter pub get
4. Input your API key and secret in lib/main.dart
5. Change the bundle identifier/application ID and development team/user so you can run the app on your physical device.Do not run on an iOS simulator, as it will not work. Testing on an Android emulator is fine.
6. Add your google-services.json/GoogleService-Info.plist
7. Run the app
8. Accept push notification permission (iOS only)
9. Tap on Device ID and copy it
10. After configuring stream-cli, run the following command using your user ID:

stream chat:push:test -u <USER-ID>

You should get a test push notification 🥳

Foreground Notifications

Sometimes you may want to show a notification when the app is in the foreground. For example, when you’re in a channel and you receive a new message from someone in another channel.

For this scenario, you can also use the flutter_local_notifications package to show a notification.

You need to listen for new events using FirebaseMessaging.onMessage.listen() and handle them accordingly:

FirebaseMessaging.onMessage.listen((message) async {
  handleNotification(
    message,
    chatClient,
  );
});

Saving Notification Messages to the Offline Storage (Only Android)

When the app is closed you may want to save received messages when you receive them via a notification so that later on when you open the app they’re already there.

To do this you need to integrate the package stream_chat_persistence in our app that exports a persistence client, see here how to set it up.

Then calling FirebaseMessaging.onBackgroundMessage(...) you need to use a TOP-LEVEL or STATIC function to handle background messages; here is an example:

Future<void> onBackgroundMessage(RemoteMessage message) async {
  final chatClient = StreamChatClient(apiKey);
  final persistenceClient = StreamChatPersistenceClient();

  await persistenceClient.connect(userId);

  chatClient.connectUser(
    User(id: userId),
    userToken,
    connectWebSocket: false,
  );

  handleNotification(message, chatClient);
}

void handleNotification(
  RemoteMessage message,
  StreamChatClient chatClient,
) async {
  final data = message.data;
  if (data['type'] == 'message.new') {
    final flutterLocalNotificationsPlugin = await setupLocalNotifications();
    final messageId = data['id'];
    final cid = data['cid'];
    final response = await chatClient.getMessage(messageId);
    await persistenceClient.updateMessages(cid, [response.message]);

    persistenceClient.disconnect();

    flutterLocalNotificationsPlugin.show(
      1,
      'New message from ${response.message.user.name} in ${response.channel.name}',
      response.message.text,
      NotificationDetails(
          android: AndroidNotificationDetails(
        'new_message',
        'New message notifications channel',
      )),
    );
  }
}

FirebaseMessaging.onBackgroundMessage(onBackgroundMessage);