Sending a Notification with the notification object as null does not send a Notification to the device

[wynston-champion-actabl]

When sending a notification (via a server) and setting the notification object to null, the notification is not sent to the device, though, I do get a 200 response (confirmed when tested in Postman). The reason why I am wanting to set this object to null is to keep the server code to be cross compatible between my Xamarin Forms and MAUI app.

For Xamarin Forms, I am using a different library (Plugin.FirebasePushNotification), but I am able to set the notification object to null and the notification sends to the device. I'd like to not have to manage two ways of sending notifications for Xamarin Forms and MAUI and allow the code to be cross compatible.

Would it at all be possible to allow the notification object to be null?

Here is the payload for MAUI that sends a successful notification:

{
    "message":{
      "token":"_some_token_",
      "notification":{
        "body":"This is an FCM notification message!",
        "title":"FCM Message"
      },
      "data": {
        "actualData": "_some_serialized_data_"
        },
        "apns": {
            "fcmOptions": null,
            "headers": {
                "apns-priority": "5"
            },
            "payload": {
                "aps": {
                    "content-available": 1
                }
            }
        }
    }
}

Here is the payload for MAUI that is unsuccessful:

{
    "message":{
      "token":"_some_token_",
      "notification":null,
      "data": {
        "actualData": "_some_serialized_data_"
        },
        "apns": {
            "fcmOptions": null,
            "headers": {
                "apns-priority": "5"
            },
            "payload": {
                "aps": {
                    "content-available": 1
                }
            }
        }
    }
}

Notice that the notification object, when set to null, does not work.