Error while testing in test mode and running in locally

[mubarismubi]

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

should not crash homePage , i have 2 filter for a backend query . if one of the filter value is null or empty it crashed

Expected Behavior

should not crash if the filter value is null or empty . i have toggled ignore empty filter value

Steps to Reproduce

run project in test mode or locally

Reproducible from Blank

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

Bug Report Code (Required)

IT40p/j3uIZ6odsC5qrAbu1plgcWOUAabJJMsu17aCgofePtOol3evXsVxdoZ+3gTAl2IESmmn4DwPT2iNnxNe4nAwibGIRmyJN+cQ7yXTqiUZOBCJOBPXJ5EeBXN0ih56bQhiRQXcduWFog12C6NeSuY3XYO5j1ImdISq/LZO4=

Visual documentation

Environment

- FlutterFlow version: 
- Platform:
- Browser name and version:
- Operating system and version affected:

Additional Information

No response

[Juansarmi]

Hello!
I'm sorry to hear you're experiencing this issue. So far, I haven't been able to reproduce the error on my end.

To help us identify the problem, could you let me know which version of FlutterFlow you're using? Also, if you uncheck the "Ignore empty filter values" option, do you still encounter the same error?

Looking forward to your response.
Best regards!

[mubarismubi]

@Juansarmi 6.1.53+ , yes if i Ignore empty filter values" option , still have the issue . i hope u tried test mode not run mode . run mode it works fine

[Juansarmi]

Hello again!

I haven’t found any issues when using filters in general. However, after looking a bit deeper into your project, it seems the problem might be related to how your filters are set up.

Please make sure that the values you're using in your filters are not null. If possible, try assigning default values. For example, in some of your queries, you're using a value from the app state — currentListingRef — which might still be null at the time it’s used, since it depends on the result of another query triggered during the page’s onLoad actions.

You could try fixing this by checking whether your filter values are empty or null before using them, or by using conditional builders to delay the query until the necessary data is available.

Best regards!

[mubarismubi]

but there is a toggle to filter on null values and ignore empty filter , should not crash it right? . is there any other way to not crash ? the app state will be null for some condition it will not be null . but the error .
i have attached the properties . it should not crash

[Juansarmi]

Hello again!
Unfortunately, I haven’t been able to reproduce the error on my end. However, I’m sharing some information below regarding the optional settings you’ve selected, as I believe there may be some confusion around them
https://docs.flutterflow.io/resources/backend-query/query-collection/#defining-the-query

As for the issue in your project, I’d recommend reaching out to support either through the in-app chat or by emailing support@flutterflow.io — they’ll be in a better position to assist you with your specific case.

Best regards