API Editor easily break, reload/restart require to back normal.

[Zhihong0321]

Has your issue been reported?

• I have searched the existing issues and confirm it has not been reported.
• 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

1. Every time you try to edit Header parameter.
2. if you try to save a invalid format parameter, system prompt error.
3. The Entire API Editor break from now.
4. Now, even you edit the correct parameter, SYSTEM REFUSE TO ACCEPT ANYMORE.

Another scenerio :

1. create a new api call, but name put blank
2. try to save it, system prompt error, must give it a name
3. Enter a Name on the name field
4. viola. ENTER API Editor now break. It refuse to accept any input on that field. Even you RE-CREATE from ground zero, the editor still angry about why you forget the name field just now. It refuse to work.

SOLUTION :
RELOAD the page.
RESTART THE DESKTOP APP.

tested on chrome on macos, chrome on windows 11, 10 pc, laptop.

Expected Behavior

Sometime i forget, couldnt you guys just forgive me?
i cant save the entire new API Call, and have to redo from ground zero ( because i have to reload the entire page )

Steps to Reproduce

1. in api editor, header field, api name field,
2. try to enter invalid input
3. click save
4. system prompt error
5. viola. Now system refuse to work anymore.

Reproducible from Blank

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

Bug Report Code (Required)

none

Context

i dealing with alot api call.

Visual documentation

none, no need

Additional Info

No response

Environment

- FlutterFlow version:
- Platform:
- Browser name and version:
- Operating system and version affected:
 
chrome :
on macos, windowns 10, 11
on M2 Air, Ryzen 4500u laptop, Intel i7-10700K PC.

[rogeraleite]

I am having the same issues, thank you @Zhihong0321 for reporting that.

[paulperez-dev]

Hi @Zhihong0321, I was able to reproduce the issue, I will send it to the ENG team so they can work on this.

Thanks for your feedback!