ADD: Payload category to support Actions#289
ADD: Payload category to support Actions#289marcosrdz wants to merge 20 commits intoBlueWallet:masterfrom
Conversation
Overtorment
left a comment
There was a problem hiding this comment.
first, what youre trying to achieve - you can just check tht payload has .txid field on the client.
second, youre hardcoding thevalue, and instead i think youshould have modified definitions of specific notfications in openapi.yaml, to add a constant field:
constantField:
type: "string"
const: "constantValue"
description: "This is a constant field with a single value"
and then re-generate ts files from that openapi spec.
but option 1 is easier
Option 1 is not possible. Client expects it from server. |
|
@Overtorment lmk if I need to change anythin |
|
Why option 1 is not ok? Payload from the server for those pish types will always have a txid field |
AppDelegate.mm requires the payload it receives from the server to contain the "category" property. if it doesnt exist or if its empty it will not display the buttons. |
|
is that a requirement by apple? or its up to us to change? cause frankly, modifying client is easier than server in this case |
Its a requirement. Client has to receive it on the payload. Otherwise a compromised app could intercept it |
wtf. post docs link pls |
For LOCAL notifications you can do do locally. Not for remote |
|
https://developer.apple.com/documentation/usernotifications/unnotificationcategory To apply category objects to your notifications, include the category’s identifier string in the payload of any notifications you create. For local notifications, put this string in the categoryIdentifier property of the UNMutableNotificationContent object that you use to specify the notification’s content. For remote notifications, use this string as the value of the category key in the aps dictionary of your payload. |
|
@Overtorment any updates? |
No description provided.