Apple Seeds First Betas of iOS 26.1, iPadOS 26.1, and macOS Tahoe 26.1

[MarkR]

Wish I waited to update till 26.1 was pushed. Too many bugs for me on 26 (iPhone 16 Pro Max).

I never upgrade to a new major OS release until at least the .2 version. Apple's software quality control has been horrible over the past several years. I just don't trust them to put out a relatively solid major OS release on the first try anymore.

 

[DiscoMcDisco]

Here’s two for you to try. Alter your Safari settings for tabs to be at the bottom, then try and post in this forum. Bet you’ll find the text in the text box turns light grey and very difficult to read.

Second, are the up/down arrows on this forum in a consistent place or do they float around like they’re filled with helium?

Yeah, not sure what you’re on about.

Even switching dark mode is fine.

No weirdness for me at all, I mean, maybe the audio icon and extensions clashing perhaps…

 

[Jay Bly]

Will be interesting. I have not had any issues on my 17.

 

[mikamika83]

Erm, am I the only person who has barely had a single problem with any 26 beta from day 1? You all moan about stuff I have literally never seen and i’m a dev/test specialist.

I almost want to get all your steps to reproduce and see if I just missed them or simply don’t get the problem

Iterate, refine, improve… moaning about shiny edges (which are frankly lovely) while I’m out here wanting UI Scaling that goes with text size cos why should i have a button thats near on full screen with the smallest text choice… for 16 years…

> re: i’m a dev/test specialist.

Let me give you a specific problem to test, mr. test specialist.

Step 1: Open VSCode
Step 2: Open Activity Monitor
Step 3: Make sure the `GPU %` column is visible, add it to columns if hidden.
Step 4: Sort by `GPU %`, make sure the process `WindowServer` is visible (should be first in the list)
Step 5: Scroll the VSCode editor, observe the GPU% go to 50%+ for the `WindowServer` process

Now, mr dev/test specialist, try working a full day with scrolling in vscode and observe your laptop get to space heater temperatures, fans kicking in.

M1 Max btw

 

[jbuccino]

My MBP M4 stalled during boot after the upgrade. Removing Little Snitch 6.3.1 seems to have solved the issue.

 

[Pooneil]

Today, I learned the word “alacrity”. Thanks!

Mister Spock used alacrity in a Star Trek episode when I was growing up when the Star Ship Enterprise was in another tight spot. Television wasn’t quite as dumbed down as today.

 

[DiscoMcDisco]

> re: i’m a dev/test specialist.

Let me give you a specific problem to test, mr. test specialist.

Step 1: Open VSCode
Step 2: Open Activity Monitor
Step 3: Make sure the `GPU %` column is visible, add it to columns if hidden.
Step 4: Scroll the VSCode editor, observe the GPU% go to 50%+

Now, mr dev/test specialist, try working a full day with scrolling in vscode and observe your laptop get to space heater temperatures, fans kicking in.

M1 Max btw

Wow, love a challenge but don’t have VSCode, I use VSpro or Xcode, on a non-Max M1 MacBook Pro …

So,

1. Can’t cover your requirements
2. Don’t know what else your system is doing or running
3. Love you picked something literally on the edges of any standard user. Does it do the same in other software or just Microsoft software?

If you can send me to a service that’s running an image of your machine in the cloud or something, or provide me a full set of system diagnostics, apps installed etc etc then I’d gladly have a go.

Also, VERY Glad you like to challenge what people say though, that’s a honourable trait. You can happily look me up on LinkedIn if you like, Russ Watson-Thomas. Have at it, if it makes you feel better knowing I’m not a 13 year old being all high and mighty and has actually worked in software dev for 20 years… or get back in your box, whichever you prefer

Cheers!!

 

[gleepskip]

> re: i’m a dev/test specialist.

Let me give you a specific problem to test, mr. test specialist.

Step 1: Open VSCode
Step 2: Open Activity Monitor
Step 3: Make sure the `GPU %` column is visible, add it to columns if hidden.
Step 4: Sort by `GPU %`, make sure the process `WindowServer` is visible (should be first in the list)
Step 5: Scroll the VSCode editor, observe the GPU% go to 50%+ for the `WindowServer` process

Now, mr dev/test specialist, try working a full day with scrolling in vscode and observe your laptop get to space heater temperatures, fans kicking in.

M1 Max btw

How did you definitively determine the GPU usage in Tahoe is an OS issue and not a Microsoft issue?

 

[DiscoMcDisco]

How did you definitively determine the GPU usage in Tahoe is an OS issue and not a Microsoft issue?

I’ve already fed the troll, you don’t have to but appreciate it

 

[JoeSilver]

Just give me the option to disable all the Liquid Glass nonsense and I’ll be happy. This isn’t a huge ask.
Just give us a toggle in the Display control panel, Apple. It’s ok for people giving you money to not be 100% onboard with your “bold new vision.”

Not sure if you're serious, but in case, Liquid Glass is not a theme which can be just disabled or changed. It's an entire UI fully integrated within the OS.

 

[PatrikCoC]

> re: i’m a dev/test specialist.

Let me give you a specific problem to test, mr. test specialist.

Step 1: Open VSCode
Step 2: Open Activity Monitor
Step 3: Make sure the `GPU %` column is visible, add it to columns if hidden.
Step 4: Sort by `GPU %`, make sure the process `WindowServer` is visible (should be first in the list)
Step 5: Scroll the VSCode editor, observe the GPU% go to 50%+ for the `WindowServer` process

Now, mr dev/test specialist, try working a full day with scrolling in vscode and observe your laptop get to space heater temperatures, fans kicking in.

M1 Max btw

While we wait for Apple to stop vibe coding, you can use this command to fix the high GPU usage:

sed -i '' 's/experimentalDarkMode:!0}/experimentalDarkMode:!0,hasShadow:false}/g' /Applications/Visual\ Studio\ Code.app/Contents/Resources/app/out/main.js

This disables the window shadow for VS Code that causes this bug.
There is also an autofill bug that causes 100% CPU usage and input lag, you can fix it by using this command:

defaults write -g NSAutoFillHeuristicControllerEnabled -bool false

 

[iHorseHead]

I wonder if Apple Intelligence is gaining Turkish and other languages’s support with this new update.

I hope not.

 

[PatrikCoC]

How did you definitively determine the GPU usage in Tahoe is an OS issue and not a Microsoft issue?

It's caused by window shadows for all Electron-based apps and some more.

 

[scouser75]

Here’s two for you to try. Alter your Safari settings for tabs to be at the bottom, then try and post in this forum. Bet you’ll find the text in the text box turns light grey and very difficult to read.

Second, are the up/down arrows on this forum in a consistent place or do they float around like they’re filled with helium?

I second this. And it’s not just this forum. It happens randomly on other forums too. But hoping this is fixed in this update.

 

[Brighton Apple Guy]

Please contain a ton of bug fixes and optimization, especially scrolling animation performance in safari and lists like mail and apple music. its so jittery and stuttery on 15 pro.

Safari 26 is an abomination when you use the Liquid Glass URL bars on the bottom- not complaining though, made a nice little earner fixing peoples sites thanks to Apple busting a ton of CSS stuff.

It's broken so many sites, including major ones.

 

[mikamika83]

Wow, love a challenge but don’t have VSCode, I use VSpro or Xcode, on a non-Max M1 MacBook Pro …

So,

1. Can’t cover your requirements
2. Don’t know what else your system is doing or running
3. Love you picked something literally on the edges of any standard user. Does it do the same in other software or just Microsoft software?

If you can send me to a service that’s running an image of your machine in the cloud or something, or provide me a full set of system diagnostics, apps installed etc etc then I’d gladly have a go.

Also, VERY Glad you like to challenge what people say though, that’s a honourable trait. You can happily look me up on LinkedIn if you like, Russ Watson-Thomas. Have at it, if it makes you feel better knowing I’m not a 13 year old being all high and mighty and has actually worked in software dev for 20 years… or get back in your box, whichever you prefer

Cheers!!

>re: Love you picked something literally on the edges of any standard user.

You said you were a developer, i assumed you use vscode, which is used by, don't quote me on this, 99.9% of developers on Mac? Aside from mac-native devs who only use xcode

 

[DiscoMcDisco]

I second this. And it’s not just this forum. It happens randomly on other forums too. But hoping this is fixed in this update.

TBF, I usually have Safari defaulted to 75% for all sites… it’s always seemed cleaner/more stable to me that way… other than the even more over zealous form field zooming (that I still can’t turn off, after 12 years moaning about that one lol)

 

[switz]

Moved most of my Apple gear to the release 26 series software after the beta developer cycle. Have had no need for a fire hose to put out any fires.

I will wait now to see if any issues develop at this level. No hurry to create problems.

 

[DiscoMcDisco]

>re: Love you picked something literally on the edges of any standard user.

You said you were a developer, i assumed you use vscode, which is used by, don't quote me on this, 99.9% of developers on Mac? Aside from mac-native devs who only use xcode

Found something to pick at? nice.

I said Dev/Test Specialist, not developer… but that’s nitpicking right?

I’ve always preferred a native UI, and other than being forced by almost every company I’ve worked at to use VSpro (because lots of monoliths are still Microsoft houses) I generally refrain from using anything MS on MacOS because… the whole MS ecosystem is vile.

VSCode doesn’t suck, but the only reason I installed it was to check on copilot integrations (openAI, Claude, GitHub copilot etc) for seeing the state of play across a number of apps. It wasn’t good, it didn’t stay.

I think your 99.9% probably includes a lot of indie, which is also fine, but I’m not indie.

 

[srknpower]

I hope not.

Why? And it is gaining Turkish support with iOS 26.1

 

[mikamika83]

I’ve always preferred a native UI, and other than being forced by almost every company I’ve worked at to use VSpro (because lots of monoliths are still Microsoft houses) I generally refrain from using anything MS on MacOS because… the whole MS ecosystem is vile.

I understand you think I'm a troll and wasting your time, but I assure you that bug is real and is affecting a lot of people's daily productivity.

The only reason I got a bit upset and made the earlier comment is — it perplexed me to no end that a test specialist is echoing the good old "it works on my machine, why is everyone whining so much?" (you said moaning, your words not mine)

I don't doubt your credibility, but it's quite confusing.

 

[helloapple1]

I never upgrade to a new major OS release until at least the .2 version. Apple's software quality control has been horrible over the past several years. I just don't trust them to put out a relatively solid major OS release on the first try anymore.

Good decision. I put too much faith into Apple sometimes.

 

[thetotalitaria]

Can someone confirm whether this and the iTunes Store app are fixed?

 

[DiscoMcDisco]

I understand you think I'm a troll and wasting your time, but I assure you that bug is real and is affecting a lot of people's daily productivity.

The only reason I got a bit upset and made the earlier comment is — it perplexed me to no end that a test specialist is echoing the good old "it works on my machine, why is everyone whining so much?" (you said moaning, your words not mine)

I don't doubt your credibility, but it's quite confusing.

Oh what, the feature not a bug stuff… yeah ok, I get that… but at the same time, I hammer this daily driver running betas and it’s one of the only times it genuinely perplexes me… maybe I’m also just to old and disgruntled to stick to the old rhetoric

 

[Corpuscle]

> re: i’m a dev/test specialist.

Let me give you a specific problem to test, mr. test specialist.

Step 1: Open VSCode
Step 2: Open Activity Monitor
Step 3: Make sure the `GPU %` column is visible, add it to columns if hidden.
Step 4: Sort by `GPU %`, make sure the process `WindowServer` is visible (should be first in the list)
Step 5: Scroll the VSCode editor, observe the GPU% go to 50%+ for the `WindowServer` process

Now, mr dev/test specialist, try working a full day with scrolling in vscode and observe your laptop get to space heater temperatures, fans kicking in.

M1 Max btw

Nice attitude. NOT! Sounds so childish.

And how do you know these issues aren't related to the bugs in the program and not with Apple software/hardware?