Sooner than later, you'll come across this issue when using APIs on flutterflow.
Cross-Origin Resource Sharing (CORS) issues occur when a web application running in one domain (origin) tries to make requests to a server hosted on a different domain. Browsers enforce CORS to prevent potential security risks that could arise from cross-origin requests.
Interestingly Flutterflow offers a proxy server to test APIs in test and run mode but not in production (ie: When we publish). This is why you won't notice this issue when testing. You'll think all is well and when you publish - BAM, your APIs won't work because of CORS.
That leads me to ask 2 questions.
1. Would Flutterflow consider offering native support (proxies etc) to solve CORS issues for paid users in production. For the developers, I assume this is a day's worth of work (unless I've misunderstood the complexity of the work) but can save users multiple hours. This specifically if users are not using Firebase as their backend. Users like me prefer supabase.
2. What are the options for newbees to solve this issue without too much coding? Preferably for us simpletons who love a relational database like Supabase which offers use of functions for free. ;)
John Higgins and Pooja Bhaumik your insights would be very helpful.
EDIT: Update
Here's how I solved this issue. I don't call any APIs directly from Flutterflow. I call them via an integration service like BuildShip or Make.com or n8n.
Eg:
Before:
Flutterflow → Twitter
After:
Flutterflow → Buildship → Twitter