I’m using Xcode 12.4 and ran into this same issue. My document is a ReferenceFileDocument (don't know if that influences this bug). My app initially presented an editor screen via a sheet. Closing the sheet and then backing out to the document browser would trigger an immediate save. Then I switched the editor view to be displayed via a NavigationLink. Then, as you report, the save would only be triggered after 15 seconds. I have decided to switch back to using a sheet to present my editor. Regarding the 15 seconds, that’s the normal delay that triggers a save after making an edit. Normally that’s OK while you are still editing a document. But yeah, the minute you close the document, it should trigger a save.

You need access to the internal UndoManager that TextEditor uses. Then you can use it to configure your undo button and to call undo()/redo() on, BUT I don't know of a way to get to that UndoManger. You can however, create your own UIViewRepresentable that wraps a UITextView and then get access to the internal undo manager that UITextView uses. Here’s how I did that: Declare a binding in your UITextView:UIViewRepresentable to an UndoManager. Your UIViewRepresentable will set that binding to the UndoManager provided by the UITextView. Then your parent View has access to the internal UndoManager. struct MyTextView: UIViewRepresentable { /// The underlying UITextView. This is a binding so that a parent view can access it. You do not assign this value. It is created automatically. @Binding var undoManager: UndoManager? func makeUIView(context: Context) -> UITextView { let uiTextView = UITextView() // Expose the UndoManager to the caller. This is performed asynchronously to avoid modifying the view at an inappropriate time. DispatchQueue.main.async { undoManager = uiTextView.undoManager } return uiTextView } func updateUIView(_ uiView: UITextView, context: Context) { } } struct ContentView: View { /// The underlying UndoManager. Even though it looks like we are creating one here, ultimately, MyTextView will set it to its internal UndoManager. @State private var undoManager: UndoManager? = UndoManager() var body: some View { NavigationView { MyTextView(undoManager: $undoManager) .toolbar { ToolbarItem { Button { undoManager?.undo() } label: { Image(systemName: "arrow.uturn.left.circle") } } } } } }

I've submitted a bug report about this as well.

In iOS 16, you can use the presentationDetents modifier. ScreenView() .presentationDetents([.medium]) There are variations other than medium. See the documentation.

Using Xcode 14 beta 5, I have the same error when using UIDocumentBrowserController in the iOS 16 simulator. I don't have a device with iOS 16, so I'm not sure if it's just a simulator issue. I only get this error with certain simulators, like iPhone. None of my iPad simulators have this issue.

Have you seen this: https://stackoverflow.com/questions/75513158/how-do-you-add-an-image-attachment-to-an-attributedstring. I've also been able to create an AttributedString that includes graphic attachments by loading an RTFD file into NSAttributedString and then initialize an AttributedString from the NSAttributedString. The AttributedString contains the graphic attachment as demonstrated by printing the object to the console. But when placed in a TextEditor, the graphics are not displayed. If I do a similar thing with UITextView, it displays the graphics.

This crashes in the simulator with: [MTLDebugRenderCommandEncoder setRenderPipelineState:]:1627: failed assertion `Set Render Pipeline State Validation renderPipelineState must not be nil. To be fair, any sample code I've found that tries to run PaperMarkupViewController on the simulator crashes. Is it possible to test PaperKit on the simulator?