Unset integer fields returning 0 from app state variables

[MartinLockheart]

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

Unset integer fields in app state variables are returning 0. I was under the impression that unset variables return null unless set, and if this has changed I didn't see any information about it. This is a breaking issue for my apps currently.

Expected Behavior

Empty integers in app state should be null.

Steps to Reproduce

1. Create a new page
2. Add an integer app state variable
3. Select a text variable and set it to the app state variable value.

Reproducible from Blank

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

Bug Report Code (Required)

IT4gis/l8YxPxMtF7rn6Y+9WoGUXHDp/R4c0sNobbxAjIoDoPJkUaePCVxNoZNO5T1ZbKEWJ+U00+anthYTfCsApIRerbYh4z855EzmVYEC/aoSpDsyoS3FTL+FWfmKD0cCFnB1TCPV2V10j72a2fu+XSj/qNrn4Zwh9f6PHaOI=

Visual documentation

Environment

- FlutterFlow version: 6.5.31
- Platform: Windows
- Browser name and version: N/A
- Operating system and version affected: Windows 11

Additional Information

This is breaking all of my null checks for integers (which are very important for some apps).

[Juansarmi]

Hello! FlutterFlow automatically assigns this value by default, since leaving it empty would cause an error when running the test.

As a visual improvement, you could add a conditional check to prevent the number from being displayed when its value is zero.

Best regards.

[MartinLockheart]

I'm sorry, so I should expect all integers in app state to be equal to 0 even when unset?

[MartinLockheart]

As shown in my example, I wanted to conditionally display the text if that value was set and not empty. It is unset and empty. Therefore, it should not display.

Page state integers are able to be nullable. Is this just an app state limitation?

[MartinLockheart]

I can work around it as needed, but I have never seen anywhere that suggested that an unset integer (in app state specifically) would count as "set and equal to zero". If that is intended functionality, that really needs to be made clear somewhere.