Title: High CPU usage by WindowServer during Twitch playback on M4 Pro (macOS 26 Tahoe) Description: After upgrading to macOS 26 (Tahoe), I’ve noticed that Twitch playback in both Safari and Microsoft Edge causes WindowServer to consume 40–50% CPU on a MacBook Pro with the M4 Pro chip. This results in noticeable fan noise and reduced battery life, even when only one 1080p stream is active. This behavior was not present in the previous version of macOS. Steps to reproduce: Open Twitch in Safari or Edge. Play any live stream at 720p or 1080p. Observe Activity Monitor – WindowServer process hits 45%+ CPU consistently. Expected: Hardware video decoding and efficient GPU-based composition should prevent CPU overload. Actual: WindowServer consumes high CPU, fans activate Hardware: MacBook Pro 14” (M4 Pro, 2025), macOS 26.0 (Tahoe)

Hello, I found an issue with the Games app on macOS 26 (Tahoe) when viewing achievements: In App Store Connect, each achievement has different values set for the pre-earned description and the post-earned description. When testing with GameKit directly (GKAchievementDescription), both values are returned correctly. However, in the macOS Games app, the post-earned description is shown even before the achievement is earned. This seems to be a display issue specific to the Games app on macOS. Could you confirm if this is a known bug in the Games app, or if there is a reason why pre-earned descriptions are not being shown? Thank you.

since the release of iOS26 i get new reports of people making home screen apps of website pages that had camera accessibility to take pictures that mention the camera being 90degree sideways to what it should be. i have tested it myself and was able to reproduce the issue quite easily on iPhones 13|15|16 regular and pro versions. this affects all cameras when trying using them with navigator.mediaDevices.getUserMedia({...})...

Hello, My experience is limited but I am looking to connect with app developer who has experience so I may receive mentorship. Thank you for taking the time to read this : ) Zakariah J. McLeroy

With macOS Tahoe, Launchpad has been replaced by an App Library–style mode within Spotlight. While the alleged intention is UX consistency across the Apple ecosystem, the result is both a catastrophic usability regression and a radical break in consistency with iOS and iPadOS. Predefined App Library categorization is functionally incoherent: On iOS and now macOS, Apple’s predefined App Library categories place apps with seemingly identical functionality into unrelated groups—for example, 3D scanning tools scattered across Education, Utilities, and Productivity. Instead of making apps easier to find, this effectively creates a labyrinth that users must traverse to locate apps whose names and icons they may not recall. However Apple defines its app categories, they are not only inconsistent but also hopelessly inadequate for the long tail of real-world applications and user workflows. Loss of user control: Launchpad enabled users to group and organize applications according to their workflows. This aligns with Apple’s own Human Interface Guidelines, which emphasize user control, discoverability, and predictable behavior. The new Spotlight interface removes that flexibility, locking users into predefined categories that both impede and mislead—and cannot be overridden. Consistency across platforms is broken: If the goal was to unify iOS, iPadOS, and macOS, this approach actually undermines consistency. On iOS and iPadOS, users can still rely on a customizable Home Screen—a Launchpad-like experience—as their primary way of launching apps. In Tahoe, that option has been removed. macOS now forces users to depend exclusively on Spotlight with App Library categories, while eliminating the very feature that was consistent across platforms. Catastrophic impact on my workflow: As an interdisciplinary artist working in 2D, 3D, and time-based media, as well as coding, I make extensive use of a constantly changing array of AI tools and experiment with many new apps and web services, which I often turn into Web Apps. I cannot possibly recall the names of every native and web app on my system. I need predictable access to groups of related tools. Tahoe’s new auto-categories split those apps apart arbitrarily, slowing me down and interrupting established workflows, forcing me to navigate the aforementioned labyrinth just to find what I need. Proposal: A constructive way forward High-level objective: Simply restore Launchpad—or restore the ability to customize app categories/folders and manually assign apps to them, overriding or augmenting the predefined categories. This ensures users can launch apps according to their workflow, without needing to remember exact names or icons. Possible solutions: Allow manual subfolders within Applications, represented hierarchically in Spotlight. Provide a fullscreen Launchpad-like organizer (with uninstall via long-click, etc.), either as a replacement or toggleable option. Retain Apple’s auto-categories for those who prefer them, but let users override or augment them with their own. In summary: Tahoe eliminates a working, consistent paradigm (Launchpad/Home Screen) and forces reliance on an App Library system that categorizes poorly and cannot be customized. This is both a step backwards in functionality and a break in cross-platform consistency. A constructive solution is to restore Launchpad—or at least restore the ability for users to organize apps in ways that fit their workflows.

Hi, I want to understand how Per-App VPN can be configured on iOS. Specifically: Is Per-App VPN something that can be controlled directly from code (inside an app), or does it always require MDM / configuration profiles (.mobileconfig)? If it requires a configuration profile, how can I specify which apps (by bundle identifier) should use the VPN? Is it possible to let users dynamically choose apps for Per-App VPN, or is this strictly managed by MDM? My goal is to make sure that only apps selected by user dynamically use the VPN connection, while other apps continue to use the normal network. Any official Apple documentation, examples, or guidance would be greatly appreciated.

I started monitoring using the following code: deviceActivityCenter.startMonitoring( DeviceActivityName(name), during: makeDailySchedule(), events: events ) Where: DeviceActivitySchedule( intervalStart: DateComponents(hour: 0, minute: 0), intervalEnd: DateComponents(hour: 23, minute: 59), repeats: true, warningTime: nil ) In DeviceActivityMonitor, I read and write data using UserDefaults and keep the logic minimal to ensure the size does not exceed 6MB. However, after a period of time, monitoring continues to fail. Why is this happening? How can I resolve this issue?

I have a strange problem. My code works perfectly on my iPhone, i.e. on a real iPhone, but when I upload the build version to TestFlight, it no longer works. I use React Native. The issue is as follows: I have created a code for Grid View that runs automatically when another person joins the stream. It works locally without any problems, but unfortunately the public version does not work. What could be the reason for this?

Hi, I found a Bug in new Preview App on MacOS 26 release, while adding a new calendar entry. If I click on a date inside a PDF file in Preview App, the calendar view pops and prompts to add a new calendar event. The background, which I guess should show the calendar, is showing a yellow screen. See images below. This happens on both my M1 Air and M4 Pro Macbook. Kind regards, Lorenz

After updating iOS 26beta1, it has been a software update error. Can you give me some suggestions to solve the problem?

I have an iPhone 14 Pro, after downloading and installing the new iOS 26, I can’t make any calls, it instantly says “Call Failed”, my cellular data is also not working, however I can still receive calls. This bug needs to be fixed ASAP…

I have base model M4 mini on Mac OS 26 which keeps removing the docked application launcher. I keep adding it back which works till the next incremental update and it's been removed again. The ONLY way I can stop this from happening is to create an alias to the folder and to add that to the dock. I have 3 devices on the 26 Dev beta and the other 2 do not suffer this issue. I was expecting the release candidate to have resolved this but alas it hasn't.

Like I said, Xcode always selects the most recently used device for debugging, but when that device disconnects from the Mac, Xcode takes a long time to load and you can’t dismiss it. What a stupid feature! Has anyone encountered the same issue and found a way to resolve it? Thank you very much!

Hi! Short time lurker, and first time poster, but I will try to be as descriptive as possible. I have had my HomePod mini since 2021, and have been loving it. Recently, though, I am facing issues which have paralyzed it. Background: Running two HomePod Minis under a stereo pair on the same network in a room. Devices worked well, with the odd dropping of the sound once a while, not too big of an issue. Started running HomePod OS26 beta in July to see what the new updates have, and maybe if the audio issues would be resolved. Issue: Two weeks ago, the after the (then) latest update, there was a no response issue in the app. No big deal, let's just restart the HomePod pair. After restart, no bueno. I also got a new beta software update notification, so decided if I updated them both, the issue will probably be resolved. No dice. The issue persists. So I decided to pair the HomePods and factory reset them. Both HomePods disappeared from my home app. Regular behavior. Going to reset them with the old unplug for 30 s, replug into power, hold finger on the display had no issues for the first one. For the second HomePod, unplug, hold, and plug in. Problems. No display. Tried it a bunch of times, nothing. Waited a day, in case the capacitors needed to be discharged for it to do a cold boot. Nothing. Looking across the interwebs, I found that we can connect the HomePods to Macs, have them show up on Finder, and update from there. Connecting into the Mac, nothing. Waited for the caps to discharge before engaging again, nothing. Now, I fear I may have problems. So I scheduled a meeting at the Genius Bar. Genius Bar individual said no support as you are running beta software. We are not allowed to touch or diagnose those devices. They also said that there are no external facing endpoints for us to diagnose or check. I would have better luck with online Apple Support or over call with Apple Support. Okay, sounds good. Contacting Apple Support, they said that we will have to wait for the official release of HomePodOS 26 for us to support you, to which I agreed. During this time, I thought about seeing if I could troubleshoot and see if anything was coming out of the HomePod when connected to the Mac. So I wrote a script, querying and logging different aspects of the USB controller on the Mac and seeing what device connects. I removed all other USB devices connected to the Mac, and started the script. First, I connected and disconnected the HomePod a couple of times, and on the last connect, I left it in, and let the script record the readings. Reading the output told me that there was indeed a device that was connecting and disconnecting. Here are some of my findings: Port Readout Summary Apple's UVDM stack lights up on the Port-USB-C@2 (CC path, SOP) AppleUVDM driver tried to read identity VDOs, initially rejected, then carried on and the transport finished powering on successfully. Furthermore, the VDM read attempts itself are rejected, typical when the accessory is gating Apple specific commands The CC transport merged metadata for SOP with a 3-VDO identity set. The CC property change during the run indicates an active PD negotiations. USB link states also toggled on that port with driver status Ready Port-USB-C@2/SOP shows Vendor ID and Product ID (not sure if this is private information, so not sharing) Port-USB-C@1/SOP, the e-marker in the HomePod cable shows the same, with product type "Passive Cable" Only CC is flagged "TransportsActive" Apple's accessory authentication stack is present The USB speeds on the port flicker between Gen 3 and Gen 2, indicating to me some sort of handshake failing in the stack, which is preventing enumeration in the System Report and Finder This likely is indicating to me that the target isn't enumerating as a normal USB device, but rather as a USB-PD Vendor Defined Messaging (UVDM) protocol on the CC line. Furthermore, the signature is in a "hidden" service/update modes, which does not enumerate standard USB functions. So, having all this information available to me, I got on a call with Apple Support today, and they went through some of the troubleshooting steps and told me that they could neither escalate the issue (due to it being on a beta software that THEY DO NOT SUPPORT) nor remediate or troubleshoot the issue (as it is an accessory) and the only thing their support options say is to wipe the device, as it is something that is not supported. Upon my suggestion of this my USB logs being used to review the case, they said my personal USB logs would be detrimental towards my case. Their final recommendation was for me to reach out to Apple Developer support as I am running beta software on this HomePod Mini. So, here I am! I highly believe this is a Software issue, contrary to what Apple Consumer Support call representative indicated. All and any help/guidance and support is appreciated. All and any help in boosting the visibility of this issue on the forums would also be greatly appreciated. I have had these bad boys since my undergrad, and I would hate to lose one of them. For Apple Support, before you lock and close this post down and recommend I go to Apple Consumer Support, they said that they cannot help me, and consumer support steps start and end at resetting the device.

A while ago i installed iOS 26 beta 2 on my iPhone 12 mini with an unrecognised battery, and after updating, the battery percentage was stuck at 1%. so I tired different things, but never worked if not downgrading to iOS 18, now iOS 26 is out and i don't know if it now safe to update. i don't have the time now to troubleshoot so if someone can help me or tell me if this bug is fixed

After my phone updated to the latest version of iOS 26 Beta overnight, I found out this morning that I cannot get past the setup process as it fails to recognise it's connected to the WiFi and is then unable to activate Apple Intelligence. I've tried bypassing this via iPhone mirroring on my MacBook, and while I can access the home screen that way, all native apps are inaccessible and 3rd party apps are only accessible via app switcher. The 3rd party apps (Slack, Instagram, etc) work fine, meaning the device has an internet connection. Unless someone has another suggestion, it looks like my only option is to remove the beta software by restoring my device - although I'm going to wait until iOS 26 is fully released later today (how convenient) as I don't want to use an iOS 18 backup and lose a bunch of stuff.

Apple did not allow this post on regular forums due to iOS 26 usage, sent me there to post Previously, you were able to manage gifts that you send to other people (i.e. gift cards) via App Store app - there was a "Gifts" button in the App Store, where you could resend the gift if it did not arrive. Now, on iOS 26, this button is not available anymore in the app. It's just not there. On my Macbook that currently runs Sequoia, this button is available in the App Store app, but clicking it returns "Cannot connect to App Store". Did Apple remove that functionality? Because I can't even submit a ticket on Apple Support to file a claim about undelivered gift. Gift sending itself works as usual, I managed to send a new gift right after that.

My iPhone is on iOS 26 RC and when I tried adding music to my library, the app crashed and when I opened it again my whole Apple Music library including playlists disappeared but it still shows that the app is showing 8 gb of storage. I’ve tried restarting my phone, closed the app and reopened it, and that didn’t work, what do I do

I have a FORD F250 2021. I returned for a deployment, and CarPlay does not work in my vehicle. I have tried all the YouTube, TikTok, Facebook, and Instagram videos I could find. They all actually started to repeat, so I decided to come here. My wife has an iPhone 16 Pro Max, and it connects to CarPlay without any issues. Other than all the social media suggestions, do you have any other suggestions? No, I am not ready to purchase a new device.

Hi, my fusion drive is not recognized with the latest tahoe developer beta. is it official or it's a bug ? it works when I reboot into previous verion of macOS. APFS Containers (6 found) | +-- Container disk3 AD9B43A5-66E7-4696-8183-8FD75230DAD2 | ==================================================== | APFS Container Reference: disk3 | Size (Capacity Ceiling): 994662584320 B (994.7 GB) | Capacity In Use By Volumes: 899491840000 B (899.5 GB) (90.4% used) | Capacity Not Allocated: 95170744320 B (95.2 GB) (9.6% free) | | | +-< Physical Store disk0s2 8183A70B-64A7-434E-85A4-5FA40F692BC9 | | ----------------------------------------------------------- | | APFS Physical Store Disk: disk0s2 | | Size: 994662584320 B (994.7 GB) | | | +-> Volume disk3s1 295CC2B7-EFA6-4706-8A6F-4C8FDC455857 | | --------------------------------------------------- | | APFS Volume Disk (Role): disk3s1 (System) | | Name: Macintosh HD (Case-insensitive) | | Mount Point: Not Mounted | | Capacity Consumed: 12576616448 B (12.6 GB) | | Sealed: Yes | | FileVault: Yes (Unlocked) | | Encrypted: No | | | | | Snapshot: 9B660F16-30C2-4B5E-911A-5B6250626C0C | | Snapshot Disk: disk3s1s1 | | Snapshot Mount Point: / | | Snapshot Sealed: Yes | | | +-> Volume disk3s2 766CF320-F93A-42D0-9660-F48E5B6C3B1A | | --------------------------------------------------- | | APFS Volume Disk (Role): disk3s2 (Preboot) | | Name: Preboot (Case-insensitive) | | Mount Point: /System/Volumes/Preboot | | Capacity Consumed: 7744360448 B (7.7 GB) | | Sealed: No | | FileVault: No | | | +-> Volume disk3s3 2A8ABBAC-435B-493E-A1AE-2DCCE5966207 | | --------------------------------------------------- | | APFS Volume Disk (Role): disk3s3 (Recovery) | | Name: Recovery (Case-insensitive) | | Mount Point: Not Mounted | | Capacity Consumed: 1165090816 B (1.2 GB) | | Sealed: No | | FileVault: No | | | +-> Volume disk3s5 5339AAF8-3765-458A-AB1F-930AFD53CAA3 | | --------------------------------------------------- | | APFS Volume Disk (Role): disk3s5 (Data) | | Name: Macintosh HD - Data (Case-insensitive) | | Mount Point: /System/Volumes/Data | | Capacity Consumed: 875640164352 B (875.6 GB) | | Sealed: No | | FileVault: Yes (Unlocked) | | | +-> Volume disk3s6 99818862-6CC2-4805-9C96-5837D666543F | --------------------------------------------------- | APFS Volume Disk (Role): disk3s6 (VM) | Name: VM (Case-insensitive) | Mount Point: /System/Volumes/VM | Capacity Consumed: 2147524608 B (2.1 GB) | Sealed: No | FileVault: No | +-- Container ERROR -69808 | ====================== | APFS Container Reference: disk5 | Size (Capacity Ceiling): ERROR -69620 | Capacity In Use By Volumes: ERROR -69620 | Capacity Not Allocated: ERROR -69620 | | | +-< Physical Store disk4 (No UUID) | | ------------------------------ | | APFS Physical Store Disk: disk4 | | Size: 3200631791616 B (3.2 TB) | | | +-> No Volumes | +-- Container disk7 B400D344-9D63-4168-BA45-3883D02FF515 | ==================================================== | APFS Container Reference: disk7 | Size (Capacity Ceiling): 499793244160 B (499.8 GB) | Capacity In Use By Volumes: 40511234048 B (40.5 GB) (8.1% used) | Capacity Not Allocated: 459282010112 B (459.3 GB) (91.9% free) | | | +-< Physical Store disk6s2 9458DABF-09A9-4A8A-A5A1-EF5B0FBD82FC | | ----------------------------------------------------------- | | APFS Physical Store Disk: disk6s2 | | Size: 499793244160 B (499.8 GB) | | | +-> Volume disk7s1 2F2C63B5-69D1-4F8E-B720-1B72B743E752 | --------------------------------------------------- | APFS Volume Disk (Role): disk7s1 (No specific role) | Name: Icy (Case-insensitive) | Mount Point: /Volumes/Icy | Capacity Consumed: 40350416896 B (40.4 GB) | Sealed: No | FileVault: No | +-- Container ERROR -69808 ====================== APFS Container Reference: disk9 Size (Capacity Ceiling): ERROR -69620 Capacity In Use By Volumes: ERROR -69620 Capacity Not Allocated: ERROR -69620 | +-< Physical Store disk8 (No UUID) | ------------------------------ | APFS Physical Store Disk: disk8 | Size: 22000969973760 B (22.0 TB) | +-> No Volumes