iPadOS 17.7.7

I used standard font styles in an iOS app. For example .font(.headline). I hoped that developing this way would allow the adoption of the app to other platforms, relatively easy. However, when trying to run for iPadOS, the text did not increase in size to occupy the more abundant space offered by larger screen, but it actually shrank. Overall, the app does not look great automatically. Why does it happen? What is the best practice for cross platform development with SwiftUI (with regards to font sizes). I want to make as little as possible human interface design decisions on my own and just let SwiftUI take care of everything. (But I also want the results to look as Apple would consider great looking)

Hello.I am implementing a SwiftUI Drag and Drop application which runs fine on both macOX and IpadOS.The only problem I have is that on iPadOS, the Dragged image is rendered just as an empty rectangle, while on macOS I have a correct dragged image.The body of the view from which the items are dragged is : var body: some View { HStack { ForEach( libraryRowItems, id: .self) { thelibraryItem in libraryItemView(item: thelibraryItem) .onDrag { return NSItemProvider(object: NuageIdentifier(identifier:thelibraryItem.id)) } } } }and the body for libraryItemView : var body: some View { let topColorGradient = Color(Color.RGBColorSpace.sRGB, red: 0.298, green: 0.301, blue: 0.301); let bottomColorGradient = Color(Color.RGBColorSpace.sRGB, red: 0.235, green: 0.239, blue: 0.239); return ZStack { RoundedRectangle(cornerRadius: 5) .fill(LinearGradient(gradient: Gradient(colors: [topColorGradient, bottomColorGradient]), startPoint: .top, endPoint: .bottom)) Text((text)).foregroundColor(.white).font(.custom(STIX2Math,

https://github.com/apple/sample-food-truck Hi! I'm following along with the sample-food-truck application from WWDC 2022. I'm seeing some weird navigation issues when building the app for iPadOS. The Table component displays a Select Button for selecting elements and a Done Button disabling that state. These buttons seem to be breaking something about navigation on iOS 18.4.1. It's a nondeterministic issue… but tapping the buttons seems to lead to some corrupt state where the app transitions out of OrdersView and back to TruckView. This code from FoodTruckModel seems to be making a difference: Task(priority: .background) { var generator = OrderGenerator.SeededRandomGenerator(seed: 5) for _ in 0..<20 { try? await Task.sleep(nanoseconds: .secondsToNanoseconds(.random(in: 3 ... 8, using: &generator))) Task { @MainActor in withAnimation(.spring(response: 0.4, dampingFraction: 1)) { self.orders.append(orderGenerator.generateOrder(number: orders.count + 1, date: .now, generator: &generator)) } }

Multiple payloads are allowed for App notification settings payload for macOS devices, but for iOS/iPadOS devices they are not allowed. And this restricts us to maintaining/keep track of a single profile having app notifications payload. May I know the reason behind this? Reference : https://developer.apple.com/documentation/devicemanagement/notifications

I'd like to use the eye tracking feature in the latest iPadOS 18 update as more than an accessibility feature. i.e. another input modality that can be detected by event + enum checks similar to how we can detect and distinguish between touches and Apple pencil inputs. This might make it a lot easier to control and interact with iPad-based AR experiences that involve walking around, regardless of whether eye-tracking is enabled for accessibility. When walking, it's challenging to hold the device and interact with the screen with touch or pencil at all. Eye tracking + speech as input modalities could assist here. Also, this would help us create non-immersive AR experiences that parallel visionOS experiences that use eye tracking. I propose an API option for enabling eye-tracking (and an optional calibration dialogue within-app), as well as a specific UIControl class that simply detect when the eye looks at the control using the standard (begin/changed/end) events. My specific use case is that I'd like