Crash Opening Custom Component from Slidable List

[Javicg10]

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

When opening a custom component from a button inside a Slidable List, if we click on a container, the app crashes with a red screen error (Unexpected null value). This issue occurs consistently across different areas of the app whenever a custom component is triggered from within a Slidable ListTile Button.

The error trace suggests an issue with Navigator, possibly due to an invalid context when opening the component.

Expected Behavior

Opening a custom component from a button inside a Slidable List and clicking on a Container on it should not crash the app. The custom component should display normally without causing a Navigator error.

Steps to Reproduce

1. Create a new page in FlutterFlow.
2. Add a Slidable ListTile to the page.
3. Inside the list, add a button in the Slidable Action.
4. Create a custom component, and add a blank container on it
5. Configure the button to open that custom component
6. Run the app and slide an item to reveal the action buttons.
7. Click the action button that opens the custom component.
8. Click on the container.
9. Observe that the app crashes with a red screen error.

Reproducible from Blank

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

Bug Report Code (Required)

IT4OiMjc35N1m8tK+KrubO9VhiMsJj8la6xMkep+VUgbGIPNFogIfMzBVEpVZ/2+f2xAeWKZ8X4GpvTUhobxUvsVFwytGZg71apiWh/PRkKVWrK7BbioWX8nTOlhIH3G0cCvswlBJuteTHs37DiAeditSgDaNoTYIWwjRc+KVaDOnnCdGSPJNS9E2SsJGku1EfljIVDq+f6QspZl1eTjzw==

Visual documentation

Environment

- FlutterFlow version:  v5.2.0
- Platform: Web
- Browser name and version: Chrome 131.0.6778.86 (arm64)
- Operating system and version affected: macOS

Additional Information

I am 90% sure this didnt happen before, so probably is a recent bug from the Flutter Version update. (?)

[Alezanello]

Hello!

Thank you for sharing the issue. I attempted to replicate it by creating a page with a slidable action that opens a bottom sheet. Inside the bottom sheet, I added a container with an action to dismiss the sheet when clicked. Everything worked as expected on my end.

To help troubleshoot further, I can share the project as a public clone so you can test it yourself and make adjustments to see if you can reproduce the issue. Let me know if that works for you!

Project: https://app.flutterflow.io/project/qa-3700-62ud2h