To comply with the Digital Services Act, which takes full effect on February 17, 2024, Developers must integrate with the new Notifications APIs. docs.unity.com/ugs/en-us/manu... unity.com/legal/digital-servi...
Пікірлер: 8
@lemetamax4 ай бұрын
Okay, now this makes sense. I've been pushing back this video, but I'm glad to finally get a chance to watch it. Well explained and didn't have me going crazy about whether or not to delay launching the game
@n_mckean4 ай бұрын
Is there any functional limitation around this? For example, I think it best to save lastReadDate in CloudSave. I assume there is nothing stopping us querying CloudSave etc before returning the notifications to the user?
@MemphisGameDevs4 ай бұрын
As far as I can tell, it's not device specific. So you don't have to display the same notifications across PC and mobile. But I'm not a lawyer or even in the EU.
@n_mckean3 ай бұрын
Hi again. Other than the example that notes the properties of notification (e.g. notification.CaseId, etc) is anyone aware if there is a unique identifier for the notification? If we have multiple, how do we ensure we are noting which particular ones are 'consumed by the user?
@MemphisGameDevs3 ай бұрын
Looks like notifications all have a case id and a project id. They also have a created at date which is how you can tell the last one that got read
@n_mckean3 ай бұрын
@@MemphisGameDevs I just can’t find documentation to suggest whether created at it unique, I guess it should be. They need to publish example content.
@n_mckean3 ай бұрын
Sorry for all the comments, but can you explain line 89? Also, is there an issue in the GetLastNotificationReadData? The first time this code runs, there is no stored date. Won't that return an empty string that can't then be Parsed to a long as it would be the wrong format?
@Evil0taku3 ай бұрын
No problem. That line doesn't actually do anything. It should have been removed. "GetLastNotificationReadDate()" makes it redundant anyways.