Fix for Chrome Browser CORS error - stale cache

I recently had been struggling with a CORS issue on my staging app. It worked fine previously but all of a sudden my calls to vercel started returning a CORS error. I knew the error was not from the server because the right CORS headers were set, and also the app worked well in incognito mode.

I tried clearing application cache and site settings data but neither worked.

Then, I opened the Devtools/console, went to the network tab, and selected disable cache.

This surprisingly resolved an error I had been struggling with for days! I hope this helps someone.