iPadOS 17.7.7

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

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!

Dear Support Team, I am writing to seek technical assistance regarding a persistent issue with Dolby Vision exporting in DaVinci Resolve 20 on my iPad Pro 12.9-inch (2021, M1 chip) running iPadOS 26.0.1. The Issue: Despite correctly configuring the project for a Dolby Vision workflow and successfully completing the dynamic metadata analysis, the Dolby Vision Profile dropdown menu (and related embedding options) is completely missing from the Advanced Settings in the Deliver page. My Current Configuration & Steps Taken: Software Version: DaVinci Resolve Studio 20 (Studio features like Dolby Vision analysis are active and functional). Project Settings: Color Science: DaVinci YRGB Color Managed. Dolby Vision: Enabled (Version 4.0) with Mastering Display set to 1000 nits. Output Color Space: Rec.2100 ST2084. Color Page: Dynamic metadata analysis has been performed, and Trim controls are functional. Export Settings: Format: QuickTime / MP4. Codec: H.265 (HEVC). Encoding Profile: Main 10. The Problem:

Hello， We’re seeing an iPad-specific Launch Screen issue related to multitasking window sizes. Environment Device: iPad (iPadOS 26) Device orientation: Landscape App is launched in a small window where the app window is portrait-shaped (width < height) Issue When the iPad is in landscape but the app is launched as a portrait-shaped small window, the LaunchScreen.storyboard appears to be rendered/layouted as landscape, not matching the actual window geometry. As a result, the Launch Screen content is clipped / partially missing (we see blank/empty area at the bottom during launch). After the app finishes launching, our first view controller uses the correct window size and the UI looks fine — the problem is mainly during the Launch Screen phase. What we checked LaunchScreen.storyboard uses Auto Layout and is expected to adapt to screen/window size. This only reproduces when the device orientation and the app window aspect ratio don’t match (landscape device + portrait-shaped app window, or vice ver

1. Summary In a hybrid iOS app using WKWebView (Angular + Capacitor), after programmatically blurring an element and connecting a Bluetooth keyboard, pressing Ctrl+Home or Ctrl+End causes the app to crash. The crash stack shows the issue occurs inside UIKit keyboard handling (UITextInteractionSelectableInputDelegate _moveToStartOfLine), indicating a system-level bug. 2. Steps to Reproduce Open the hybrid app containing a WKWebView. Blur the input (programmatically). Connect a Bluetooth keyboard. Press Ctrl + Home or Ctrl + End. Expected result: No crash. The command should be ignored if no text input is active. Actual result: App crashes immediately. 3. Crash Log (Crashlytics Trace) Crashed: com.apple.main-thread 0 WebKit 0xfbdad0 + 236 1 UIKitCore 0x10b0548 -[UITextInteractionSelectableInputDelegate _moveToStartOfLine:withHistory:] + 96 2 UIKitCore 0xd0fb38 -[UIKBInputDelegateManager _moveToStartOfLine:withHistory:] + 188 3 UIKitCore 0xa16174 __158-[_UIKeyboardStateManager handleMoveCursorToStartOfLine:befo