iPadOS 17.7.7

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

Hi @dminbear , Please submit any feedback directly to the App Store and StoreKit engineering teams with Feedback Assistant: For technical questions about using the Declared Age Range API, such as how to present age range share requests, and the associated age bands and age categories, visit Feedback Assistant and select iOS & iPadOS > Developer Technologies & SDKs > Declared Age Range Framework. For technical questions about using PermissionKit, such as how to communicate significant changes to your app, visit Feedback Assistant and select iOS & iPadOS > Developer Technologies & SDKs > PermissionKit Framework. To learn more about providing feedback, please see below: Bug Reporting https://developer.apple.com/bug-reporting/ Once submitted, please respond here with the Feedback ID, so I may escalate internally. Cheers, Paris X Pinkney |  WWDR | DTS Engineer

Hi @jonathanm@takeoffmedia.com, Please submit any feedback directly to the App Store and StoreKit engineering teams with Feedback Assistant: For technical questions about using the Declared Age Range API, such as how to present age range share requests, and the associated age bands and age categories, visit Feedback Assistant and select iOS & iPadOS > Developer Technologies & SDKs > Declared Age Range Framework. For technical questions about using PermissionKit, such as how to communicate significant changes to your app, visit Feedback Assistant and select iOS & iPadOS > Developer Technologies & SDKs > PermissionKit Framework. To learn more about providing feedback, please see below: Bug Reporting https://developer.apple.com/bug-reporting/ Once submitted, please respond here with the Feedback ID, so I may escalate internally. Cheers, Paris X Pinkney |  WWDR | DTS Engineer

Hi @chou_ios, Where legally required, you must check the age of the people using your app, starting with new Apple Accounts created in Texas on or after January 1, 2026, which has obligations only for iOS and iPadOS apps. To learn more, see Next steps for apps distributed in Texas. To test content revocation in Sandbox on iOS and iPadOS 26.2 and later, please see the documentation below: Testing Age Assurance in Sandbox https://developer.apple.com/documentation/storekit/testing-age-assurance-in-sandbox Navigate to your Sandbox Apple Account settings Access your Sandbox Apple Account settings to configure Age Assurance test scenarios: Confirm that you have enabled Developer Mode. If you haven’t, see Enabling Developer Mode on a device Open Settings and select Developer. Scroll down to Sandbox Apple Account. If you’re not logged in to an account, select Sign In to authenticate yourself. Once you’re signed in, select your Apple Account. Test Age Assurance on device Test various age range scenar