Self hosted + react inbox component
Im using novu in production, however to make development easier I have added novu locally in docker-compose and is using the self-hosted version here.
However the inbox component is not working with self hosted novu, at least it seems?
Is this known about? Any ways i can get this to work?
8 Replies
Hi Larsen
With self-hosted version, you will need to add backendUrl and socketUrl with your own self host api service url and ws service url respectively
With self-hosted version, you will need to add backendUrl and socketUrl with your own self host api service url and ws service url respectively
I have done this,
I can even see network requests fetching the notifications,
however it shows no badge/pill that there are messages unread
and it shows no messages in the inbox
I do get some rendering error, due to a split on some apperenceKey, however have not been able to solve this.
My immidate hunch was that there was a difference in version for whats self hosted and what the inbox component can render?
@larsen
Since this is self hosted version and we don't have acces to self hosted version logs. Could you please share all error logs from console and network tabs if you seen anything?
Ive attached the screenshots ive whats going on, the requests are all going trough, however its not rendering any notifications..
Im also getting , unreadCount more thatn one, and this is not rendering a badge on the bell
```
"data": {
"applicationIdentifier": "W0N8QL28vbCA",
"token":"xxx",
"totalUnreadCount": 1,
"removeNovuBranding": false,
"maxSnoozeDurationHours": 0,
"isDevelopmentMode": true
}
}
Same issue here. Network requests seem to be working fine.
Works fine for me on @novu/react 3.8.1, when I upgrade to 3.9.3 it breaks.
Thanks, @Basilade
can confirm that pinning @novu/react 3.8.1 makes the notifications render at least, would be nice to solve this issue, tho
Thanks for the update. Will share the feedback with team.