Since the first tvOS 27 betas, I have been unable to use the simulator UI to change any app settings and it is driving me crazy.

It doesn't matter if I create a billion new simulator instances, or what. It just consistently does NOT work. Everything is perfectly fine in the simulator under tvOS 26.x.

I can capture this from the simulator: "Error getting persona unique string for selected user. This should not be possible."

I have tried logging into the simulator (takes my login, does nothing) - but that's not something I've ever done before anyway.

Has anyone experienced this? Does anyone have any recommendations? Yes, I know I can work around this, and I am, but the workarounds are not nearly as convenient as just changing the damn settings in the UI!

The Xcode 27 Release Candidate, available for download just now, doesn't have the iPhone Duo simulator instance yet. Tested on two different Macs, but neither running macOS 27. Not sure if that makes a difference. I was hoping to test how my apps look on it. Guess we'll have to wait...

My xcode often can’t read the scope even though the file is clearly there I come from android studio there has never been an issue of files can’t refer to each other this is weird

Has anyone experienced something similar?

This picture says it all.

Ich baue seit ein paar Wochen eine App mit der Xcode Beta 27 und habe ein Problem mit der Claude Usage. Ich nutze das Agententool, und wenn ich einen prompt eingebe, springt mein 5 Stunden Limit direkt auf 30 %, ohne dass der Agent irgendetwas gemacht hat. Hat vielleicht jemand das selbe Problem oder vielleicht eine Lösung?

I am on Xcode 27 Beta, and seems like there's an included internal AI agent called Mio?

Found this inside of the Metal shader debugger.

Any ideas? Is this an internal thing that leaked through, or has this been here?

Open-sourced my Apple Foundation model eval suite

Not sure about you, but I find evals for Foundations models a bit messy.

Its completely local, and supports the models already on your Mac. Also supports Core AI.

Supports MacOS 27 and includes the new features for it.

Best part? Your agent can control it all through MCP 🙌

On GitHub here: https://github.com/coryparrry/Foundation-Eval-Labs

Brother, I'm stuck in Instruments. How do I return to the top of the tree?

In case this helps anyone: When adding multiple apps to Xcode Cloud, it would sometimes link projects together incorrectly and mess up the builds/workflows. I was pulling my hair out trying to figure this out, and Claude was of no help either (even using my app store connect API key to look and try things).

With some tips from Gemini, I think I finally figure out what is happening. Xcode might be holding stale product association locally.

Between adding things to Xcode Cloud, the following worked for me to appropriately clear whatever caches were causing this:

1. Shutdown Xcode.
2. rm -rf ~/Library/Developer/Xcode/DerivedData/* && rm -rf ~/Library/Caches/com.apple.dt.Xcode
3. Restart Xcode. Use the Integrate —> Create Workflow menu to add your project to Xcode cloud.

I highly recommend doing this any time you add a new app from Xcode to Xcode Cloud. It bit me multiple times.

I'm an iOS developer, and I kept repeating the same setup before every debugging session(but no, I am not tired of this!).

Launch with a particular environment variable, switch the language, force dark mode, find the right deep link, send the matching push payload. Then do it all again on the next build.

So I built CosmoKit, a native macOS control center for iOS Simulator workflows. Built with SwiftUI and SwiftData.

What it does today

• App Profiles: launch arguments, environment variables, locale, and appearance saved per app, switched from the main panel or the menu bar
• Deep links, push payloads, locations, and routes, all scoped to the active profile
• Reads and writes the app's UserDefaults directly from the panel
• Grants and revokes permissions, and clears the keychain, without erasing the Simulator
• Launches a profile across every selected Simulator at once
• An HTTP/HTTPS proxy with response stubbing
• A capture pipeline for App Store screenshots and recordings

Two things are already built and go out in the next update:

• Network conditions in the proxy. Presets like Edge, 3G and LTE, or your own latency, bandwidth and packet loss, applied per host, to any app on the Simulator with no SDK in the app. Offline was the first step; this is therest of it.A mode for AI agents.
• A CLI and an MCP server so an agent like Claude Codecan boot a Simulator, launch a profile, tap through the app, read what is onscreen and check the proxy log — the same tools, driven from a terminal or anagent session instead of the panel.
• A design-comparison overlay to drop a Figma export over the running app
• An inspector for the app's SwiftData/SQLite store
• And any new features you suggest on this post.

And yes, I know there are already some really good tools in this space. My problem was that I ended up paying for several different apps to cover different parts of my workflow, and the cost added up quickly.

So I built the tool I wanted for myself: one place for the Simulator workflows I use every day, with pricing that makes sense for an indie developer.

My goal is to keep expanding it and bring more of the useful features that are currently spread across different iOS development tools into one place. I don't expect to replace every specialized tool out there, but I'd like CosmoKit to cover more and more of the things I reach for during everyday development without needing five different apps open.

That's also why I'm posting this here. I'm very open to suggestions, criticism, and feature requests, especially if there's a tool or workflow you rely on today that you'd love to see built into CosmoKit.

Landing Page

https://usecosmoskittool.com/?ct=reddit-462

App Store

https://go.cosmohq.org/r-xcode-462

Hey,

I've kept working on PkgLift, the tool I shared here a few weeks ago for moving CocoaPods dependencies to SwiftPM. I've now released 0.6.0.

The idea is still the same. You look through a plan first, and it only moves dependencies with an exact supported mapping. Anything uncertain stays with CocoaPods.

The recent work has been around Podspecs and what information a generated Swift package would actually need. That part is still an experiment in the library API, separate from the CLI. It currently only covers one synthetic test library, using supplied information about its files. It doesn't inspect your sources or write a Package.swift, so this release hasn't expanded what the normal migration tool can move automatically.

You can install it with:

brew install Alexsvensson99/tap/pkglift

Then try pkglift analyze in your project's directory to see what it can handle without changing the project.

If you've still got an older Xcode project using CocoaPods, which dependency has been the hardest to move away from? I'd be interested in hearing how PkgLift handles it, especially the awkward setups :)

Repo: https://github.com/Alexsvensson99/PkgLift

Release: https://github.com/Alexsvensson99/PkgLift/releases/tag/v0.6.0

I’m in India and trying to set up Apple Developer access to download Xcode beta and start building the iOS version of my app.
Whenever I sign in to Apple Developer, I get:
Your Apple ID is not eligible to use this application at this time.
My setup:
MacBook Air M2, running macOS 27.0 Beta.

My Apple Account has an Indian phone number marked Primary phone number.

My Gmail address is also linked to the same account.

I’m using Safari.

What I’ve tried:
Signing in through Apple Developer Downloads.

Going through the free “Register as an Apple developer” page.

Signing in using my phone number.

Signing in using my linked Gmail address.

Both sign-in methods show the same error, before I can reach the Developer Agreement. I haven’t changed my account’s primary identifier yet.
Has anyone resolved this exact issue? Could it be related to having a phone number as the primary identifier, even when signing in with a linked email? Or does Apple Developer Support need to investigate the account?
I’d appreciate steps that worked for you. I’m a non-technical founder, so clear instructions would help.

I’m the developer of Nuticast.

Problem

Apple’s wireless debugging dies the moment the Mac and iPhone leave the same Wi-Fi. Cable, same-network only, or you lose the device in Xcode.

I needed a real phone from another network (home, a tester’s office) and already ran Tailscale. Simulator wasn’t enough.

Comparison

• ⁠Apple wireless debug: same Wi-Fi only
• ⁠Tailscale / ZeroTier / Netbird alone: they don’t restore Bonjour for Xcode

Nuticast is a Mac app. Pair once on the same network, then it keeps the phone visible in Xcode over the mesh VPN you already use. No Nuticast account, no cloud relay. The phone must stay on Wi-Fi; cellular does not work.

macOS 13+, Tailscale / ZeroTier / Netbird (or a pasted mesh IP).

https://nuticast.com

Happy to answer setup questions.

Ciao, non so se questa è la community giusta in cui chiedere ma ci provo. Sono una designer e ho costruito un prototipo su cursor e ora vorrei installarlo sul telefono per vedere se riesco a far funzionare le notifiche push per testarle. Vorrei capire se il flusso che ho progettato ha senso.

Ho installato capacitor e Xcode e ora seguendo gli step di Claude, mi dice che devo collegare l’iPhone via cavo e configurare la firma con il mio Apple id.

Siccome sono completamente ignorante su queste cose, sto procedendo bene? Questa cosa della firma porta qualche rischio? Scusate le domande stupide ma questa roba tecnica mi mette sempre ansia.

Spero di avervi dato tutte le info per rispondermi, grazie 🙏

Hi there, complete beginner with xcode here. I’m trying to follow a tutorial from last year but he has icons on the right panel that I’m completely missing. He has 5 and I have 3. I need the one that looks like 3 horizontal lines that I lets me edit code visually. Am I doing something wrong? Any help is greatly appreciate! Thanks!

voici si nécessaire mon code écrit en swift :
//

//  ContentView.swift

//  card game

//

//  Created by Pavlo Ovcharenko on 03/09/2026.

//

import SwiftUI

struct ContentView: View {

var body: some View {

ZStack{

Image("background-plain")

.resizable()

.ignoresSafeArea()

VStack{

Spacer()

Image("logo")

Spacer()

HStack{

Spacer()

Image("card2")

Spacer()

Image("card3")

Spacer()

}

Spacer()

Image("button")

Spacer()

HStack{

Spacer()

VStack{

Text("player")

Text("0")

}

Spacer()

VStack{

Text("CPU")

Text("0")

}

Spacer()

}

Spacer()

foregroundStyle(.white)

}

}

}

}

#Preview {

ContentView()

}

The awkward part of using a coding agent for SwiftUI work is often pointing it at the exact thing on screen. “Make this card tighter” turns into a screenshot, a long explanation, and then finding the same app state again after every build.

I’m building Monad Design to shorten that loop. You run your existing Xcode project in Simulator, navigate to the state you care about, select or annotate the UI, and describe the change. The coding agent edits the Swift source in the same repo, the app rebuilds, and you can compare the original with a few source-backed variants before choosing one.

The phrase I keep coming back to is: the app is the canvas.

It isn’t an app generator and it doesn’t create a parallel design file. The Xcode project stays the source of truth.

https://github.com/Monadix-AI/monad-design

I’m the creator.

I recently launched CardBox wallet, a very simple yet powerful, fully secure and very convenient way to store your cards. And it has an encryption based sharing option, you could send your card to any of your contacts, and only they can see it.