This should log the response, right? Well it doesn't. I see the connection in the network tab, it's alive and healthy. Any ideas?
function callback(response){
return console.log(response)
}
const unscribe = appwrite.client.subscribe('dashboard', callback);
beforeNavigate(to => {
unscribe()
})```
Images confirming that everything is set as it should be? and we indeed are connected
is dashboard the name of your collection?
Would it not be
appwrite.client.subscribe('databases.*.collections.dashboard', callback);
yes, i'm so sorry, i just figired that out while you were writing ))
added for test individual document, everything works just fine, god damn me old fool, always blind to obvious things
thank you @Kenny
Glad you figured it out! :)
[SOLVED] Realtime Subscriptions - callback doesnt log?
Recommended threads
- custom domain with CloudFlare
Hi all, it seems that CloudFlare has blocked cross-domain CNAME link which made my app hostname which is in CloudFlare, unable to create a CNAME pointing to clo...
- Custom emails
What happen if I use a third party email provider to customize my emails and my plan run out of emails/month? Appwrite emails are used as fallback sending emai...
- Realtime with multiple connections
I need the Realtime on multiple Collections for diffrent applicational logic. So my question is: Is there a way to have only 1 Websocket connection or do I need...