{"id":48780,"date":"2025-08-05T14:29:30","date_gmt":"2025-08-05T18:29:30","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=48780"},"modified":"2025-12-11T13:36:00","modified_gmt":"2025-12-11T18:36:00","slug":"swiftui-documentgroups-are-terribly-limited","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2025\/08\/05\/swiftui-documentgroups-are-terribly-limited\/","title":{"rendered":"SwiftUI DocumentGroups Are Terribly Limited"},"content":{"rendered":"

Christian Tietze<\/a>:<\/p>\n

This is how little you need to get started[…]<\/p>

[…]<\/p>

What the system does is provide a launch scene for you when you only declare a DocumentGroup<\/code> in your SwiftUI.App.body<\/code>. You can customize this by making the launch scene yourself. WWDC24 “Evolve Your Document Launch Experience”<\/a> contains examples that at least offer to style what’s above the document picker.<\/p>

[…]<\/p>

So I believe they settled for: throw, and we ignore it; but throw immediately on button press, which means throw twice real quick, then you get an alert, because something’s broken.<\/p>

[…]<\/p>

Scene<\/code>s cannot contain conditionals, the SceneBuilder<\/a> does not support this. That means there’s no way to have an app offer different scenes depending on whether or not in-app purchases have been made.<\/p><\/blockquote>\n\n

Alexandre Colucci<\/a>:<\/p>\n

\n

It baffles my mind that SwiftUI DocumentGroup still lacks the ability to programmatically create or open documents in response to external triggers like Quick Actions, Quick Look, Widgets, or the Files app.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n