Online test environment does not support API calls.

[felipeslo]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

When running any project in test mode, the registered API calls in the project do not execute.

Expected Behavior

When running any project in test mode, the registered API calls in the project do work.

Steps to Reproduce

Take any project, run it in test mode, and try to use an API call.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT48iMjfsI52rt9G+KrAb/owijosJjI7aL8zjcFTSQI8J5zKB+wAYvf7P1FWTLzkY3NcJ2CZrHMxxvfqk+P1D/oCBEyWG4B6wpNUcAzJTn67R4zUBqW3fW1REZ5jJ0inyJ+7kCRACNNtZVYgw3GIB+iRcBLYK7GwIVgjHsmlJdeK2SrDX1iXc2URm05KZDPz

Visual documentation

Environment

- FlutterFlow version: 6.0.12
- Platform: 3.27.3
- Browser name and version: Chrome 137.0.7151.69
- Operating system and version affected: Windows 10

Additional Information

No response

[Alezanello]

Hi there! 👋

Thanks for reaching out. I’m sorry, but I wasn’t able to reproduce the issue on my end. I set up a test API call on a button and ran it in test mode — everything worked as expected.

Feel free to clone and test the public project here: https://app.flutterflow.io/project/qa-4313-9ns225

[felipeslo]

Access to XMLHttpRequest at 'https://secure-ridge-22999-537c838d4a8a.herokuapp.com/https://cjmzlwcavxweckyjfokf.supabase.co/auth/v1/token?grant_type=password' from origin 'https://ff-debug-service-frontend-pro-ygxkweukma-uc.a.run.app' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Access to XMLHttpRequest at 'https://secure-ridge-22999-537c838d4a8a.herokuapp.com/https://cjmzlwcavxweckyjfokf.supabase.co/auth/v1/token?grant_type=password' from origin 'https://ff-debug-service-frontend-pro-ygxkweukma-uc.a.run.app' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

There is still an error in the cors.

[felipeslo]

It was noticed that the account projects after update 6.0.10 somehow habituated the use of proxy in calls. Disabling it, worked normally.

[fbabic-xa]

I am actually experiencing the identical issue. When I test the API calls from the API Calls Page, everything works properly. When I run the app in test or run mode, the API calls are not working. But if I publish to web, they work again. It's been like this since 6.0.09 or 6.0.10 version.

[AbnerCX]

I am experiencing the same issue.

When I run my project in test mode, the registered API calls in the project do not execute. I have checked the console and noticed CORS errors and 503 status codes, especially on requests like token/ and channel. However, when I duplicated the project and tested the copy, everything worked correctly and the API calls were executed without issues.

It’s important to mention that everything was working normally until a couple of days ago. I haven’t made any significant changes that could have caused this issue, so I believe it might be related to the platform itself.

[julioacosta]

@Alezanello The project you're using as an example uses a different Heroku proxy than the one we're referring to.

QA Test

My Project

Proxy QA: https://blooming-anchorage-74937-01abcbf2453c.herokuapp.com
Proxy my instance is using: https://secure-ridge-22999-537c838d4a8a.herokuapp.com

As you can see in terminal the curl to the first proxy is working properly while the second does not respond nothing

How can i config my project to use https://blooming-anchorage-74937-01abcbf2453c.herokuapp.com as proxy in test mode?

[kysemon]

Hi there! 👋

Thanks for reaching out. I’m sorry, but I wasn’t able to reproduce the issue on my end. I set up a test API call on a button and ran it in test mode — everything worked as expected.

Feel free to clone and test the public project here: https://app.flutterflow.io/project/qa-4313-9ns225

The API call works fine when triggered from a button, but it doesn’t work when triggered from a form that uses input values. For example, this issue occurs on a login page.

[syg-eliseu]

I'm experiencing the same problem. My requests to firebase cloud functions urls, which are wrapped by heroku, don't work.

The problem is with heroku.

Run mode:

Postman With Heroku:

Postman Without Heroku:

Whenever my request is involved with heroku I go through this problem. To avoid the error, I have to disable the use of proxy in the advanced request settings.

[fbabic-xa]

@syg-eliseu , your solution fixed it for me - I turned of the use of proxy in the advanced settings. Thank you!