Anyone noticed #Playgrounds issue with Xcode 26 beta 4?

Developer Tools & Services Xcode
localadmin
localadmin OP
Created Jul ’25
Replies 4
Boosts 5
Views 319
Participants 3

I'm getting following message when launching #Playgrounds canvas with Xcode 26 beta 4.

Here are things I've tried:

  • Reinstall Xcode
  • Reinstall components
  • Removed derived data
  • Run Disk Utility to fix permissions
  • Tried to change Default Actor Isolation, Approachable Concurrency
  • Changed around settings on Schemes: Run: Options and Diagnostics
  • Created brand new project with default settings.

Filed FB19003005 in Feedback Assistant.

I'm surprised to see that I didn't see any posts on this during my search. So this could be isolated matter just to me.

Answered by localadmin in 850534022

Here's my finding:

  • It works when I put #Preview {} before the #Playground {}.
  • Been shaky though. If I still see it, I can remove derived data and restart the Xcode. Works most of the time.

Not sure if this is acceptable, but this is the life of bleeding edge beta. Hopefully next version can be better.

Replies  4
Boosts  5
Views  319
Participants  3
localadmin
localadmin OP
Jul ’25

Additional FYI:

  • I was going to re-image the OS, but noticed that Beta 3 works fine. (That means it's not the OS issue, right?)
  • Currently using beta 3, but keeping on a lookout for any similar issues from others. So far, none.
  • I'm using MacBook Air M3 with 24GB RAM.
1
theonlyone
theonlyone OP
Jul ’25

Just wanted to chime in and say I'm having the exact same problem with a MacBook M1, Seqouia 15.5, 64GB ram.

I haven't tried Beta 3 so I can't confirm whether that'll fix it.

--

Update: That was an an old Vision OS project (Vision 26). If I create a brand new iOS 26 project, playgrounds seem to work properly.

0
localadmin
localadmin OP
Jul ’25
Accepted Answer

Here's my finding:

  • It works when I put #Preview {} before the #Playground {}.
  • Been shaky though. If I still see it, I can remove derived data and restart the Xcode. Works most of the time.

Not sure if this is acceptable, but this is the life of bleeding edge beta. Hopefully next version can be better.

1
citizen7
citizen7 OP
Jul ’25

I observed the same problem with Xcode 26 beta 4, it was ok with beta 3. The problem occurs whether running Xcode 26 beta 4 on macOS 15 or macOS 26 beta 4.

Fortunately the solution I found is simple enough - adding "import SwiftUI" seems to resolve the issue for me.

5
Anyone noticed #Playgrounds issue with Xcode 26 beta 4?
First post date Last post date
 
 
Q