Hello Apple Developer Community, I am seeking clarification on the intended display behavior of HLS audio tracks within the iOS 26 (or current beta) native player, specifically concerning the NAME and LANGUAGE attributes of the EXT-X-MEDIA tag. In our HLS manifests, we define alternative audio tracks using EXT-X-MEDIA tags, like so: #EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID="audio",LANGUAGE="ja",NAME="AUDIO-1",DEFAULT=YES,AUTOSELECT=YES,URI="audio_ja.m3u8" #EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID="audio",LANGUAGE="ja",NAME="AUDIO-2",URI="audio_en.m3u8" Our observation is that when an audio track is selected and its name is displayed in the native iOS media controls (e.g., Control Center or within a full-screen video player's UI), the value specified in the NAME attribute ("AUDIO-1", "AUDIO-2") does not seem to be used. Instead, the display appears to derive from the LANGUAGE attribute ("ja", "en"), often showing the system's localized string for that language (e.g., "Japanese", "English"). We would like to understand the official or intended behavior regarding this. Is it the expected behavior for the iOS native player to prioritize the LANGUAGE attribute (or its localized equivalent) over the NAME attribute for displaying the selected audio track's label? If this is the intended design, what is the recommended best practice for developers who wish to present a custom, human-readable name for audio tracks (beyond the standard language name) in the native iOS UI? Are there any specific AVPlayer properties or AVMediaSelectionOption considerations that would allow more granular control over this display, or is this entirely managed by the system based on the LANGUAGE attribute? Any insights or official guidance on this behavior in iOS 26 (and potentially previous versions) would be greatly appreciated. Thank you for your time and assistance.

Since last week I get this error when uploading my app to app store Connect: Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases. (ID: 18be8ca4-805d-4cc2-9b3d-3c7a97a89c7b) I could upload before. I have the Tahoe Beta 26.0 iOS installed and the xcode 26.0 beta 4. Does anyone has advise on how to solve this issue?

I've added some menus to the new (mac-like) menu bar on the iPad App under iPadOS 26, which is working fine. However if the main view controller covers the whole screen and shows a fullscreen Map (MKMapView), the menu bar has a dark gradient as a background, which makes it extremely difficult to see the menu. I guess the iPadOS tries to put a semi-transparent layer between the view controller and the menu bar to make sure that the content of the view controller doesn't interfere with with the menubar and the menu is easy to read. But when the view controller shows a map, the system seems to get the colors for this transparent layer wrong. Is it possible to solve this, or is this still a bug of iPad OS 26? Interestingly, when I create a screenshot of the screen, this dark gradient which makes the menu bar unreadably is not included in the screenshot. So in the screenshot the menu is easy to read. Only on the real device, the menu bar is almost unreadably

Lucid app frozen after ios26 beets install. Any ideas when the fix will occur?

Hello Apple team and community, I’m reporting a critical issue affecting iPhone 13 (128 GB) on iOS 26 Public Beta 3. Problem Summary: • Device stays stuck at 1% battery, even while charging • Battery Health shows 0% in Settings • Phone reboots every 5 minutes while unplugged • Only works when connected to power • Cannot update, charge properly, or maintain uptime Additional Context: • The issue appeared immediately after installing iOS 26 beta 3 • Affected devices often have a replaced battery (even official or high-quality replacements) • Seems to be a software validation bug related to battery firmware • Reported by many users across Reddit, Apple Forums, and Twitter — but not listed in Known Issues What Has Been Tried: • Recovery Mode / Safe charging / Clean install (same version) – no effect • Third-party repair tools (ReiBoot, 3uTools) — partial workaround • Jailbreak with Nugget or iCleaner to disable crash daemons – temporarily helps • Apple Support suggested full device replacement (!) ⸻ Request: Please investigate and acknowledge this issue. This bug renders devices unusable for users with legitimate battery replacements — we need a fix in an upcoming beta.

Using the #Playground macro in beta 3 worked fine, but the Playgrounds package appears to be missing in beta 4. import Playgrounds #Playground { print("🚀 Playground is active") } Canvas error message: Cannot find playgrounds Check whether the playground is compiled for the current scheme and OS of the selected device. There could be compile time checks filtering playgrounds out. Check for dead code stripping or other settings that could exclude playgrounds from the final binary.

The information menu in the settings doesn’t work. It automatically exits to the main screen.

Hi, Have done the update for IOS Beta 4 and after it was done the screen just had the background and no icons. Couldn't get to any of the icons. Tried to do a restore on the iPad from my Mac and it started the restore but then got the message that it errored out and gave me this: Need help trying to get this fixed. Also tried a computer that wasn't in the beta and got the same error message. Tried to turn it off and then see if it would go back to the error before and it just stays in recovery mode. Please help. Thank you.

Hi, developers, I maintain a shipped app that uses string concatenation to construct Metal shader and compile on-device. Beta 4 seems disabled __asm keyword, resulting the compilation failure. The error is: v2/GEMMKernel.cpp:229: error: program_source:23:9: error: illegal string literal in 'asm' __asm("air.simdgroup_async_copy_1d.p3i8.p1i8"); The relevant code is available at https://github.com/liuliu/ccv/blob/unstable/lib/nnc/mfa/v2/GEMMHeaders.cpp#L30 although any __asm will trip this. Please give us guidance on whether this is a regression or this will be something enforced in 26 release. Personally, I would consider this as a bug given it won't impact anything "compiled" shaders. Thanks for your patience reading this!

I’m working on an old iPad app with a concept that only works in landscape mode. The app’s content is not dynamic and can’t be rearranged depending on the window size. To ensure a good user experience, I set the UIRequiresFullScreen key to true in the Info.plist. Despite this, it’s still possible in iPadOS 26 to resize an app that requires fullscreen. When this happens, the three-dot button overlaps the content, and elements placed in the top-left corner become hard to access. Is there a way to detect when an app is resized and/or when the three-dot button overlaps the app? The UIScreen / UIScene or UIWindow bounds don’t seem to change when UIRequiresFullScreen is set to true. Also, UIScene.isFullscreen always returns false.

I disable 4 or 5 Finger Gestures on Settings.app > Multi-tasking and Gestures. But in the third-party apps, 4-5 finger touches are sometimes immediately cancelled. Especially, 4-5 finger swipe gesture. I filed this issue to FB19226717. I develop Piano instrument app. 4 or 5 finger touches are required for that kind of apps. Please fix this, Apple.

I have a Generable type with many elements. I am using a stream() to incrementally process the output (Generable.PartiallyGenerated?) content. At the end, I want to pass the final version (not partially generated) to another function. I cannot seem to find a good way to convert from a MyGenerable.PartiallyGenerated to a MyGenerable. Am I missing some functionality in the APIs?

Hey everyone, Just wanted to share a critical issue we’ve encountered while testing our app on iOS 18 simulators and devices using Xcode 26 Beta 3: Crash Details We're seeing the following fatal exception during launch: NSInvalidUnarchiveOperationException Could not instantiate class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ because no class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ was found... The crash originates from Storyboards/XIBs that include a UIToolbar. It appears UIKit is referencing an internal SwiftUI-related class (UICoreHostingView), which isn't present at runtime — leading to immediate crashes. Affected: Apps using UIToolbar in Storyboards or XIBs Running on iOS 18 (Simulators or Devices) and below Built using Xcode 26 Beta 3 CrashLog: Fatal Exception: NSInvalidUnarchiveOperationException 0 CoreFoundation 0x11a21c __exceptionPreprocess 1 libobjc.A.dylib 0x31abc objc_exception_throw 2 CoreFoundation 0x178ea0 -[NSException initWithCoder:] 3 UIFoundation 0x28774 UINibDecoderDecodeObjectForValue 4 UIFoundation 0x28a18 UINibDecoderDecodeObjectForValue 5 UIFoundation 0x28cac -[UINibDecoder decodeObjectForKey:] 6 UIKitCore 0x21e680 -[UIView initWithCoder:] 7 UIKitCore 0x9b4784 -[UIToolbar initWithCoder:] 8 UIFoundation 0x28890 UINibDecoderDecodeObjectForValue 9 UIFoundation 0x28cac -[UINibDecoder decodeObjectForKey:] 10 UIKitCore 0x1e3a80 -[UIRuntimeConnection initWithCoder:] 11 UIFoundation 0x28890 UINibDecoderDecodeObjectForValue 12 UIFoundation 0x28a18 UINibDecoderDecodeObjectForValue 13 UIFoundation 0x28cac -[UINibDecoder decodeObjectForKey:] 14 UIKitCore 0x1e87dc -[NSCoder(UIIBDependencyInjectionInternal) _decodeObjectsWithSourceSegueTemplate:creator:sender:forKey:] 15 UIKitCore 0x1e2ea4 -[UINib instantiateWithOwner:options:] 16 UIKitCore 0x9f96c -[UIViewController loadView] 17 UIKitCore 0x75da8 -[UIViewController loadViewIfRequired] 18 UIKitCore 0x14430 -[UIViewController view] 19 UIKitCore 0x4237bc -[UINavigationController _preferredContentSizeForcingLoad:] 20 UIKitCore 0x116b15c -[_UISheetPresentationMetrics formSheetSizeForViewController:windowSize:screenSize:] 21 UIKitCore 0xb5c60c -[UIViewController _formSheetSizeForWindowWithSize:screenSize:] 22 UIKitCore 0x546ebc -[_UISheetLayoutInfo _preferredSize] 23 UIKitCore 0x18da60 -[_UISheetLayoutInfo _isEdgeAttached] 24 UIKitCore 0x19d428 -[_UISheetLayoutInfo _margins] 25 UIKitCore 0x19ce88 -[_UISheetLayoutInfo _stackAlignmentFrame] 26 UIKitCore 0x211018 -[_UISheetLayoutInfo _fullHeightUntransformedFrame] 27 UIKitCore 0x18f39c -[_UISheetLayoutInfo _untransformedFrame] 28 UIKitCore 0x188350 -[UISheetPresentationController _containerViewLayoutSubviews] 29 UIKitCore 0x18f1fc -[UITransitionView layoutSubviews] 30 UIKitCore 0x26070 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] 31 QuartzCore 0x14c14 CA::Layer::layout_if_needed(CA::Transaction*) 32 UIKitCore 0x16b78 -[UIView(Hierarchy) layoutBelowIfNeeded] 33 UIKitCore 0x186f4c -[UISheetPresentationController presentationTransitionWillBegin] 34 UIKitCore 0x3187b4 -[_UIFormSheetPresentationController presentationTransitionWillBegin] 35 UIKitCore 0x185dd0 __80-[UIPresentationController _initViewHierarchyForPresentationSuperview:inWindow:]_block_invoke 36 UIKitCore 0x1874f8 __77-[UIPresentationController runTransitionForCurrentStateAnimated:handoffData:]_block_invoke_3 37 UIKitCore 0x8584c -[_UIAfterCACommitBlock run] 38 UIKitCore 0x85784 -[_UIAfterCACommitQueue flush] 39 UIKitCore 0xa254 _runAfterCACommitDeferredBlocks 40 UIKitCore 0x9f74 _cleanUpAfterCAFlushAndRunDeferredBlocks 41 UIKitCore 0x9e84 _UIApplicationFlushCATransaction 42 UIKitCore 0x9e0c __setupUpdateSequence_block_invoke_2 43 UIKitCore 0x9404 _UIUpdateSequenceRun 44 UIKitCore 0x8ab4 schedulerStepScheduledMainSection 45 UIKitCore 0x41e4 runloopSourceCallback 46 CoreFoundation 0xfa8c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ 47 CoreFoundation 0xf8a4 __CFRunLoopDoSource0 48 CoreFoundation 0xf700 __CFRunLoopDoSources0 49 CoreFoundation 0x10080 __CFRunLoopRun 50 CoreFoundation 0x11c3c CFRunLoopRunSpecific 51 GraphicsServices 0x1454 GSEventRunModal 52 UIKitCore 0x135274 -[UIApplication _run] 53 UIKitCore 0x100a28 UIApplicationMain 54 Saleslink DEV 0x1f9ea8 main + 17 (AppDelegate.swift:17) 55 ??? 0x1af61bf08 (Missing) Would love to know if anyone else has encountered this, or if there’s an official radar or feedback ID we can follow. Hoping this gets resolved before the GM release of Xcode 26. Thanks!

(I made a mistake and saved too soon. Nothing to see here. Sorry!)

Recurring crash on install of any app with the new sourceVideoTrackProvider.next() dyld[41966]: Symbol not found: _$sSo19AVAssetReaderOutputC12AVFoundationE8ProviderC4nextxSgyYaKFTjTu Referenced from: <79AA2BE0-A6B4-32F5-A804-E84BBE5D1AEA> /Users/<username>/Library/Developer/Xcode/DerivedData/TrackProviderCrash-bbbhjptcxnmfdcackxtpucnunxyc/Build/Products/Debug-maccatalyst/TrackProviderCrash.app/Contents/MacOS/TrackProviderCrash.debug.dylib Expected in: <1B847AF9-7973-3B28-95C2-09E73F6DD50B> /usr/lib/swift/libswiftAVFoundation.dylib Can be reproduced with the current Xcode Beta 4 by running on to MacCatalyst and macOS https://developer.apple.com/documentation/AVFoundation/converting-projected-video-to-apple-projected-media-profile Crash goes away of you comment out lines 154-158 and 164-170 which are while let sampleBuffer = try await sourceVideoTrackProvider.next(){/*other code*/} Can also be reproduced if you add the code below to a MacCatalyst project import AVKit let asset: AVURLAsset = .init(url: Bundle.main.url(forResource: "SomeVideo.mp4", withExtension: nil)!) let videoReader = try! AVAssetReader(asset: asset) let videoTracks = try! await asset.loadTracks(withMediaCharacteristic: .visual) // Get the side-by-side video track. let videoTrack = videoTracks.first! let videoInputTrack = AVAssetReaderTrackOutput(track: videoTrack, outputSettings: nil) let sourceVideoTrackProvider: AVAssetReaderOutput.Provider<CMReadySampleBuffer<CMSampleBuffer.DynamicContent>> = videoReader.outputProvider(for: videoInputTrack) //Comment out this while let sb = try! await sourceVideoTrackProvider.next() { }

I have a new M4 iPad Air and a brand new Apple Pencil Pro. It was working well until I installed iPadOS 26.0 (23A5297m) beta. Now, when using GoodNotes to write the Pencil functions for about 6-8 seconds and then disconnects for 2-3 seconds and then reconnects. You can imagine how disruptive this is. It does the same thing trying to highlight in the Kindle app, so I think it is an iOS issue. As I write this, I am discovering that the Pencil is not wanting to stay connected at all despite showing up in the list of Bluetooth devices and connecting temporarily. I've tried forgetting and reconnecting the Pencil several times. It is charged to 100%, and I receive the alert that the iPad detects the Pencil. Is anyone else having this issue? Do I need to assume this is being addressed?

Not sure if this is the proper place to post this. In quotes below is what I posted on the regular forum but it was removed when I used the word 'beta' - didn't know that was an issue. The email then sent me here. "Updated both my MacBook Pro (M1, Late 2020) and my iPhone 13 Pro with the new Tahoe 26 Public Beta and now my phone number is "unavailable for iMessage and FaceTime" It's listed on the website for sign in to the account, but now messages on my different devices don't sync and I can't send from my number or receive messages in new threads to my number. After an hour or so of digging online I called their support - who didn't know about Tahoe. The best he could tell me is wait 24 hours for the system to catch up. Sigh. It's the same number I've had since (well before) iPhone 2 when I first set up the account. I've been doing the betas since they've been available, and I expect quirks and issues. I've just never had an issue this invasive." Follow up - existing threads still seem to work, I'm assuming I'm missing anyone new texting me, since my number isn't listed

I have been trying to get the drag and drop to work on iOS 26 betas. Single drag is okay, but I thought this year we were getting multi-select drag added. creating a simple object that can be dragged. Using the .draggable and added dropDestination which does trigger. The problem is the dragContainer does nothing. Not really clear what it is supposed to do. How am I supposed to allow for multiple item drag and drop like the Photos app? In there you can start a drag and tap additional photos to add to the drag. I can do this with a UICollectionView, but not with SwiftUI. struct DragObject: Codable, Identifiable, Transferable { var index: Int enum Keys: String, CodingKey { case index } var id:Int { index } public func encode(to encoder: any Encoder) throws { var container = encoder.container(keyedBy: Keys.self) try container.encode(self.index, forKey: .index) } static public var transferRepresentation: some TransferRepresentation { CodableRepresentation(contentType: .json) } } @available(iOS 26.0, *) struct DragDropTestView: View { @State var items : [DragObject] = (0..<100).map({ DragObject(index: $0) }) @State var selected : [DragObject.ID] = [] var body: some View { let _ = Self._printChanges() ScrollView { Text("Selected \(selected)") LazyVGrid(columns: [GridItem(.adaptive(minimum: 150, maximum: 180))], alignment: .center, spacing: 10) { ForEach(items, id: \.index) { item in VStack { Text("\(item.index)") } .frame(width: 100, height: 100) .padding() .background(Color.blue) .cornerRadius(8) .contentShape(.dragPreview, Circle()) .draggable(item) .dropDestination(for: DragObject.self) { draggedItems, session in print("Dragged Item Count: \(draggedItems.count)") } } } } .dragContainer(for: DragObject.self, selection: selected){ ids in dragItems(ids: ids) } } func dragItems(ids: [Int]) -> [DragObject] { return ids.map({ DragObject(index: $0)}) } }

I'm unable to find the right combination modifiers to get drag and drop to work using the new .draggable(containerItemID:) and dragContainer(for:in:selection:_:) modifiers. The drag is initiated with the item's ID, the item is requested from the .dragContainer modifier, but the drop closure is never triggered. Minimal repro: struct Item: Identifiable, Codable, Transferable { var id = UUID() var value: String static var transferRepresentation: some TransferRepresentation { CodableRepresentation(contentType: .tab) } } struct DragDrop: View { @State var items: [Item] = [ Item(value: "Hello"), Item(value: "world"), Item(value: "something"), Item(value: "else") ] var body: some View { List(items) { item in HStack { Text(item.value) Spacer() } .contentShape(Rectangle()) .draggable(containerItemID: item.id) .dropDestination(for: Item.self) { items, session in print("Drop: \(items)") } } .dragContainer(for: Item.self) { itemID in print("Drag: \(itemID)") return items.filter { itemID == $0.id } } } } #Preview("Simple") { DragDrop() }

I'm not seeing the Accessibility or Attributes Inspectors in Xcode 26. Were these features removed? Xcode 16 Xcode 26