django-push-notifications 3.1.0

Dependencies

• Python 3.7+

• Django 2.2+

• For the API module, Django REST Framework 3.7+ is required.

• For WebPush (WP), pywebpush 1.3.0+ is required (optional). py-vapid 1.3.0+ is required for generating the WebPush private key; however this step does not need to occur on the application server.

• For Apple Push (APNS), apns2 0.3+ is required (optional).

• For FCM, firebase-admin 6.2+ is required (optional).

Setup

You can install the library directly from pypi using pip:

$ pip install django-push-notifications[WP,APNS,FCM]

Edit your settings.py file:

INSTALLED_APPS = (
        ...
        "push_notifications"
)

# Import the firebase service
from firebase_admin import auth

# Initialize the default app (either use `GOOGLE_APPLICATION_CREDENTIALS` environment variable, or pass a firebase_admin.credentials.Certificate instance)
default_app = firebase_admin.initialize_app()

PUSH_NOTIFICATIONS_SETTINGS = {
        "APNS_CERTIFICATE": "/path/to/your/certificate.pem",
        "APNS_TOPIC": "com.example.push_test",
        "WNS_PACKAGE_SECURITY_ID": "[your package security id, e.g: 'ms-app://e-3-4-6234...']",
        "WNS_SECRET_KEY": "[your app secret key, e.g.: 'KDiejnLKDUWodsjmewuSZkk']",
        "WP_PRIVATE_KEY": "/path/to/your/private.pem",
        "WP_CLAIMS": {'sub': "mailto:development@example.com"}
}

For more information about how to generate certificates, see docs/APNS.

You can learn more about APNS certificates here.

Native Django migrations are in use. manage.py migrate will install and migrate all models.

Settings list

All settings are contained in a PUSH_NOTIFICATIONS_SETTINGS dict.

For APNS, you are required to include APNS_CERTIFICATE. For WNS, you need both the WNS_PACKAGE_SECURITY_KEY and the WNS_SECRET_KEY.

General settings

• USER_MODEL: Your user model of choice. Eg. myapp.User. Defaults to settings.AUTH_USER_MODEL.

• UPDATE_ON_DUPLICATE_REG_ID: Transform create of an existing Device (based on registration id) into a update. See below Update of device with duplicate registration ID for more details.

• UNIQUE_REG_ID: Forces the registration_id field on all device models to be unique.

APNS settings

• APNS_CERTIFICATE: Absolute path to your APNS certificate file. Certificates with passphrases are not supported. If iOS application was build with “Release” flag, you need to use production certificate, otherwise debug. Read more about Generation of an APNS PEM file.

• APNS_AUTH_KEY_PATH: Absolute path to your APNS signing key file for Token-Based Authentication . Use this instead of APNS_CERTIFICATE if you are using .p8 signing key certificate.

• APNS_AUTH_KEY_ID: The 10-character Key ID you obtained from your Apple developer account

• APNS_TEAM_ID: 10-character Team ID you use for developing your company’s apps for iOS.

• APNS_TOPIC: The topic of the remote notification, which is typically the bundle ID for your app. If you omit this header and your APNs certificate does not specify multiple topics, the APNs server uses the certificate’s Subject as the default topic.

• APNS_USE_ALTERNATIVE_PORT: Use port 2197 for APNS, instead of default port 443.

• APNS_USE_SANDBOX: Use ‘api.development.push.apple.com’, instead of default host ‘api.push.apple.com’. Default value depends on DEBUG setting of your environment: if DEBUG is True and you use production certificate, you should explicitly set APNS_USE_SANDBOX to False.

FCM/GCM settings

• FIREBASE_APP: Firebase app instance that is used to send the push notification. If not provided, the app will be using the default app instance that you’ve instantiated with firebase_admin.initialize_app().

• FCM_MAX_RECIPIENTS: The maximum amount of recipients that can be contained per bulk message. If the registration_ids list is larger than that number, multiple bulk messages will be sent. Defaults to 1000 (the maximum amount supported by FCM).

WNS settings

• WNS_PACKAGE_SECURITY_KEY: TODO

• WNS_SECRET_KEY: TODO

WP settings

• WP_PRIVATE_KEY: Absolute path to your private certificate file: os.path.join(BASE_DIR, “private_key.pem”)

• WP_CLAIMS: Dictionary with default value for the sub, (subject), sent to the webpush service, This would be used by the service if they needed to reach out to you (the sender). Could be a url or mailto e.g. {‘sub’: “mailto:development@example.com”}.

• WP_ERROR_TIMEOUT: The timeout on WebPush POSTs. (Optional)

For more information about how to configure WebPush, see docs/WebPush.

Sending messages

FCM/GCM and APNS services have slightly different semantics. The app tries to offer a common interface for both when using the models.

      from push_notifications.models import APNSDevice, GCMDevice

      device = GCMDevice.objects.get(registration_id=gcm_reg_id)
      # The first argument will be sent as "message" to the intent extras Bundle
      # Retrieve it with intent.getExtras().getString("message")
      device.send_message("You've got mail")
      # If you want to customize, send an extra dict and a None message.
      # the extras dict will be mapped into the intent extras Bundle.
      # For dicts where all values are keys this will be sent as url parameters,
      # but for more complex nested collections the extras dict will be sent via
      # the bulk message api.
      device.send_message(None, extra={"foo": "bar"})
      device.send_message(None, extra={"foo": "bar"}, use_fcm_notifications=False) # Silent message with custom data.

# You may also pass a Firebase message object.
      device.send_message(messaging.Message(
              notification=messaging.Notification(
                      title='Hello World',
                      body='What a beautiful day.'
              ),
      ))
      # If you want to use gcm.send_message directly, you will have to use messaging.Message.

      device = APNSDevice.objects.get(registration_id=apns_token)
      device.send_message("You've got mail") # Alert message may only be sent as text.
      device.send_message(None, badge=5) # No alerts but with badge.
      device.send_message(None, content_available=1, extra={"foo": "bar"}) # Silent message with custom data.
      # alert with title and body.
      device.send_message(message={"title" : "Game Request", "body" : "Bob wants to play poker"}, extra={"foo": "bar"})
      device.send_message("Hello again", thread_id="123", extra={"foo": "bar"}) # set thread-id to allow iOS to merge notifications

Web Push accepts only one variable (message), which is passed directly to pywebpush. This message can be a simple string, which will be used as your notification’s body, or it can be contain any data supported by pywebpush<https://github.com/web-push-libs/pywebpush>.

Simple example:

from push_notifications.models import WebPushDevice

device = WebPushDevice.objects.get(registration_id=wp_reg_id)

device.send_message("You've got mail")

JSON example:

import json
from push_notifications.models import WebPushDevice

device = WebPushDevice.objects.get(registration_id=wp_reg_id)

title = "Message Received"
message = "You've got mail"
data = json.dumps({"title": title, "message": message})

device.send_message(data)

Sending messages in bulk

from push_notifications.models import APNSDevice, GCMDevice

devices = GCMDevice.objects.filter(user__first_name="James")
devices.send_message("Happy name day!")

Sending messages in bulk makes use of the bulk mechanics offered by GCM and APNS. It is almost always preferable to send bulk notifications instead of single ones.

It’s also possible to pass badge parameter as a function which accepts token parameter in order to set different badge value per user. Assuming User model has a method get_badge returning badge count for a user:

devices.send_message(
        "Happy name day!",
        badge=lambda token: APNSDevice.objects.get(registration_id=token).user.get_badge()
)

Firebase

django-push-notifications supports Firebase Cloud Messaging v1.

When using FCM, django-push-notifications will automatically use the notification and data messages format to be conveniently handled by Firebase devices. You may want to check the payload to see if it matches your needs, and review your notification statuses in FCM Diagnostic console.

# Create a FCM device
fcm_device = GCMDevice.objects.create(registration_id="token", user=the_user)

# Send a notification message
fcm_device.send_message("This is a message")

# Send a notification message with additionnal payload
fcm_device.send_message("This is a enriched message", extra={"title": "Notification title", "icon": "icon_ressource"})

# Send a notification message with additionnal payload (alternative syntax)
fcm_device.send_message("This is a enriched message", title="Notification title", badge=6)

# Send a notification message with extra data
fcm_device.send_message("This is a message with data", extra={"other": "content", "misc": "data"})

# Send a notification message with options
fcm_device.send_message("This is a message", time_to_live=3600)

# Send a data message only
fcm_device.send_message(None, extra={"other": "content", "misc": "data"})

Behind the scenes, a Firebase Message will be created. You can also create this yourself and pass it to the send_message method instead.

Sending FCM/GCM messages to topic members

FCM/GCM topic messaging allows your app server to send a message to multiple devices that have opted in to a particular topic. Based on the publish/subscribe model, topic messaging supports unlimited subscriptions per app. Developers can choose any topic name that matches the regular expression, “/topics/[a-zA-Z0-9-_.~%]+”. Note: gcm_send_bulk_message must be used when sending messages to topic subscribers, and setting the first param to any value other than None will result in a 400 Http error.

from push_notifications.gcm import send_message, dict_to_fcm_message

# Create message object from dictonary. You can also directly create a messaging.Message object.
message = dict_to_fcm_message({"body": "Hello members of my_topic!"})
# First param is "None" because no Registration_id is needed, the message will be sent to all devices subscribed to the topic.
send_message(None, message, to="/topics/my_topic")

Reference: FCM Documentation

Exceptions

• NotificationError(Exception): Base exception for all notification-related errors.

• apns.APNSError(NotificationError): Something went wrong upon sending APNS notifications.

• apns.APNSDataOverflow(APNSError): The APNS payload exceeds its maximum size and cannot be sent.

Django REST Framework (DRF) support

ViewSets are available for both APNS and GCM devices in two permission flavors:

• APNSDeviceViewSet and GCMDeviceViewSet

  • Permissions as specified in settings (AllowAny by default, which is not recommended)

  • A device may be registered without associating it with a user

• APNSDeviceAuthorizedViewSet and GCMDeviceAuthorizedViewSet

  • Permissions are IsAuthenticated and custom permission IsOwner, which will only allow the request.user to get and update devices that belong to that user

  • Requires a user to be authenticated, so all devices will be associated with a user

When creating an APNSDevice, the registration_id is validated to be a 64-character or 200-character hexadecimal string. Since 2016, device tokens are to be increased from 32 bytes to 100 bytes.

Routes can be added one of two ways:

• Routers (include all views)

from push_notifications.api.rest_framework import APNSDeviceAuthorizedViewSet, GCMDeviceAuthorizedViewSet
from rest_framework.routers import DefaultRouter

router = DefaultRouter()
router.register(r'device/apns', APNSDeviceAuthorizedViewSet)
router.register(r'device/gcm', GCMDeviceAuthorizedViewSet)

urlpatterns = patterns('',
        # URLs will show up at <api_root>/device/apns
        url(r'^', include(router.urls)),
        # ...
)

• Using as_view (specify which views to include)

from push_notifications.api.rest_framework import APNSDeviceAuthorizedViewSet

urlpatterns = patterns('',
        # Only allow creation of devices by authenticated users
        url(r'^device/apns/?$', APNSDeviceAuthorizedViewSet.as_view({'post': 'create'}), name='create_apns_device'),
        # ...
)

Update of device with duplicate registration ID

The DRF viewset enforce the uniqueness of the registration ID. In same use case it may cause issue: If an already registered mobile change its user and it will fail to register because the registration ID already exist.

When option UPDATE_ON_DUPLICATE_REG_ID is set to True, then any creation of device with an already existing registration ID will be transformed into an update.

The UPDATE_ON_DUPLICATE_REG_ID only works with DRF.