Bottom sheet does not respect bottom safe area

[DanielGiraldoMontes]

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

I have created a bottom sheet and I want it to respect the bottom safe area of the devices (Android/iOS) but the issue is even if I provide the Safe Area option while opening the bottom sheet it does not respect the safe area of the device and the pixels overflow at the bottom.

But if you see the button is at the bottom and it respects the safe area

Expected Behavior

The bottom sheets should respect the safe area at the bottom on iOS devices as well as on Android devices.

Steps to Reproduce

1. Create a new page
2. Create a new component without any bottom padding (and add anything Text/Image)
3. Create a button on the page and create the action to show the bottom sheet (And toggle the safe area option)

Reproducible from Blank

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

Bug Report Code (Required)

IT4wz/Hqx89goflF1s7cavlVnj4vIjo4R+cRke5+Qis9f5CvOpYUec/6PlhVXs/nY3NieWacp14ywfzrv/H9DcA3ISiCQNlcypZcZBbwXk+hVr2TF7u0dEBDINJVFXah5revpiUkLvdvLXgs2Wb7e+/LfC7UJufoC1Q8Sq/LZO4=

Visual documentation

Environment

- FlutterFlow version: v5.3.7  released April 1, 2025
- Platform: MacOS
- Browser name and version: N/A
- Operating system and version affected: iOS

Additional Information

This issue can complicate the user experience while building mobile apps because all the devices don't have the same bottom safe area, then we may need to create different paddings dealing with poor UX experiences for some devices.

[Juansarmi]

Hi!
I’m sorry to hear that you’re facing this issue.

One possible solution would be to enable the SafeArea within your Card09OrderCard component and adjust the offset to better suit your specific needs. Please let me know if this resolves the problem. If not, I’d be happy to investigate further.

Best regards.

[DanielGiraldoMontes]

Hi @Juansarmi,

Thanks for your response, but I am just curious this is not a specific scenario, even if it is reproducible from a blank project and looks like there is no way to wrap a component within the SafeArea by itself, I mean, while showing the bottom sheet from the page, there is an option to wrap the sheet within the safe area, that is what I want to show you that is not happening for the bottom safe area maybe do you require further details? Could you access the project I have shared? Even that is a project created from scratch.

It is not expected that if I enable the SafeArea for my component as shown in the image, shouldn't the component content be wrapped within a SafeArea internally to respect it? :

Let me know if you can further check the issue or if I can provide more details

[Juansarmi]

Hello again!

I’m following up on your case. I’ve been able to identify the error and will be forwarding it to the engineering team for further investigation. I will keep you updated on any progress regarding the investigation.

In the meantime, I’ve found a workaround that I mentioned to you earlier. I’ve attached an image for reference.

Essentially, it involves enabling the safe area directly on the component you're using within the bottom sheet.

I hope this helps, and I truly appreciate your patience.

Best regards

[DanielGiraldoMontes]

Hi @Juansarmi,

Great, I will try to check it and let you know, looks like that is the expected configuration, maybe the safe area shouldn't be provided while showing the bottom sheet, it should be specified to the component itself !!! I didn't notice this option, let me test it and validate but sounds like this is the workaround.

And even that is expected because if we wrap entirely the bottom sheet within the safe area then the sheets will not go back down, I think I should play with the safe area just for the component and not entirely for the sheet (When we have bottom sheets for options or different scenarios where we want a background in it)

Thanks a lot for your support.

[Juansarmi]

Hi again!
I hope the workaround helped. I’ll keep you posted as we work towards a resolution.
Best regards.

[github-actions]

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.