You need to return the view. #Preview { var callBack: (Date) -> Void = { _ in } return ContentView(callBack: callBack) }

You might want to look through this page... https://support.apple.com/guide/iphone/view-or-change-cellular-data-settings-iph3dd5f213/ios

That functionality was disabled a long time ago due to privacy concerns. You can get an identifier that remains the same as long as one of your apps is installed, but if they are deleted and installed again, a new one is assigned... https://developer.apple.com/documentation/uikit/uidevice identifierForVendor

And then I realize I was looking at the code you had to reenable the timer. You might want to consider moving the code into the app delegate. I've used the disable timer successfully in a media program to prevent the app locking while playing videos since the user wouldn't be interacting with the phone.

Are you sure the setIdleTimerDisabled code is executing? It is my understanding that the call to UIApplicationMain() never returns.

It looks like Sonoma 14.1 is limited to iOS 15.2. I have an M2 mac mini and that was the oldest platform available to install. 15.0 was showing installed but failed to run.

I found a solution import PlaygroundSupport import SwiftUI struct SheetView: View { @Binding var content: String? init(_ content: Binding<String?>) { _content = content } var body: some View { Text(content!) } } struct ContentView: View { @State private var isPresented = false @State private var content: String? @State private var startTask = false var body: some View { Text("Tap me") .onTapGesture { startTask = true } .frame(width: 500.0, height: 500.0) .task(id: startTask) { guard startTask else { // startTask = false // <===== Crashes if removed content = "Some message" isPresented = true } .sheet(isPresented: $isPresented) { SheetView($content) } } } let view = ContentView() PlaygroundPage.current.setLiveView(view)

I think I know the problem. You are accessing the content property value as it is at that moment, but you access the isPresented property in what amounts to the will set call, so you are seeing the future presented value, but the present content. I'm not sure of a fix for it since it becomes immutable if you remove the state wrapper.

Silly question, do you have a text field in focus when you do that? It seems to require that to respond.

I was poking around with it in a playground and it feels like a race condition is happening. It was working for a bit with the line commented out with some print statements added to try to see what was happening. Body is evaluated three times as would be expected.

Never mind, I just realized you have a state value that should logically mean the content is present.

It is my understanding that .task executes asynchronously, so it most likely isn't done when sheet executes.

Your app needs to update the control state, enable/disable, based on its control state. I have this function that handles a change in the player state /// updates the media player controls to reflect the new player status /// - Parameter status: player status flags func updateUI(status: PlayerStatus) { ModuleData.singleton.mediaCommandCenter.playCommand.isEnabled = status.intersects(with: .play) ModuleData.singleton.mediaCommandCenter.stopCommand.isEnabled = status.intersects(with: .stop) ModuleData.singleton.mediaCommandCenter.pauseCommand.isEnabled = status.intersects(with: .pause) ModuleData.singleton.mediaCommandCenter.nextTrackCommand.isEnabled = status.intersects(with: .skipForward) ModuleData.singleton.mediaCommandCenter.togglePlayPauseCommand.isEnabled = status.intersects(with: [.stop, .play, .pause]) ModuleData.singleton.mediaCommandCenter.previousTrackCommand.isEnabled = status.intersects(with: .skipBackward) ModuleData.singleton.mediaCommandCenter.skipForwardCommand.isEnabled = status.intersects(with: .skipBackwardTime) ModuleData.singleton.mediaCommandCenter.skipBackwardCommand.isEnabled = status.intersects(with: .skipBackwardTime) ModuleData.singleton.mediaCommandCenter.seekForwardCommand.isEnabled = status.intersects(with: .seekForward) ModuleData.singleton.mediaCommandCenter.seekBackwardCommand.isEnabled = status.intersects(with: .seekBackward) } The status values are a bit mask enum with various controls enabled/disabled.

One additional horrible hack is to check the right bar button items list to see if it has more items than you expect, and if so, drop the first one. In my case I was expecting one, so I set it to be just the last item in the list. I have the advantage of not needing my app to go to the store, so I don't know if this combination of things would be allowed in store apps.

The best I managed with it being presented full screen is to set the right navigation item to be a close button and set the navigation controller toolbar as hidden in viewDidLoad. This leaves a blank toolbar, but that at least gets rid of the share button. Looking at the screen using xcode's view inspector, it looks like it might be creating a toolbar since I see two toolbars stacked on one another, a blank one and the one with the share button. I also set the toolbar to hidden in willLayoutSubviews That works on a compact screen, aka portrait on a phone, but in landscape the share button becomes a second button to the left of my close button. I just spotted the landscape issue and am still looking into it.