Page State Name Update Error

[gasserwshalaby]

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

when a page state is renamed, it does not reflect in any area it is used while used within an "update page state" action. even though its name is changed in FF builder, it is not reflected in the code generated.

Expected Behavior

when a page state is renamed, its name should be changed throughout every instance it is used in the page immediately, as well as changed in the generated code as well.

Steps To Reproduce

1. create a new page
2. create a page state which is a list of documents type.
3. add / remove any compatible type to the page state
4. rename the page state
5. the name is updated in FF UI builder in the actions section
6. run test mode, get the error for the old page state name not being updated, thus throwing an error of it being not found.

Bug Report Code

IT48ksrl34x2tbwA15DUbu9VgiMRJkM7U78njOpHZw88J5zKB+wAYvf7P1FWTLyiT1VhMU2KgmEx7Pfqjt/AFfk6HxKVGKJd+sx+ShbJTlKVV5CYBoe7fW1fEp9bf3KFy8CJnBJ5Pu5iSHAH2jqTNd+vHjDsQp/4OjE/LfmlLdeK2SrDX1iXc2URm05KZDPz

Context

i am trying to track a list of selected documents displayed in a list view with a check box and a text displaying the choice's name. when checked or unchecked, the action is to add or remove the selected/unselected document for the page state which is a list of documents of the same type.

Additional info

No response

Environment

- FlutterFlow version: v1.1.57
- Platform: Mac app
- Browser name and version: FF desktopapp for Mac, v1.1.57
- Operating system and version affected: OS Monterey 12.5

[hariprasadms]

Hi @gasserwshalaby - I can re-produce the issue. Renaming the page status is not changing the state variable names where ever it is used. However, I do not see test run is failing.

Dev info - Please check this in custom code as well.

[aemelyanovff]

@gasserwshalaby Thanks for reporting the issue. It'll be fixed in the next update.