iPadOS 17.7.7

Hello everyone, I’m facing an issue with In-App Purchases during App Review and would appreciate guidance from anyone who has encountered a similar situation. Context: New iOS/iPadOS app, first submission. One Non-Consumable In-App Purchase. IAP was created, fully configured, and submitted together with the app version. IAP status in App Store Connect: In Review. App includes Restore Purchase and uses standard StoreKit purchase flow. Paid Apps Agreement is accepted. Problem: During Apple’s review, when the reviewer taps the purchase button, a generic error appears: “Purchase failed. An error occurred, please try again.” Apple rejected the app under Guideline 2.1 – Performance – App Completeness, stating that the IAP shows a bug. What seems to be happening: The IAP itself is still in review and therefore not fully active, which causes the purchase attempt to fail. However, the app cannot be approved because the purchase fails, creating a circular dependency: App cannot be approved because IAP purchase

In iOS 18, TabView with .tabViewStyle(.sidebarAdaptable) introduced a powerful adaptive pattern — tabs in compact, sidebar in regular. However, the current Tab API only supports a title and an image (icon). There is no way to provide a trailing accessory view (e.g., a secondary icon or indicator) for sidebar rows. This is a meaningful gap in the API, because trailing accessories are a well-established pattern throughout UIKit and SwiftUI. Precedent in Apple's own design language Apple already supports trailing accessories in many analogous contexts: UITableViewCell / UICollectionViewListCell — support accessories (disclosure indicators, checkmarks, custom views) via UICellAccessory. UIListContentConfiguration — allows leading and trailing content in list rows. SwiftUI List rows — support Label, HStack with trailing elements, .badge(), and swipeActions. NavigationLink — automatically renders a disclosure chevron as a trailing accessory. UITabSidebarItem (UIKit, iOS 18) — supports configurationUpdateHandler and

I'm working on my Swift Student Challenge 2026 submission and have a question about the evaluation environment. My app targets iOS 26 (I had to configure this on the Package.swift file directly) and uses the Speech framework for on-device speech recognition. I've selected Swift Playgrounds as my evaluation path (rather than Xcode) with the intention of having it run on a physical iPad rather than Simulator. My question: What version of iPadOS will the evaluation iPads be running? The reason I ask is practical, as my app's minimum deployment target is iOS 26. If the evaluation device is running an earlier version of iPadOS, the app won't launch at all. I've searched the eligibility and terms pages but couldn't find this documented anywhere.

Is it possible to drive NavigationSplitView navigation with a view in sidebar (left column) that is not a List? All examples that I have seen from this year only contain List in sidebar. I ask this because I would like to have a more complex layout in sidebar (or first view on iOS) that contains a mix of elements, some of them non-interactive and not targeting navigation. Here’s what I would like to do: import SwiftUI struct Thing: Identifiable, Hashable { let id: UUID let name: String } struct ContentView: View { let things: [Thing] @State private var selectedThingId: UUID? var body: some View { NavigationSplitView { ScrollView(.vertical) { VStack { ForEach(things) { thing in Button(Thing: (thing.name) ( selectedThingId == thing.id ? selected : )) { selectedThingId = thing.id } } SomeOtherViewHere() Button(Navigate to something else) { selectedThingId = someSpecificId } } } } detail: { // ZStack is workaround for known SDK bug ZStack { if let selectedThingId { Text(There is a thing ID: (selectedThingId)) }

Following is an error I encounter when trying to run a foundation model function in simulator. Error Domain=FoundationModels.LanguageModelSession.GenerationError Code=-1 (null) UserInfo={NSMultipleUnderlyingErrorsKey=( Error Domain=ModelManagerServices.ModelManagerError Code=1026 (null) UserInfo={NSMultipleUnderlyingErrorsKey=(n)} )} Its a swift playground I'm building in xcode and works fine in the preview and on a real device too but since it's my submission for the swift student challenge I need it to run on the simulator. I have updated my macOS to latest version of Tahoe(26.3) and Xcode is also on latest version. The simulator I run the playground is also on ios and iPadOS 26. I have set my region to US and have turned on Apple Intelligence on my mac too. Any suggestions on how to fix the issue?👾

Hi everyone, I’m looking for clarification regarding an App Review rejection under Guideline 2.1 – Performance – App Completeness. Apple reported the following issue: Bug description: “Create PIN” button was not responsive Review device: iPad Air 11-inch (M3) OS version: iPadOS 26.2.1 What’s confusing is the following: Observed behavior on our side The app has been tested extensively on: Multiple iPhone models iPad devices (including recent iPadOS versions) In all our testing: The Create PIN button is responsive The tap action triggers correctly The flow completes without errors At this point, we are unable to reproduce the issue described by App Review on either iPhone or iPad. iPhone-only intent vs iPad review The app is designed and optimized for iPhone usage only. However, the review was performed on an iPad device. If an app is available for download on iPad, is it always expected to function fully on iPad regardless of being phone-optimized? If iPad support is not intended, is explicit

There is a problem with the launchscreen of my application on iPadOS 26. After release of the windowed mode feature the launchscreen of my fullscreen landscape-only application is being cropped and doesn't stretch to screen's size when the device is in the portrait mode. How can I fix this?

I am currently developing my submission for the Swift Student Challenge 2026. My project focuses on financial literacy for children (Canteen Hero), and I want to ensure it runs flawlessly during the judging process. I have two specific questions regarding the environment: Which iOS/iPadOS version do judges typically use for testing? Should I assume they will be using the latest stable release (e.g., iOS 19/iPadOS 19) or a specific beta version? Device Compatibility: Is it a requirement to design the app for all previous iOS versions (backward compatibility), or is it acceptable to target only the latest APIs (iOS 18/19+) to utilize modern features like SwiftData and the latest SwiftUI animations? Thank you for your guidance!