Notification Bell for Experience Cloud (LWR)

i have the exact same issue ! @Hieu, @George @Amit do we have a fix for this issue yet?

hi Kandil Mossad i want to use this notification in my lwr site and i want to display some coupon codes through it , so could you help me how can i make it possible by this notification feature

hi Kandil Mossad i want to use this notification in my lwr site and i want to display some coupon codes through it , so could you help me how can i make it possible by this notification feature

@Amit, thanks your code changes fixed the problem for my org (deployed the branch from your PR) @George, sorry I didn't noticed DM from you, but it looks like the root cause is addressed. Thanks Guys very much for your help, appreciate it! Waiting for the official release of the Notification Bell package with the fix.

Hi George, Yes It was something else other than permission it was in the code I have added the comments on Github please review those. thank you

@Amit "Allow guest users to access public APIs" is not needed, this setting refers to "guest users" meaning the unauthenticated part of the site. Notifications functionality does not apply to unauthenticated users. So this permission is not needed, whatever worked for you must've been something else you did, not enabling this permission. @Sebastian I sent you a DM on the trailblazer community to request that you setup a user for me in your sandbox so that I can help troubleshoot, but have not heard from you there. Can you please check and let me know if that's something we can do?

Hi Sebastian, I found the issue fixed in mine i will create a pull to merge in there code if you are using source code you can apply this fix

Hi Amit! Added the setting to my site ("Allow guest users to access public APIs") but it didn't help. Still the same error: "returnValue" : { "error": "System.TypeException: Invalid conversion from runtime type List<ANY> to Map<String,ANY>" } Request payload looks like this: { "namespace": "notifbell", "classname": "@udd/01p5t000009qVL4/NS", "method": "getNotifications", "isContinuation": false, "params": { "numDays": 30, "maxNumNotifications": 50, "notificationType": "0ML1i000000000fGAA" }, "cacheable": false } The same user (with a Customer Community Plus license) receives proper responses via standard ConnectAPI fired from LWC component. The status call: '/services/data/v60.0/connect/notifications/status': returns: { "lastActivity": "2024-03-01T10:12:39.728Z", "oldestUnread": "2024-02-19T16:42:37.066Z", "oldestUnseen": "2024-02-19T16:42:37.066Z", "unreadCount": 5, "unseenCount": 5 } '/services/data/v60.0/connect/notifications/' returns an array with 5 notification elements. If you need any further information about the sandbox and site configuration please let me know because the problem still exists. Regards, Sebastian

Go to site Administration -> Preferences - Allow guest users to access public APIs this will fix your error

To sup up: 1. Experience Site built on LWR template 2. Site domain added to the Remote Site Settings 3. Community user has Customer Community Plus license 4. Custom Notification Type is created and generated successfully 5. Your Component is added to the site (Domain's Site selected, proper Custom Notification type checked 6. Site is published successfully 7. Your components returns an error (see the main comment details) 8. Custom piece of code that calls for the standard API [GET] connect/notifications/ returns an array of notification objects.

Yes, I've done this step.

Hi Sebastian, have you added the site's domain to the org's Remote Site settings?