onMount(async () => {
let transactions = await database.listDocuments(
env.PUBLIC_VAULT_DB_ID,
env.PUBLIC_TRANSACTIONS_COLLECTION_ID
);
console.log(transactions);
client.subscribe(
`databases.${env.PUBLIC_VAULT_DB_ID}.collections.${env.PUBLIC_TRANSACTIONS_COLLECTION_ID}.documents`,
(response) => {
console.log(response);
}
);
});```
I am trying to get this realtime to get to work and it seems to connect to the websocket but it just doesnt respond with anything
(for in context the list documents works fine)
Is the users has permission for the documents and the sub documents?
it does seem like realtime gets disconnected
Have you create/update/delete new documents in that collection?
Mmm This is your <:kubernetes:781202441546629180> instance?
Nah I just went with a dedicated node
it was just too fittely to get that working great
Yes, agreed
I update one of the documents their number
Update this payment amount
Does this look normal to you? shouldnt it respond back like there is a connection or doesnt appwrite do that?
No, that's okay
Just wanted to verifiy that
It seems like if you're changing something in the console it **__won't__** fire realtime events
Connect to the <:realtime:1108648060894068776> realtime and update the document using any SDK or REST api
oh okey let me try that
If it's true that the real time won't trigger changes done in the console maybe it's worth to mention it in the docs
Ah that worked ^^
Great
So it's indeed the way it works
[SOLVED] Realtime no response
Thanks! Thought the console would act the same but it doesn't really matter in my case
<a:agooglethumbsup:635256484682530825>
Recommended threads
- Finding job
Hi. I am a full-stack developer with experience in developing scalable and user-friendly web applications. I handle both front-end and back-end development, im...
- CDN not delivering correct bundle
My site 69b4cd410035893573dc is not delivering the latest deployed version via CDN, it seems stuck on versions from previoiu days, alternative links for the lat...
- Site ID: 6a22303d000c95ef93bdDomain: van...
multiple rapid deployments + a force push to master caused the router to lose the domain-to-deployment binding, even though the Domains tab shows the mapping is...