I have disabled cors on chrome and my function is accessible on my frontend but not working unless i disable cors. I have added the domain to platform and not fixed. Any help on this will be appreciated.
TL;DR
Issue: CORS policy blocking access to function on frontend even after disabling CORS in Chrome and adding domain to platform.
Solution: The CORS policy can be circumvented by adding appropriate headers to the response in the backend code. Ensure that the backend server responds with the proper CORS headers to allow frontend access to the function.Recommended threads
- Go 1.25 runtime
So I'm trying to use go 1.25 for my functions and I can only find go-1.23 as a function runtime. So I did some searching and found https://github.com/appwrite/a...
- [ENHANCEMENT] Use the custom Next.js dep...
Deployment adapters on Next.js are now stable! This means that we don't have to stick to the limitations of sniffing out build outputs and manually moving or mo...
- NextJS builds sudden runtime_timeout
My builds suddenly stopped working. Activating old prebuilt snapshots work, but redeploying that same code produces builds that throw runtime_timeout FRA region