Question about supported alert format in live activity push start notifications.

[rsaccone]

I have a question about the alert portion of the push start live activity notification. In the example below from Apple's docs it shows that for a push start live activity that the alert object can contain a title and body sub-objects which for localization purposes contains keys to localized strings and the parameters for formatting. From looking at the pushy code base it isn't clear to me that Pushy supports building this format of the alert. It is different from the alert schema used in visible and background pushes. Does pushy support this variation of alert?

Here's a link to the Apple docs on the push start payload for reference https://developer.apple.com/documentation/activitykit/starting-and-updating-live-activities-with-activitykit-push-notifications#Construct-the-payload-that-starts-a-Live-Activity

{
    "aps": {
        "timestamp": 1234,
        "event": "start",
        "content-state": {
            "currentHealthLevel": 100,
            "eventDescription": "Adventure has begun!"
        },
        "attributes-type": "AdventureAttributes",
        "attributes": {
            "hero": {
                "name": "Power Panda",
                "avatar": "U+1F43C",
                "healthLevel": 100,
                "heroType": "Forest Dweller",
                "healthRecoveryRatePerHour": 0.25,
                "url": "game:///panda",
                "battleCode": "game:///panda/battle",
                "level": 3,
                "exp": 600,
                "bio": "Power Panda loves eating bamboo shoots and leaves."
            }
        },
        "alert": {
            "title": {
                "loc-key": "%@ is on an adventure!",
                "loc-args": [
                    "Power Panda"
                ]
            },
            "body": {
                "loc-key": "%@ found a sword!",
                "loc-args": [
                    "Power Panda"
                ]
            },
            "sound": "chime.aiff"
        }
    }
}

[jchambers]

It looks like this is a new format and we'll need to add support. I've opened #1112 for this.

Until we add support, please note that payloads are just JSON strings, and you are absolutely not obligated to use Pushy's provided payload builders to generate them.

Separately, I have a growing temptation to remove the payload builders from the project entirely. With the vast array of JSON libraries out there, I'm not really convinced that maintaining payload builders inside Pushy is providing a lot of value to the community (or at least not value in proportion to the hassle). Still, that's a thing for the future.

[rsaccone]

Thanks for the timely response. Very helpful.