FlutterFlow / flutterflow-issues

A community issue tracker for FlutterFlow.
98 stars 17 forks source link

Action block always throws back if changing something in the callbacks #2828

Closed artemBobrov closed 2 weeks ago

artemBobrov commented 3 weeks ago

Has your issue been reported?

Current Behavior

If i have the callbacks in the action blocks and try to change any behavior inside the action block, i aq always thrown back to the initial parent action in the action flow editor.

Expected Behavior

I should just be able to change the action without throwing back

Steps to Reproduce

  1. Create any component with some action with a component parametr
  2. From any page call this component as a bottom sheet for example
  3. Open action flow editor
  4. Click the Set action for a callback action
  5. Try to do anything - like adding action inside the action flow editor
  6. You would be thrown to the parent screen of the action flow editor immediately

Reproducible from Blank

Bug Report Code (Required)

IT4kjPHlz5JPj7xY17X5bfpsvGI4JjJ8TLJMqNYbGA0hNZOvEIkUPcj4dhRLYte/YG1mGWaL+XE1w+D6ueDpKPkrBwWYfpQ7za5XQRWUTnynMJSIO86oSmpQJ95VGEePyMO3rCQnPsBfWXgTwUOUe/CdG3qCf9qOYwx5e6fDbOY=

Context

I am trying to work with the callback actions.

Visual documentation

Here is the video recorded [https://share.vidyard.com/watch/9JbJiFicjF7oYkA851Lro3? ]

Additional Info

No response

Environment

- FlutterFlow version: 3.19.1
- Platform: MacOS
- Browser name and version: Using Desktop App
- Operating system and version affected: MacOS Sonoma 14.4.1 (23E224)

General

Relative to the time the changes were made, data was lost within

When following my steps to reproduce, data loss happens

Perlo34 commented 2 weeks ago

i confirm, using windows desktop app, every click i made on action pannel , like edit page state , click on a value , the action block was unselected

cwangfr commented 2 weeks ago

Same here, on Windows Desktop has problem, on the web is ok

paulperez-dev commented 2 weeks ago

Hi @artemBobrov, thanks for reporting the issue! We are keeping track of this issue on https://github.com/FlutterFlow/flutterflow-issues/issues/2813.

I'm going to close this issue.