
now no one replies

Please wait

You should definitely get some more patience, if you don't, no one will be able to help you.

<:appwritepeepo:1156975874852270110> huh

Am currently working on it

Seems like connection is bleing blocked. I would try disabling ssr

if am building a web app obviously i would use SEO

Honestly, I recommend using Rest API if you use NextJS. The SDK support is mainly only Client-sided, so for me the SDK was also completely useless. 😄

Not precisely. Discord is a web app and doesn't needs SEO in user-generated content

A normal website would want SEO, if you like it or not, it's something a user wants. My personal opinion is that the SDK is obviously not made for frameworks like NextJS

NextJS has too many references towards Server-Side, unless you make literally every page use the client, it's not recommended to use the SDK

Yes, but not for user generated content. It's being improved to have better support for SSR

It might be improved, but as said, as the current state I recommend just using the RestAPI

am just thinking that

it can do everything anyway, it might just need a little bit more code that the sdk normally does for you, but it's less time consuming in the long run.

how to off it

but how to use the REST

Hey 👋 If you provide me with your project ID, I can check if there are any server errros on our end.
Other than that, I would recommend trying it client-side, just to see if that solves the problem. Also comparing development and production might reveal some information. I know basics about Next.js, but I think they do some changes to fetch
- that possible doesnt play well with Appwrite. Do you know how that could be checked with Next.js? If that's the case, it would be great if you reproduced it in a simple demo app, so we can easily investigate it and write a fix in our SDKs.

projectId: moneytube


I dont see any internal errors regarding document creation from your project, so the socket timeout is likely happening from the client-side.
Next.js is very robust framework, and this could be due to configuration, setup, build or compatiblity with SDK. Since I am not expert with Next.js, I cant give exact answers. Trying to turn features on/off is a great step towards figuring out what exactly it's that Next doesnt like about Appwrite. I have seen projects built with Next.js both using server-side rendering and client-side rendering, so I am sure there is some solution.
I would recommend trying what D5 suggested, and seeing if not using SSR makes it work properly.

ohky thnkx for your time

Heyo. Check the references in the docs and change web to rest

You can find specific info in the Docs -> Rest API about certain endpoints

I recommend reading through the docs and get a better understanding of how to properly use the Appwrite REST. If you don't know how make fetch requests, please read the nextjs docs: https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating https://nextjs.org/docs/app/building-your-application/routing/route-handlers
Recommended threads
- my database attribute stuck in processin...
when i created attributes in collection 3 of those attributes become "processing", and they are not updating, the worst thing is that i cant even delete them s...
- Forever Processing Issue
I encountered an issue when creating attributes in the collections . if you create an attribute of type string for example and choose a size of 200 or 250 or a...
- Realtime Disconnects and Error: INVALID_...
Hi! I just want to ask here if there's any workaround with the disconnect issues we're encountering when subscribing to realtime events in react native using ex...
