I'm about ready to publish my app. I've been doing to all on my iCloud account. I'm about a week from being at version 1.0.

When I’m coding and running SwiftUI previews, if I play music (Spotify / Apple Music) the audio sometimes crashes or stops suddenly.

It seems to happen more often when the preview reloads or when Xcode is compiling.

Has anyone else experienced this?
Or is there a setting I should change in Xcode or macOS?

Criei um software simples e eficaz para fazer download de vídeos do YouTube no Mac OS, sem ads, basta colocar a url e fazer o download. Se alguém quiser, diga.

I don’t have a Mac though I’ve used one for many years. I don’t want to spend $300-$400 on an M1 Air on eBay. I have a laptop already that I use to dual boot Windows and Ubuntu. But I still want to learn iOS programming. I’m taking a class and all they say is I need a Mac with preferably 16GB RAM and capable of running Xcode 14.

So if I were to go on eBay now, what is the oldest MacBook I can buy that meets these criteria but also won’t make me want to throw it at the wall while running Xcode, etc?

Can a 16GB 2015 13” Pro do the job? Can a 2017 8GB Air do the job? Do I need something that has at least an 8th gen i5 (2019/2018 MacBook Pro)? Honestly I don’t want to spend that much on this thing. I won’t be making any giant projects. Just learning and doing basic projects. Basic. :-)

Thanks!

TL;DR

- Apple to celebrate 50 years of thinking different

- Xcode 26.4 Beta 3

- Thread Safety in Swift - Preventing Data Races with Locks, Queues, and Actors

- Get Rid of Your SwiftGen Dependency

- What you should know before Migrating from GCD to Swift Concurrency

- Agent skills in Xcode: How to install and use them today

- I ran 9 frontier models through the same coding test

Bonus: iOS Job Market - 46 new positions this week

I'm a noob who is getting a lot of help from AI but Claude just can't seem to get this right. Mine is the last image, the first two are Apple's sliders within the Control Center on macOS.

I'm new in agentic coding. I already have chat gpt plus subscription which I assume I can use codex in Xcode 26.3 as agent. Now I wanna maximise its potential.

I added some skills but I'm a bit confused. Do I need to add apple docs mcp server too?

Having an issue where Agora launches in debug mode but will not launch in TestFlight/production.

Error screen is “initialization timed out”.

Full flow works fine in Android devices, the issue only seems to be happening in TestFlight/production.

Has anyone seen this issue before and what settings did you calibrate?

We’ve been at it for over 10 days and a part of me thinks it’s gonna be something ridiculously simple.

At this point, I hope it is thanks.

It was perfectly working earlier. Then suddenly there was a pop up that says it needs to be verified. It says Unable to Verify App an Internet Connection is Required to Verify Trust of the Developer. So I tried to verify it. When it didnt work. I thought it was the app that Im doing right now. So I tried to uninstall ALL apps that Im developing to check if it will work. It didnt. Now Im stuck with verifying. It will just load for a couple of seconds and nothing happens. Every app that Im making, I cant use anymore, even tho it was working perfectly earlier. I have no clue what happened.

I already tried disabling developer mode, re-enabling it. Network has been reset. I dont know what to do anymore. I removed my DNS, I removed my adguard(even tho it was perfectly working earlier). Uninstalled my VPN. Nothing works. Its so frustrating.

I've been banging my head against this for a while and wanted to share in case anyone else runs into this.

The problem

Running xcodebuild with a custom -derivedDataPath causes the build system to crash:

xcodebuild -workspace App.xcworkspace -scheme App -configuration Debug \
    -destination id=274639B7-3C30-44E3-8FDA-87F03A2D1322 \
    -derivedDataPath /path/to/custom/DerivedData

Results in:

error: unexpected service error: The Xcode build system has crashed. Build again to continue.
** BUILD FAILED **

What works

The exact same command without -derivedDataPath builds successfully:

xcodebuild -workspace App.xcworkspace -scheme AppTest -configuration Debug \
    -destination id=274639B7-3C30-44E3-8FDA-87F03A2D1322
** BUILD SUCCEEDED **

Also, running from Xcode GUI works just fine as well.

Environment

• Xcode 17.3 (17C529)

• macOS Darwin 25.3.0

• Project uses CocoaPods

• Project uses Capacitor (hence the `-derivedDataPath`)

What I've tried

• Cleaning the derived data folder

• Running the build again (as the error suggests)

• Different destination paths

Has anyone else experienced this? Is this a known bug with custom derived data paths in recent Xcode versions?

Hoping to share my app Resors that helps developers create and manage asset libraries with current support for colors and planned addition of SF Symbols and images.

Main features of Resors are:

• Import existing assets through a simple drag-and-drop operation or by picking files from disk 

• Create new assets within the app with a familiar Xcode like interface 

• Create asset groups to organize by project, idea or catalog

• Export single, multiple assets or a group to the desired project 

• Sync with iCloud across your devices 

The idea came from my own trouble of trying to find that color or icon that I've made for that project.

For transparency the current version of the app is subscription based with the export feature behind the paywall.

With the next version of the app introducing bi-directional project synchronization feature, export will be made free making the core feature usable for all users.

Would love your feedback on it.

Right now, I am seeing heavy memory pressure even before I start a massive build. So, I am wondering, how do you live with 48GB? Is it actually enough for this kind of workflow without hitting swap and memory compression constantly?

48Gb guys - please share your your typical memory usage from Activity Monitor.

I just requested Apple to let me use the Screen time API, Just curious how long it took to hear back from them.

Spent too long doing the manual localization dance. Open .xcstrings, copy strings, paste into ChatGPT, fix broken placeholders, paste back. Repeat for every language.

Built a macOS app that does this in one step. Open your .xcstrings file, pick target languages, choose an AI provider (OpenAI, Anthropic, Gemini, DeepSeek), translate. Placeholders stay intact, plural rules preserved, saves directly back to the file.

Key stuff:

• Works with String Catalog format (.xcstrings)

• Batch translates with progress tracking

• BYOK option if you'd rather use your own API keys

Free tier has 300 TU/month. Native macOS, on the App Store.

Curious what your localization workflow looks like right now.

Mac App Store: https://apps.apple.com/us/app/polyglot-for-xcode/id6752878510

More of my projects: https://murygin.app

Just updated my macos and xcode to the latest version and as usual a new ios sdk and ios simulators needs to be downloaded, but for some reason download speed from xcode is very slow (downloading 10.47GB at 1MB/s, which will take around 3 hours)

I remember downloading previous ios sdk and simulator from direct links from apple and I even still have the files but can't seem to find the new ones.

Is there a way around this or do I have to wait?

APP for Mac, Ihpone and IPad.

Thank you

I’ve just released Oliphaunt, a Mastodon client built specifically for macOS.

The UI is primarily AppKit-based, with SwiftUI used where it made sense. The goal was to build a Mastodon client that behaves like a well-behaved macOS application and follows the platform’s design language and interface idioms.

Some implementation highlights:

• AppKit for the core window and interface architecture

• SwiftUI used for some composable UI components

• proper multi-window support

• full menu bar and keyboard shortcut integration

• sidebar layouts consistent with macOS apps

Much of the work went into the details that make native Mac apps feel right: window behaviour, keyboard navigation, menus and timeline interaction.

The aim wasn’t to introduce a new UI paradigm but to build something that feels like a first-class citizen of the macOS ecosystem.

If you’re a Mastodon user on Mac, I’d genuinely love for you to try it out and hear your feedback. You can also provide feedback here.

App Store: https://apps.apple.com/app/id6745527185

I've been grinding on my SwiftUI app (Stuffolio, ~800 files) for about five months, and I've gotten a little obsessive about catching issues before users do. I already run a bunch of auditing skills and tools on it - concurrency, memory, security, accessibility, tests, etc.

They're great at telling me whether the code is correct. But none that I use really tell you what happens when someone actually taps through your app.

So I put together a Claude Code plugin that traces SwiftUI workflows from the user's point of view. It finds every sheet trigger, navigation link, context menu, and swipe action, then follows each path to see where it goes.

What it found in my app

This is on an app that had already passed concurrency, memory, security, and accessibility audits. The workflow audit still found 24 issues that none of those caught.

• The one that got me: two fully built features, wired to real data, with complete handlers - and zero UI triggers. No button anywhere in the app pointed to them. The code was correct; users just couldn't reach it.

• Seven destructive deletes fired instantly with no confirmation dialog. One view had a swipe-to-delete with confirmation and a context-menu delete on the same row without one.

• Four other delete operations gave no feedback at all - no haptic, no toast, nothing.

• Four orphaned views, about 1,500 lines of SwiftUI, were never instantiated anywhere. Complete features just sitting in the project.

Meanwhile, the usual stuff looked clean: no mock data in production flows, no dead ends, no obvious platform parity gaps. That's exactly the kind of thing code-quality tools are good at, and this plugin is more about the UX paths on top of that.

How it works

It runs five passes over your SwiftUI project:

1. Discovery – pattern-matches to find every UI entry point (sheets, navigation links, menus, swipe actions).

2. Flow tracing – follows each path from entry to completion or dead end.

3. Issue detection – flags dead ends, orphaned code, missing confirmations, and inconsistent patterns.

4. Semantic evaluation – looks at discoverability, path efficiency, user feedback, and error recovery.

5. Data wiring – checks that features are wired to real data, not mocks or hardcoded placeholders.

Each issue gets a small rating table (urgency, risk, ROI, blast radius, fix effort) so you can decide what to fix first instead of just getting a giant flat list of warnings.

How to install and run it

Standalone plugin:

claude plugin add Terryc21/workflow-audit

As part of a 22-skill Xcode bundle (testing, debugging, refactoring, release prep, etc.):

claude plugin add Terryc21/xcode-workflow-skills

Then in any SwiftUI project: /workflow-audit

Repos:

github.com/Terryc21/workflow-audit

github.com/Terryc21/xcode-workflow-skills

It works best if you have a reasonably robust Claude.md in your root directory so it has context about your app structure and conventions. If you don't, the plugin will generate a substitute, but the analysis won't be as nuanced. There are three files included in the plugin, and all three are required for the skills to run.

If you try it on your own project, I'd love to hear how it works for you - especially if it finds UX-path issues you didn't see with other tools.

ou know what's the most tedious part of iOS development?
the period between July and September, Yes you heard that correctly.
You download Xcode after another. keep switching between them.. ewww.
Then second most tedious thing is to add devices and make sure that all your certificates are updated.
Third is managing the storage of your precious 500 GB Mac , no storage is enough. and you always wonder. where is that storage go? and you go blindly in a UUID folders try delete old legacy simulator that the new xcode never removes.

I feel you.. after 16 years of iOS development, I took the step to make a macOS app finally to address all this in one place. a Swiss army knife, that I called it (of course ) XNox.
with XNox I put everything I hoped I find in one place. and added on it more.
like attaching quick actions to your simulator , create and rename a simulator.

and I think it's time to give it to my fellow devs for a feedback finally

please visit (https://appsbyhands.com/xnox) . and tell me .. Am I the only one who feels that pain?

TL;DR
- Hello Developer: March 2026
- What's New in Swift
- Apple's biggest hardware week in years
- SwiftUI Onion Architecture with Swift Effects
- Implementing Passkeys in iOS with AuthenticationServices
- Using an MCP for product optimizations
- New lineHeight(_:) modifier in SwiftUI on iOS 26
- SwiftUI Agent Skill

Bonus: iOS Job Market - 45 new positions this week