We recently released an update to our app to prepare for TX SB2420. Almost immediately on release, we started getting crash reports of crashes when calling isEligibleForAgeFeatures. Crashed: com.apple.root.user-initiated-qos.cooperative EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000004 Is it possible that these are beta users that have IOS 26.2 RC or is there a bug in the release version of IOS 26.2? Note: The crash reports are coming from Crashlytics so we are not getting OS build identifiers other than version "26.2"

#1) The docs for the significantAppChangeApprovalRequired option (https://developer.apple.com/documentation/declaredagerange/agerangeservice/parentalcontrols/significantappchangeapprovalrequired) are a bit unclear of the meaning. If this is set to true, does that mean (a) its an indication from Apple that the user is in a jurisdiction that requires approvals for significant app changes or (b) the App store has detected a significant app change and the app needs to use PermissionKit to re-obtain approval. #2) In section Sec.A121.053 of SB2420, it states "The developer of a software application shall provide notice to each app store through which the developer makes the software application available before making any significant change..." and there are several subsections that define what constitutes a signficant app change that include items like "change of personal data stored", etc. How can developers notify the app store that a significant change has occurred and how can the app then query the app store to detect these changes?

We use an embedded WKWebView for several screens in our app. Recently, we have been testing keyboard navigation via Full Keyboard Access in our apps. On IOS 18, everything works pretty much as expected. On IOS 26, it does not. On IOS 26, you can "tab" away from the webview and then never tab back to the webview for keyboard navigation. Is this a known issue? Are there workarounds for this issue that anyone is aware of?

Is there any reference/documentation/discussion about the motivation for including the WKWebView loadSimulatedRequest() method? Is it intended to be used for testing? Page load performance enhancement? I'm wondering if there is a way to leverage its usage in our webview dependent app.

Hi. We can see output from dyld, when adding the DYLD_PRINT_STATISTICS=1 env var, in the XCode console when running from simulator. When running on device the statistics are not printed in either XCode console or Console.app. Is there a way to get this info when running an app on device?