iPadOS 17.7.7

Framework compatibility: My app uses Foundation Models and Apple Pencil. The app runs great through Xcode; however, due to Apple Pencil support, it has to be run on a physical device. However, Swift Playgrounds on iPad doesn't support iOS 26. I was just wondering if this is something that can be mentioned in submission notes. eg. The app needs to be compiled in Xcode but run on a physical device.” Or should we expect iPadOS 26 support for Swift Playgrounds by the time of submission? Thank you!

One more, all crash is happening in iOS 26.1.0 and iPadOS 26.1.0

👋 Hello According to the regulations, you can only create the swift playground project, not the Xcode project. ( But you can still use Xcode to create a swift playground project). And the iPadOS program of the swift playground project must be submitted to the competition requirements, and the swift playground project does not support watchOS. So I think you need to create a swift playground project and develop an iPadOS app and submit it to SSC. You can see the detailed rule information here: https://developer.apple.com/swift-student-challenge/eligibility/ I hope this will be helpful to you.

We're experiencing a similar UpdateCycle crash on iOS 26, though with a slightly different manifestation. Our crash occurs when displaying custom inputView keyboards on iPad devices. Crash Details: Exception: NSInternalInconsistencyException Message: Invalid parameter not satisfying: parentEnvironment != nil Location: UC::DriverCore::continueProcessing() at address 5472 in UpdateCycle library OS Version: iPadOS 26.1.0 (84.6% of crashes), also seen on 26.0.0 and 26.0.1 Device: 100% iPad devices (iPad Pro models, all in landscape orientation) Reproduction Context: The crash occurs when a custom UIView is set as textField.inputView and the text field becomes first responder on iPad. The crash happens during UpdateCycle's processing when it attempts to access the focus environment hierarchy. The custom keyboard view appears to be accessed by UpdateCycle before it's fully integrated into the focus hierarchy, resulting in a nil parentEnvironment. Key Observations: iPad-specific: All crashes occur on iPad d

I tried reproducing this problem on an iPhone 16 running iOS 26.2 (23C55), an iPad Pro (M4) running iPadOS 26.2 (23C55), and on a Mac Book Pro running macOS 26.2 (25C56) and I was not able to reproduce the problem as described. I reloaded the pages a couple of times and scrolled the page up and down for a number of times. Possibly this is a network related issue? Maybe try reproducing the problem on some other network(s)? If this problem persists, consider opening a Technical Support Request so we can exchange additional information such as sysdiagnose reports and other logging information to try to track down the root cause of the problems you are seeing. https://developer.apple.com/support/technical/. If you start a new request please provide a url to this thread so the support request can be assigned to my attention.

Hello Justin, As you suggested, I have repeated the tests multiple times, but I was not able to reproduce the crash. As mentioned, it appears to be difficult to encounter the issue consistently. I would also like to share an additional observation: we ran the same application on iPads with iPadOS 18.1 for nearly six months without encountering any crashes. However, after updating the devices to iPadOS 18.6.2, the crashes started occurring. Since the only change during this period was the iPadOS update from 18.1 to 18.6.2, I would appreciate your insight on whether any changes in this OS update could potentially contribute to this behavior?

Hi @Kelvin.Lau, The steps listed on Testing Age Assurance in Sandbox are outdated (r. 166835996). Test various age range scenarios on the Sandbox Apple Account page in iOS or iPadOS by following these steps: Confirm Developer Mode is enabled. If not, see Enabling Developer Mode on a device. Open Settings and select Developer. Scroll down to Sandbox Apple Account. If an account is not logged in, select Sign In to authenticate. When authenticated, select your Apple Account. From the presented Sandbox Apple Account modal, select Manage. Scroll down and select Age Assurance or Revoke App Consent. Cheers, Paris X Pinkney |  WWDR | DTS Engineer

@DTS Engineer thanks for the information. you must build your app against the iOS 26.2 and iPadOS 26.2 SDKs and later, with Xcode 26.2 (17C52) and later But a clarification needed: is using Xcode 26 required only to access all API ? Can you confirm that to keep the app updatable on AppStore, it is enough to update meta data on age ratings and submit the app, even if compiled with Xcode 16 ?

Hi @Umeki, To enable all the technologies and access all the signals Apple has made available to comply with regional age assurance requirements, starting with Texas, you must build your app against the iOS 26.2 and iPadOS 26.2 SDKs and later, with Xcode 26.2 (17C52) and later. To view the latest Xcode versions and SDKs, see here. As of iOS 26.2 and iPadOS 26.2, age assurance includes the following signals: Declared Age Range API — Determine whether a person using your app is in an applicable region that requires additional age-related obligations. When a child account, or their parent or guardian, chooses to share age information, the Declared Age Range API will return the age band or age category, depending on legal requirements in the region. The API will also provide information about the method used to confirm the age band or category, whether parental controls are enabled, and whether the user is eligible for age gated features. For more details, see the following documentation: AgeRan