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 versa). When device orientation and window shape are aligned, the Launch Screen displays correctly. Question Is it expected that iPadOS renders LaunchScreen.storyboard based on the interface orientation / size class rather than the actual window bounds in multitasking scenarios? If not expected, what is the recommended way to ensure the Launch Screen matches the app’s actual window size/aspect ratio at launch (without using code, since Launch Screen is static)? Are there any additional diagnostics or recommended steps to help us investigate and confirm the root cause (e.g., specific logs, APIs/values to capture at launch such as UIWindowScene bounds, interfaceOrientation, size classes, or any guidance on how Launch Screen snapshots are chosen/cached in multitasking)? Thank you.

Hi everyone I'm experiencing an issue with iPadOS 26 regarding multi-touch gesture detection. When performing a quick four-finger gesture (tap and swipe), the system often fails to recognize the input. This especially affects multi-touch gestures, such as rhythm games with difficult levels. Steps to Reproduce: Place four fingers on the screen. Perform a quick tap or a quick horizontal swipe (like the one used to switch apps). Observe whether the gesture is ignored or detected inconsistently. Expected Behavior: 4-finger multitouch gestures should be recognized regardless of gesture speed, just like previous iPadOS versions. Actual Behavior: Gestures fail to be detected when executed quickly—same gestures still work, and miss notes in rhythm games. You can check out my posts on Twitter/x and Facebook: [https://x.com/kokona_fwa/status/1978131164104728949?s=61] Facebook: [https://m.facebook.com/groups/idipad/permalink/24438964899058806/?]

The Post-Cloud Internet: A 6G Quantum P2P Architecture. 6G, internet networking, hardware, and Quantum Architectural, technical, compendia!. ARCHITECTURAL COMPENDIUM & DATA SHEET Next-Generation 6G P2P Networking, MVI Protocol, & Quantum Infrastructure Document ID: ARC-6G-QPIN-2026 Classification: Public Vision Release Framework Version: 2.4 Vision Overview & Executive Blueprint This architectural compendium outlines a transformative blueprint for the future of global internet communication. By unifying the MVI Protocol for state consistency, IP-to-IP Quantum P2P Meshing, AI-Accelerated Cell Towers, and ultra-high performance hardware, this framework eliminates legacy centralized cloud routing bottlenecks and achieves instant, secure device-to-device connectivity. MVI Protocol & Local Digital Profiles Deterministic State Flow & Physical User Consent The Model-View-Intent (MVI) architecture governs localized network actions to eliminate data leakage and asynchronous race conditions: Local Profile Sovereignty: User identity, cryptographic keys, and personal profiles remain physically anchored on local device storage. Physical Input Validation: No outbound packet transmission occurs without explicit tactile or biometric confirmation (User Consent → Intent State → Encrypted P2P Broadcast). Unidirectional Flow: Guarantees zero background telemetry or third-party harvesting. Quantum Entanglement P2P & Edge-Node Routing Devices do not merely consume data; they act as active routing nodes (routers, cell towers, or orbital relays) forming a resilient mesh network. Network Layer Core Technology Operational Function Endpoint Nodes Personal devices with local digital profiles Instant peer-to-peer pings and localized micro-routing. Quantum Entanglement Core Entangled photon/state-pairs Zero-latency state synchronization across arbitrary geographic distance. Cellular Basestations AI-Integrated Motherboards & Processors Real-time path calculation, load balancing, and mesh optimization. Upgraded Cellular Infrastructure & Dedicated Processors AI-Driven Cell Tower Motherboards & Processors Cell towers are reimagined from passive relay towers into active computing nodes: High-Throughput Ping Processors: Dedicated multi-core silicon architectures built specifically to handle billions of simultaneous micro-pings between peer devices. Dynamic AI Routing Agents: Machine learning micro-controllers embedded directly on the tower motherboards to dynamically compute optimal routing paths between direct P2P mesh links and optical fiber backbones in milliseconds. Hardware Upgrades for 6G Throughput Unlocking Terabit-Scale Bandwidth To support the massive upload/download speeds inherent to 6G and optical infrastructure, foundational hardware components must evolve: Ultra-High-Speed Storage I/O: Next-generation NVMe and solid-state storage controllers capable of sustained read/write speeds exceeding 150 GB/s, preventing I/O throttling during high-speed data bursts. Quantum Batteries: Energy cells leveraging quantum confinement to provide extended lifespan and stable voltage under peak transceiver loads. Direct Optical Interfaces: Physical fiber-optic transceiver ports integrated natively into personal computing motherboards for direct, lossless light-based data transmission. Sincerely: VNB MVI! TECHNICAL WHITE PAPER & COMPENDIUM Hardware Limits, Optimal Silicon, and Infrastructure Upgrades for 6G Quantum P2P Networks Release ID: WP-6G-HW-2026 | Target Domain: Next-Gen Telecom & Edge Compute Introduction & Architectural Scope Realizing a decentralized, instant-connection peer-to-peer (P2P) internet integrated with local digital profiles and quantum entanglement requires pushing past current hardware boundaries. This technical paper details the peak silicon available today, maps out optimal physical thresholds based on fundamental hardware limits, and specifies required upgrades for cell towers, satellites, and client nodes. Current Peak Hardware Standards (State-of-the-Art Silicon) Enterprise Motherboards and Processor Benchmarks To support high-frequency routing, low-latency packet processing, and massive data pipelines, contemporary high-end server architectures provide the baseline for edge-node testing: Server Processing Pinnacle: Platforms utilizing AMD EPYC (5th Gen & Zen 6 architectures) offer up to 192–256 high-density cores per socket with massive multi-channel DDR5 memory bandwidth (>6400 MT/s to MRDIMM standards), making them ideal for high-throughput basestation switching. Workstation & Edge Powerhouse: Intel Xeon 600 Series Workstation Processors provide up to 86 performance-cores (P-cores) with 128 lanes of PCIe Gen 5 connectivity, offering exceptional single-threaded responsiveness for real-time AI micro-agents. Optimal Infrastructure Configuration & Hardware Upgrades Scaling Cell Towers and Satellites to Meet 6G Demands Traditional cell towers acting as passive relay points create unacceptable bottlenecks for P2P mesh architectures. Upgrading infrastructure involves transforming nodes into intelligent compute centers: Infrastructure Node Current Limitation Proposed Hardware Upgrade Cellular Basestations Centralized backhaul dependence; high latency routing via core cloud. Integration of multi-core server motherboards running local AI routing micro-agents and dedicated high-speed packet-switching silicon. Low-Earth-Orbit (LEO) Satellites Slow orbital handoffs and high payload translation delays. On-board quantum state transceivers paired with optical laser inter-satellite links and localized edge-accelerator arrays. Client Endpoints (Devices) Battery drain during continuous mesh pinging and heavy telemetry. Quantum-dot battery cells providing high energy density and stable output under peak transceiver loads. Overcoming Hardware Bottlenecks: Storage & Optical Limits Data Throughput & Physical Interconnects To prevent storage I/O and data transfer speeds from choking 6G wireless pipelines: Storage Read/Write Acceleration: Conventional solid-state drives must transition to high-throughput NVMe architectures capable of sustained sequential speeds exceeding 150 GB/s to prevent cache thrashing during concurrent multi-device streaming. Direct Optical Integration: Eliminating electrical conversion loss by building native fiber-optic transceiver ports straight into computer and server motherboards for light-speed internal routing. Conclusion By pairing current enterprise-grade multi-core processors (such as advanced AMD EPYC and Intel Xeon architectures) with localized AI cell-tower upgrades and quantum entanglement routing layers, the framework presented in this compendium provides a clear roadmap toward a secure, lightning-fast, and completely decentralized global internet. Sincerely: VNB MVI!

Environment: iOS 26; iPad Mini/Air/Pro Problem: In a TextField, I am using a keyboard with the type .decimalPad. When I initially tap into the TextField, the "popover" keyboard (i.e. the decimalPad) shows up and focusses the TextField. However, when I click outside the TextField (to dismiss the keyboard), the TextField is still focussed (the keyboard was dismissed though). When reentering in the TextField, another keyboard (from the bottom of the screen) appears (most likely .numeric). Does anybody know how to solve this? What I already tried: I tried listening to the dismissal of the keyboard to manually set the FocusState to nil. However, the dismissal of the "popover/decimal" keyboard is not recognized as such a dismissal. I also tried to build a custom component out of that, but then I lose the TextField behavior, conflicting with HIG.

On iPadOS 26.x, multiple users of our iPad app report that handwriting English words with Apple Pencil (Scribble) into a text field produces garbled output full of accented / non‑English characters instead of the English letters they wrote. Example of what shows up when a user handwrites a normal English word: -4ęśïćïá. Those accented letters (Polish / Spanish / French‑style diacritics: ę ś ï ć á) are not what the user wrote. Key facts from the reports Happens only on iPadOS 26.x — not seen on earlier iPadOS versions. Happens only with Apple Pencil / Scribble handwriting. Typing into the same field with the on‑screen keyboard is fine. The same users say Scribble works normally in other apps. The affected field is restricted to English‑only input; when that English‑only restriction is turned off, Scribble recognizes the handwriting correctly again. So the trigger appears to be Scribble writing into an English‑restricted field on iPadOS 26. No third‑party keyboards or input methods are involved. Steps (as reported by users) iPad on iPadOS 26.x with an Apple Pencil. Open the spelling/answer screen that has an English‑only input field. Handwrite an English word with the Pencil. The field fills with accented gibberish instead of the word. Question Is this a known iPadOS 26 Scribble regression? Is anyone else seeing garbled / accented output when Scribble writes into an English‑restricted text field? Any workaround short of removing the English‑only restriction? Environment Multiple end users, all on iPadOS 26.x (exact builds / iPad models being collected). I'm the developer and haven't been able to reproduce locally yet, so this is based on user reports.

Our Flutter app has been rejected by App Review 4 times with this description: "Login screen cleared the email and password fields when we attempted to enter the demo account details, preventing us from logging in." Review environment: Device: iPad Air 11-inch (M3) OS: iPadOS 26.4.2 Flutter version: 3.41.4 State management: GetX We cannot reproduce this on: Real iPhone (iOS 18.x) — works fine iPad simulator (iPadOS 26.3.1) — works fine Our TextEditingControllers are created inside a GetX controller, not inside build(), so they survive widget rebuilds. Questions: Has anyone seen text fields clearing or not retaining input specifically on iPad with iPadOS 26? Are there any known Flutter issues with text input on iPadOS 26 that could cause this? Is there anything different about how iPad handles text input vs iPhone that we should be aware of? Any help appreciated — this is blocking our App Store approval.

I'm building an app with a UISplitViewController as the base, with the main content being a UITabBarController. I'm targeting iOS 26+ and using UIKit. I've customised the tabbar on iOS to have a different font family and size, and used some custom images. Running the same app on iPad, the tabbar moves to the top of the screen, ignores ALL the appearance proxy settings and strips out the images. Its now just giant floating text. Also noticed in portrait mode when the side bar from the split view is open, it compresses the width of the tab bar down to only show 2 elements at a time, with this weird custom scroll thing to move to the rest of the tabs. If the text wasn't so massive, maybe it could fit more. I really hate every inch of this thing. Its looks ugly and functions bizarrely. Why does it ignore all the tabbar appearance settings, and how can I customise it to add icons back with smaller text? Ideally I don't want to use one of the hacks to force it to think its compact mode to bring back the old tabbar, as i'm relying on traits already to fix some SplitView annoyances and don't want those to break. But would love to have the old tab bar style. Are there any settings or toggles that I can use?

Hello Apple Developer Support, After updating my iPad to iPadOS Beta 27, the Notes+ app has started crashing frequently. This issue did not happen before the system update. The app often crashes when I open notes, edit content, or try to use files inside Notes+. Another serious issue is that I cannot properly download or import files from iCloud Drive into Notes+. When I try to select a file from iCloud Drive and add it to Notes+, the process may fail, freeze, or cause Notes+ to crash. This has made Notes+ very difficult to use on iPadOS Beta 27. I rely on Notes+ for study notes, file organization, and daily productivity, so this problem has a big impact on my normal use. Steps to reproduce: 1.Use an iPad running iPadOS Beta 27. Open the Notes+ app. 2.Open or edit an existing note. 3.Try to import or attach a file from iCloud Drive. 4.Notes+ may freeze, fail to import the file, or crash. Expected result: Notes+ should run normally, and files from iCloud Drive should be imported into Notes+ successfully. Actual result: Notes+ crashes frequently, and iCloud Drive files cannot be imported reliably. This issue started after updating to iPadOS Beta 27. Please check the compatibility between iPadOS Beta 27, Notes+, and iCloud Drive file importing. Thank you.

Hi there, Hope you are all well. I would like to know on how I am able to develop/build for both current software, like iOS 26 and iOS 27 at the same time. If it is possible, please let me know how. This is also my first WWDC as a developer, so I may have many questions. Sorry in advance lol. Thanks, Jason

I have a custom input view in my app which is .focusable(). It behaves similar to a TextField, where it must be focused in order to be used. This works fine on all platforms including iPad, except when when an external keyboard is connected (magic keyboard), in which case it can't be focused anymore and becomes unusable. Is there a solution to this, or a workaround? My view is very complex, so simple solutions like replacing it with a native view isn't possible, and I must be able to pragmatically force it to focus. Here's a very basic example replicating my issue. Non of the functionality works when a keyboard is connected: struct FocusableTestView: View { @FocusState private var isRectFocused: Bool var body: some View { VStack { // This text field should focus the custom input when pressing return: TextField("Enter text", text: .constant("")) .textFieldStyle(.roundedBorder) .onSubmit { isRectFocused = true } .onKeyPress(.return) { isRectFocused = true return .handled } // This custom "input" should focus itself when tapped: Rectangle() .fill(isRectFocused ? Color.accentColor : Color.gray.opacity(0.3)) .frame(width: 100, height: 100) .overlay( Text(isRectFocused ? "Focused" : "Tap me") ) .focusable(true, interactions: .edit) .focused($isRectFocused) .onTapGesture { isRectFocused = true print("Focused rectangle") } // The focus should be able to be controlled externally: Button("Toggle Focus") { isRectFocused.toggle() } .buttonStyle(.bordered) } .frame(maxWidth: .infinity, maxHeight: .infinity, alignment: .center) } }

I have encountered the following issue on iPadOS. Has anyone experienced this issue or reported it before? Steps to Reproduce Enable Windowed Apps mode in Settings. Launch the Settings app and another app (App X), and display both in windowed mode. Use the Settings app to completely cover App X (App X becomes inactive at this point). From the Settings app, enable Full Screen Apps mode. Bring App X to the foreground. Expected Result App X becomes active when brought to the foreground. Actual Result Even after bringing App X to the foreground, it immediately becomes inactive. The issue persists even if App X is restarted. To resolve the issue, it is necessary to either restart the iPad or switch back to Windowed Apps mode. Verified OS Versions iPadOS 26.5: Reproducible iPadOS 26.4.2: Reproducible iPadOS 26.2: Not reproducible iPadOS 26.0.1: Not reproducible Additional Information According to the console logs, App X appears to remain inactive because the deactivation reason "sceneOverlap" persists.

Is there a safeAreaInsets equivalent that only tracks system bars (tab bars, status bars, side bars, toolbars, and navigation bars) and is not affected by notches? I'm asking this because the iPadOS tab bar can appear either on the top, bottom, or left (modally or non-modally) in various configurations, including sidebarAdaptable and when the window size is small on iPadOS; the tab bar's frame is not really reliable in this case, and while the safe area insets works, it also includes the notches / rounded window corners...

The app crashes when using EAAccessoryManager.showBluetoothAccessoryPicker(withNameFilter:) to connect to a Bluetooth accessory in a multi-accessory scenario. The crash occurs immediately after selecting an accessory from the picker UI. Steps to Reproduce: Ensure a Bluetooth accessory (Accessory A) is already connected to the iPhone/iPad and is visible in Bluetooth settings. Launch the app. Initiate a connection flow that presents the Bluetooth accessory picker using EAAccessoryManager.showBluetoothAccessoryPicker(withNameFilter:). Ensure another compatible accessory (Accessory B) is available and visible in the picker. Select Accessory B from the picker to connect. After connection, simulate a disconnect of Accessory B (e.g., power cycle or remove battery). Attempt to reconnect Accessory B by triggering the same picker flow again. Select Accessory B from the picker. Result: The accessory connects successfully at the system level. The app crashes immediately after selecting the accessory from the picker (during dismissal). Reproducibility: Occurs consistently under the described multi-accessory scenario. Not observed when only a single accessory is present.

I got 2 crash in my iPad app, didn't konw why. The first crash infomation is: Invalid parameter not satisfying: configuration != nil. The second crash infomation is: /Library/Caches/com.apple.xbs/Sources/UIKitCore/Metrics/_UIListMetrics+Extensions.swift:110: Fatal error: Trait collection does not specify a user interface idiom. Trait collection: <UITraitCollection: 0x133d0e940; DisplayScale = 1, DisplayGamut = P3, HorizontalSizeClass = Regular, VerticalSizeClass = Regular, UserInterfaceStyle = Light, UserInterfaceLayoutDirection = LTR, ForceTouchCapability = Unavailable, PreferredContentSizeCategory = XXL, AccessibilityContrast = High, UserInterfaceLevel = Base, ImageDynamicRange = 0, SceneCaptureState = 0> Can someone help

Hello, I'm experiencing a navigation bar positioning issue with my UIKit iPad app on iPadOS 26 (23A340) using Xcode 26 (17A321). The navigation bar positions under the status bar initially, and after orientation changes to landscape, it positions incorrectly below its expected location. This occurs on both real device (iPad mini A17 Pro) and simulator. My app uses UIKit + Storyboard with a Root Navigation Controller. A stack overflow post has reproduce the bug event if it's not in the same configuration: https://stackoverflow.com/questions/79752945/xcode-26-beta-6-ipados-26-statusbar-overlaps-with-navigationbar-after-presen I have checked all safe areas and tried changing some constraints, but nothing works. Have you encountered this bug before, or do you need additional information to investigate this issue?

Hey everyone, Back in 2022 and 2023, we noticed that some images on our web pages would disappear randomly. After refreshing, some of the images that were missing would appear, but then another image would go missing. Did anyone else experience this issue? Is there a fix / workaround I can use? This only seems to be an issue on iOS devices and images that have the loading=“lazy” attribute.

We are seeing an issue after updating iPads to iPadOS 26.4 where cellular service is lost until network settings are reset. Environment: Devices managed via Apple Business Manager and Microsoft Intune Carrier: Verizon Confirmed affected devices: iPad (9th generation) eSIM Behavior: After update, device shows no cellular service No prompt to re-activate or re-add the cellular plan The plan appears to still be present on the device Workaround observed: Resetting Network Settings restores service Notes: This does not appear to be a provisioning issue (no need to re-add eSIM) Behavior suggests the cellular/eSIM state may not be initializing correctly after update Toggling Cellular or Airplane mode has not yet been tested for service restoration. We have not yet confirmed whether devices using a physical SIM are affected Still gathering data on scope across additional iPad models Additional observation: We have not observed this behavior on iPhones (e.g., iPhone 16 on iOS 26.4 with LTE remains unaffected) Has anyone else observed similar behavior on iPadOS 26.4, particularly on managed devices or eSIM configurations?

In an application we are developing, we would like to show a (non-interactable) textfield when a hardware keyboard is connected to the iPad. Therefore my question: Using SwiftUI, is it possible to detect the presence of a hardware keyboard and store that state inside a boolean like isHardwareKeyboardConnected?

MyOwnKeyboard Pad app has 4 text views with textfields that use touch screen for editing. There is one view, Compose, that has a textfield and a textview (UIRepresentable). The app enters text into the view using textfield buttons. The app has total control of editing. When entering text if the screen is touched it conflicts the cursor position and creates an "out of bounds" failure. In that view the app does not need any touch events. I need a method in UIRepresentable to disable the touch event. I am not familiar with UIRepresentable as this code was provided by Apple to solve a 16 bit unicode character issue. What would be the code to disable touch events in the UIRepresentable compose view. The app is free for a while until this problem is fixed. It is for iPads 11"+ . The name in the app store is MyOwnKeyboard Pad. I know some great engineer will find the answer. DTS tried. Thanks to all, maybe I'll sell some. Charlie 25mar26

Hi everyone, I am experiencing a strange rendering issue on iPadOS 26 when sizeRestrictions.minimumSize is set on a UIWindowScene. After rotating the device and then rotating it back to the original orientation, the window appears to be stretched based on its previous dimensions. This resulting "stretched" area does not resize or redraw correctly, leaving a significant black region on the screen. Interestingly, as soon as I interact with the window (e.g., a slight drag or touch), the UI snaps back to its intended state and redraws perfectly. Here is a sample code and capture of behavior. class SceneDelegate: UIResponder, UIWindowSceneDelegate { var window: UIWindow? func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) { guard let windowScene = (scene as? UIWindowScene) else { return } windowScene.sizeRestrictions?.minimumSize = CGSize( width: 390, height: 844 // larger than the height of iPad in landscape ) // initialize... } } Has anyone else encountered this behavior? If so, are there any known workarounds to force a layout refresh or prevent this "ghost" black area during the rotation transition? Any insights would be greatly appreciated. Thanks!