Since updating my MacBook Air to macOS Tahoe 26.0 Developer Beta 2, I’ve encountered a persistent cursor misalignment issue:
When interacting with lists or contextual menus, the cursor’s visual position does not align with what it actually selects.
The system registers the cursor slightly above where it appears, causing clicks to select the wrong option or fail to register.
As a temporary workaround, I can sometimes position the cursor off-target and press Enter to select, but this is a frustrating and inefficient workaround.
The issue persists after a restart and appears across multiple areas of the OS:
Right-clicking an app in the Dock to open the contextual menu → cursor highlights an incorrect item relative to its position.
In System Settings menus.
Even on the Feedback Assistant site when selecting issue categories.
Steps to Reproduce:
1️⃣ Update to macOS Tahoe 26.0 Developer Beta 2 on MacBook Air.
2️⃣ Right-click on any open application in the Dock.
3️⃣ Attempt to select an option from the list that appears.
4️⃣ Observe that the cursor highlights or interacts with a different option than where the cursor is visibly located.
Notes:
Issue is consistent across reboots.
Affects workflow and general navigation.
Temporary workaround using keyboard navigation is insufficient for productivity.
FB Number: FB18531124
If others are seeing this as well, please confirm below so Apple can prioritize investigation.
Posts under Beta tag
200 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
I am writing to report multiple issues encountered after updating to Xcode 26 Beta, which have significantly impacted my project's compilation and functionality. My project can run normally in Xcode16.3 version, Below are the specific problems, along with the steps I took to address them and the subsequent errors that arose:
Symbol Not Found Error for _NSUserActivityTypeBrowsingWeb
After updating to Xcode 26 Beta, my project failed to build with the error: "Symbol not found: _NSUserActivityTypeBrowsingWeb." To resolve this, I removed the MobileCoreServices framework from the Build Settings, as it appeared to be related. However, this led to a new error, indicating that this change introduced further complications.
Clang++ Error: No Such File or Directory 'OpenGLES'
Following the resolution of the first issue, I encountered a new error: "iOS clang++: error: no such file or directory: 'OpenGLES'." To address this, I added the OpenGLES.framework to the Build Phases. While this resolved the clang++ error, it triggered additional errors, suggesting that the underlying issue persists or new dependencies are conflicting.
Recurring XIB File Compilation Errors
My project uses XIB files, and every time I attempt to compile and run, Xcode reports errors related to different XIB files. Notably, when I open the reported XIB file, no errors are displayed within the Interface Builder. After saving or inspecting the file, the compilation error temporarily disappears, only for another XIB file to trigger the same issue in the next build. This creates a repetitive cycle. I have confirmed this is not a caching issue, as I clean the build cache (Product > Clean Build Folder) before each run. If I skip cleaning the cache, the OpenGLES-related error (Issue 2) reappears, indicating potential interactions between these problems.
These issues have made development with Xcode 26 Beta extremely challenging, as each attempted fix seems to introduce new errors, and the XIB issue creates a persistent loop. My setup includes:
Xcode Version: 26.0 beta 2 (17A5241o)
macOS Version:15.4.1 (24E263)
App Name: Endless Zombies
Platform: iOS
Genre: Roguelike / Survival / Action
TestFlight Link: https://testflight.apple.com/join/DEIN-CODE
Status: Open Beta – limited seats available
🎮 What is Endless Zombies?
Endless Zombies is a fast-paced, top-down roguelike shooter where you must survive increasingly intense zombie waves — with fully separated movement and aiming controls for maximum precision and tactical depth.
Players can upgrade their weapons, unleash special attacks, and face progressively stronger threats including Baby Waves (fast mini-zombies) and Boss Battles against giant elite enemies with unique behavior.
This is not just about survival — climb the global leaderboard and fight your way to the top!
🏆 Compete for high scores, dominate the kill count, and earn bragging rights (and potential rewards in future tournaments).
Endless Zombies is currently in its first public beta and we’re looking for players who want to help us improve mechanics, test new systems, and shape the final experience.
🧪 Looking for beta testers to:
Test gameplay fluidity and aiming responsiveness
Evaluate performance on different iOS devices
Provide feedback on UI, game balance, and spawn pacing
Report bugs and edge-case issues
🚀 Features:
🎯 Dual control movement + aiming
🧠 Smarter, optimized enemy spawn logic
⚔️ Upgradeable weapons and energy system
👥 Online friends chat and leaderboard system (PlayFab-based)
📊 Stats, progress tracking, and UI improvements
Join via TestFlight:
👉 https://testflight.apple.com/join/DEIN-CODE
We’d love to hear what you think!
Summary
When using .tabViewBottomAccessory in SwiftUI and conditionally rendering it based on the selected tab, the app crashes with a NSInternalInconsistencyException related to _bottomAccessory.displayStyle.
Steps to Reproduce
Create a SwiftUI TabView using a @SceneStorage selectedTab binding.
Render a .tabViewBottomAccessory with conditional visibility tied to selectedTab == .storage.
Switch between tabs.
Return to the tab that conditionally shows the accessory (e.g., “Storage”).
Expected Behavior
SwiftUI should correctly add, remove, or show/hide the bottom accessory view without crashing.
Actual Behavior
The app crashes with the following error:
Environment
iOS version: iOS 26 seed 2 (23A5276f)
Xcode: 26
Swift: 6.2
Device: iPhone 12 Pro
I have opened a bug report with the FB number: FB18479195
Code Sample
import SwiftUI
struct ContentView: View {
enum TabContent: String {
case storage
case recipe
case profile
case addItem
}
@SceneStorage("selectedTab") private var selectedTab: TabContent = .storage
var body: some View {
TabView(selection: $selectedTab) {
Tab(
"Storage", systemImage: "refrigerator", value: TabContent.storage
) {
StorageView()
}
Tab(
"Cook", systemImage: "frying.pan", value: TabContent.recipe
) {
RecipeView()
}
Tab(
"Profile", systemImage: "person", value: TabContent.profile
) {
ProfileView()
}
}
.tabBarMinimizeBehavior(.onScrollDown)
.tabViewBottomAccessory {
if selectedTab == .storage {
Button(action: {
}) {
Label("Add Item", systemImage: "plus")
}
}
}
}
}
Verbatim of a feedback report (FB18431713) I submitted, duplicated here since we can't see each other's feedbacks, and I wanted a centralized place to track the resolution of this as I'm surely not the only one facing this.
When building the app using Xcode 26 beta 2 and running it in an iOS 26 simulator, I'm experiencing a retain cycle in the UINavigationController.
From the data I saw in Xcode's memory graph debugger, it seems that _UIViewControllerOneToOneTransitionContext is retaining it. I base this on the fact that the line connecting a view controller and _UIViewControllerOneToOneTransitionContext has a "strong" reference, as indicated in Xcode. (However, I'm reporting this as a retain cycle in UINavigationController, as that's what seems to hold onto this transition-context.)
After installing iOS 26 Developer Beta on my iPhone 13 mini, I encountered a critical battery issue. The battery percentage was stuck at 1%, and the phone could only be used while continuously plugged in.
Despite the low reading, the device remained fully functional — I could use apps, navigate, and perform tasks normally. However, the battery indicator never rose above 1%, and the Battery Health section in Settings showed 0% Maximum Capacity, which is inaccurate.
I did not allow the phone to fully discharge, out of fear that it might not turn back on. Restarting the phone and changing cables or chargers had no effect. After restoring the device to iOS 18.7.2 using DFU mode, the issue disappeared entirely — the battery percentage behaved normally again and the health section showed the correct value (about 100%).
Observed behavior:
• Battery percentage frozen at 1%
• Maximum Capacity reported as 0%
• Device only functional while connected to power
• Issue resolved immediately after restoring to iOS 18
Temporary solution:
A DFU restore to iOS 18 (18.5 22F76) immediately resolved the issue. The battery percentage and health readings returned to normal.
Additional information:
• Charger used: Official Apple 20W USB-C charger
• Cable used: Apple USB-C to Lightning cable
• Battery health after restore: 100% (replaced)
For example:
I have a list of to-dos, each with a unique id (a GUID). I want to feed them to the LLM model and have the model rewrite the items so they start with an action verb.
I'd like to get them back and identify which rewritten item corresponds to which original item. I obviously can't compare the text, as it has changed.
I've tried passing the original GUIDs in with each to-do, but the extra GUID characters pollutes the input and confuses the model.
I've tried numbering them in order and adding an originalSortOrder field to my generable type, but it doesn't work reliably.
Any suggestions?
I could do them one at a time, but I also have a use case where I'm asking for them to be organized in sections, and while I've instructed the model not to rename anything, it still happens. It's just all very nondeterministic.
After IOS 26 beta 2 installation in my iphone 13, I can't do a screenshot using assistivetouch nor touch on back.
Calling button flickers when making a call after updating to ios 26 beta 2 kindly solve the issue asap
I've tried
deleting and reinstalling the beta
deleting and re-adding the iOS support
deleting and re-adding all the simulators
clearing DerivedData and CoreSimulator/Caches
rebooting
waiting a little while and rebuilding
Nothing works. Anyone else had any success?
I've got the initial WWDC beta of macOS 26 (25A5279m) installed inside a virtual machine (UTM), but can't seem to update to the second beta. Nothing is showing up within Software Update.
Is this because it's within a VM, or am I doing something wrong?
It'd be a real pain to have to install a new VM afresh with the RestoreImage for every update.
Cannot Install Tahoe Beta 2 because Software Update Dialogue Box will not accept my Password (None in my case). Reports: "User interaction required" Recommendations?
Why is "generate comment" button grayed out?
I'm running macOS Tahoe Beta 2, Xcode 26 Beta 2
Apple intelligence on both system preferences as well as Xcode are enabled
Created fresh Xcode project to test it (happens on my older project too)
Xcode Preferences -> Editing -> Automatically generate string catalog comments (tried with ON/OFF)
Tried to CMD+B to re-index project
Not sure what else to try.
Hi,
I'm trying to create a custom bottom toolbar for my app and want to use same fade-blur effect as iOS uses under navigation and tab bars. Having trouble doing that.
Here is what I tried:
Screenshot 1: putting my custom view in a toolbar/ToolBarItem(placement: .bottomBar). This works only in NavigationStack, and it adds a glass pane that I do not want (I want to put a custom component there that already has correct glass pane)
Screenshot 2: using safeAreaBar or safeAreaInset in any combination with NavigationStack and/or .scrollEdgeEffectStyle(.soft, for: .bottom). Shows my component correctly, but does not use fade-blur.
Can you please help me to find out the correct way of doing that? Thanks!
^ Screenshot 1
^ Screenshot 2
Test code:
struct ContentView2: View {
var body: some View {
NavigationStack {
ScrollView(.vertical) {
VStack {
Color.red.frame(height: 500)
Color.green.frame(height: 500)
}
}
.ignoresSafeArea()
.toolbar() {
ToolbarItem(placement: .bottomBar) {
HStack {
Text("bottom")
Spacer()
Text("text content")
}
.bold().padding()
.glassEffect().padding(.horizontal)
}
}
}
}
}
While testing my application on iOS beta 26, I am experiencing issues with the native UISegmentedControl component from UIKit. After implementing the control, I noticed that I am unable to switch to the second segment option—the selection remains fixed on the first segment regardless of user interaction. I have already reviewed the initial configuration of the control, the addition of the segments, and the implementation of the target-action, but the issue persists. I would like to understand what could be causing this behavior and if there are any specific adjustments or workarounds for iOS 26.
I created a minimal application containing only a UISegmentedControl to clearly demonstrate the issue.
I can see that iOS beta 2 was released yesterday. I'm not running the beta yet on my actual iPhone, but I wanted to see if an issue I reported in beta 1 was fixed.
Is there a way to update my iOS 26 simulator for beta 2? Usually, there's a new Xcode download that includes the new simulator, but it looks like the most recent Xcode beta release was June 9.
Updated iPhone to 26 beta 2, everything is ok but battery, battery is changed, not original. My phone can't charge higher than 1% and turns off every 5 minutes, even connecting to wireless charger and cable at the same time don't work, restored iPhone thru iTunes.I hope I will be able to install new beta without any problems because loving the new design, hoping for the best. Thanks.
My FB-FB18327769
Updated iPhone to 26 beta 2, everything is ok but battery, battery is changed, not original. My phone can't charge higher than 1% and turns off every 5 minutes, even connecting to wireless charger and cable at the same time don't work, restored iPhone thru iTunes.I hope I will be able to install new beta without any problems because loving the new design,hoping for the best. Thanks.
I'm trying to update to BETA 2 but my mac mini does not see the update and keeps telling me that my machine is up to date.
How do I get the latest BETA 2?
.navigationTitle disappears when using .toolbar and List inside NavigationStack (iOS 26 beta)
Summary
In iOS 26 beta, using .navigationTitle() inside a NavigationStack fails to render the title when combined with a .toolbar and a List. The title initially appears as expected after launch, but disappears after a second state transition triggered by a button press. This regression does not occur in iOS 18.
Steps to Reproduce
Use the SwiftUI code sample below (see viewmodel and Reload button for state transitions).
Run the app on an iOS 26 simulator (e.g., iPhone 16).
On launch, the view starts in .loading state (shows a ProgressView).
After 1 second, it transitions to .loaded and displays the title correctly.
Tap the Reload button — this sets the state back to .loading, then switches it to .loaded again after 1 second.
❌ After this second transition to .loaded, the navigation title disappears and does not return.
Actual Behavior
The navigation title displays correctly after the initial launch transition from .loading → .loaded.
However, after tapping the “Reload” button and transitioning .loading → .loaded a second time, the title no longer appears.
This suggests a SwiftUI rendering/layout invalidation issue during state-driven view diffing involving .toolbar and List.
Expected Behavior
The navigation title “Loaded Data” should appear and remain visible every time the view is in .loaded state.
✅ GitHub Gist including Screen Recording
👉 View Gist with full details
Sample Code
import SwiftUI
struct ContentView: View {
private let vm = viewmodel()
var body: some View {
NavigationStack {
VStack {
switch vm.state {
case .loading:
ProgressView("Loading...")
case .loaded:
List {
ItemList()
}
Button("Reload") {
vm.state = .loading
DispatchQueue.main.asyncAfter(deadline: .now() + 1) {
vm.state = .loaded
}
}
.navigationTitle("Loaded Data")
}
}
.toolbar {
ToolbarItem(placement: .navigationBarTrailing) {
Menu {
Text("hello")
} label: {
Image(systemName: "gearshape.fill")
}
}
}
}
}
}
struct ItemList: View {
var body: some View {
Text("Item 1")
Text("Item 2")
Text("Item 3")
}
}
@MainActor
@Observable
class viewmodel {
enum State {
case loading
case loaded
}
var state: State = .loading
init() {
DispatchQueue.main.asyncAfter(deadline: .now() + 1) {
self.state = .loaded
}
}
}