fullScreenCover & Sheet modifier lifecycles

Hello everyone,

I’m running into an issue where a partial sheet repeatedly presents and dismisses in a loop.

Setup

  • The main screen is presented using fullScreenCover
  • From that screen, a button triggers a standard partial-height sheet
  • The sheet is presented using .sheet(item:)

Expected Behavior

  • Tapping the button should present the sheet once and allow it to be dismissed normally.

Actual Behavior

  • After the sheet is triggered, it continuously presents and dismisses.

What I’ve Verified

  • The bound item is not being reassigned in either the parent or the presented view
  • There is no .task, .onAppear, or .onChange that sets the item again
  • The loop appears to happen without any explicit state updates

Additional Context

  • I encountered a very similar issue when iOS 26.0 was first released
    • At that time, moving the .sheet modifier to a higher parent level resolved the issue
  • The problem has now returned on iOS 26.4 beta
  • I’m currently unable to reproduce this in a minimal sample project, which makes it unclear whether:
    • this is a framework regression, or
    • I’m missing a new presentation requirement

Environment

  • iOS: 26.4 beta
  • Xcode: 26.4 beta

I’ve attached a screen recording of the behavior.

Has anyone else experienced this with a fullScreenCoversheet flow on iOS 26.4?

Any guidance or confirmation would be greatly appreciated.

Thank you!

Hello theorangajang,

Could you please place the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on.

If you're not familiar with preparing a test project, take a look at Creating a test project.

Let me know if you'd like to know more,

Richard Yeh  Developer Technical Support

Hi, did you find a solution to this problem? I am experiencing a similar issue in my app on 26.4.

I present a sheet from a fullScreenCover and the sheet just gets instantly dismissed. On 26.3 it works.

Regards,

Dear @theorangajang and @pontusnt,

This might be a known issue (FB22189610). Just to check, can you both please file bug reports on Feedback Assistant? The engineering team can then request the appropriate logs from you, and you'll be able to track progress on this. If you find something that helps you avoid the issue, please share it with the community by posting it here.

Even though we're aware of this issue, we still encourage you to open a bug report, and post the FB number here once you do. The specific info you include your bug report might help our investigation, and filing the bug report you to get notified when it is resolved.

Bug Reporting: How and Why? explains how you can open a bug report.

fullScreenCover & Sheet modifier lifecycles
 
 
Q