swiftui

Which BackgroundTask type are you using? The SwiftUI BackgroundTask API actually works by aggregating the behavior of a number of unrelated APIs, only some of which are public or fully supported on watchOS. That makes it very difficult to talk about it in a generic way. *It doesn't help that we've used the term background task for two OTHER APIs (UIApplication.beginBackgroundTask() and the BackgroundTask framework), both of which are significantly older than the SwiftUI API. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

I was just about to give up and tell you to create a demo project that just opened one web view and printed it. But I thought I should try that first myself. I did and also got 2 blank pages. There are lots and lots of possible options. But in this demo app, here is how I fixed it using a Swift Storyboard document-based app: In Xcode Interface Builder, find the print menu item. Change its sent action from print: to printDocument: in NSResponder. Observe that the app now prints correctly. I tried this with your sample and got 12 pages, including the last. Nothing seems to be missing except horizontal overview inside a div in the web view, but that's a different problem. I poked around for a bit. It looks like the old XIB templates in Xcode used printDocument: as the sent action. For some reason, in the newer Storyboard templates this was changed to just print:, which doesn't seem to work. No clue about SwiftUI. I have a newer app in Swift that isn't document-based. In this app, I seem to have already

Welcome to the forum. getting past the demo login on my app. when I press enter demo or sign in Is it SwiftUI or UIKit app ? If UIKit, have you checked the buttons are properly connected to their IBAction ? If UIKit, please show the code of the buttons if SwiftUI please show the code of the view where they are defined. I can’t enter my app to see what’s wrong with it. What do you mean ? That you cannot test beyond this demo or sign in ? You give almost no information except declaring it does not work. How could someone help ? Please read this: https://developer.apple.com/forums/thread/706527 and complete your post accordingly.

Based on the docs this should be what I really want: https://developer.apple.com/documentation/swiftui/view/backgroundextensioneffect(isenabled:) It's supposed to disable the background, but it seems to not do anything at all. The code in the commented out region is still the only that works reliably. NavigationSplitView(sidebar: { sidebarView //.background { // Color.red // .edgesIgnoringSafeArea(.all) //} }, detail: { detailView .backgroundExtensionEffect(isEnabled: false) })

I actually moved back to the older handle () function on the app delegate as the .backgroundTask (swiftui) modifier didn't seem to be called at all. That said I'm dealing with a lack of combine pipeline in background tasks.

You're not the first to ask such question. Answer here may help you: https://developer.apple.com/forums/thread/797977?answerId=855247022#855247022 With all the things you want to learn, that may take you more than 6 months full time to learn and master. So you should focus first on learning basics, like using Xcode (of course), Swift language and the basics of SwiftUI and UIKit. Good material in https://developer.apple.com/pathways/.

I can tell you how I got into iOS development and try to answer some of your questions. I started by trying to find tutorials online, but the ones I found were either too simple or did not explain anything properly. I even bought a course at Udemy but that course also did not go into the details as much as I had hoped. I finally stumbled upon the iOS course at Stanford: https://cs193p.stanford.edu Back then it was available at iTunes U (which does not exist anymore), and included the lecture videos and the course work. I watched all the videos and, crucially, did all the course work. Doing the exercises was really essential because when you listen to the lectures it all sounds easy but when you try to do it yourself it's not so easy 😄 That course was exactly what I needed: it did not require any prior knowledge except for general programming, went into the details but explained everything. Definitely can recommend it if the videos are still made available, you will have to check. To your questions: Should I

Well Apple has pretty much dropped Objective-C and moved fully to Swift and SwiftUI becuase its faster and better to use. Worth learning it though. Interesting claims. When you say faster are you talking about performance or the speed in which you scratch your code? While it's obvious Apple is recommending Swift all the new AppKit API I'm aware of (or at least care about) for macOS 26.0 is available to Objective-C and I'm grateful or that. And how do you define better to use? Do you think the compiler gives better/more descriptive warning/error fixes in Swift than Objective-C? What about viewing variables in the debugger? What about compiler speed? I will continue to use Objective-C until I can't. My policy is currently this: -Any Swift only frameworks that are required (like Storekit2) must be wrapped inside its own framework or library. -All Swift code must be private API. All public API is Objective-C. -Main project remains Objective-C and continues on like Swift doesn't exist. Do I recommend this