build disappears

Please file a Feedback report using Feedback Assistant, then post the number here. Be sure to include links to failing builds in the report.

I uploaded the requested IORegistryExplorer files. I also note a couple of other things: every time I re-attach the device, I get a new driver process and a new IOUserServer at the root of the IORegistry. Even if I delete the app the existing driver process keeps running, unless I kill it from Activity Monitor. Maybe there's something I'm not cleaning up properly, but I don't know what. when I eject the disk, there is a very perceptible delay between ejecting the volume and its associated - Data container. I use Finder/Settings and check the External Disks item in the Sidebar/Locations list. After I click the eject control next to the volume, I unplug the device as soon as it disappears from the sidebar, and very often see a notification about ejecting volume - data when it wasn't ready to be ejected. If I keep /Volumes open I can see that Volume's icon disappears first, then Volume - Data's icon. Is this a bug worth filing?

The issue was between my ears and not related to the app building or app store distribution. I did run the app locally from a ZIP (same for my friend with the M3 MacBook) and it had installed a bunch of settings under ~/Library and ~/Library/Preferences and this somehow conflicted with the App Store installation. I deleted all this and then could install from the App Store without issues. All good now, thanks! ER!K

Dual booting (triple in my case - 14/15/26) is not a viable option for Xcode development and testing of an app because different versions of macOS support different versions of Xcode. While Xcode 26.0.1 currently runs on macOS 26 and macOS 15.6, it certainly can't be run on macOS 14 and I can easily see a time in the near future where some version of Xcode 26.x requires macOS 26. Dual/triple booting does sound like a way to at least be able to run Test Flight so I can at least do my own verification of functionality before pushing the test build to beta testers. In my specific case, my app is not a game. It's a productivity app. My primary testing concern is ensuring the UI works correctly under different versions of macOS (and iOS for that matter). Being able to do this with VMs would make things SO much easier. One copy of Xcode on the host. One copy of the source code on the host. One build on the host. Then run that one binary (stored on the host) in the different VMs. It would be just l

Short update - the linked article did help me successfully build a kext collection for the kernel on my local M2 system. I had to do minor adjustments to the instructions in that article to get it working. I have been trying to boot my M2 using this kext collection (after kmutil configure-boot ... successfully completed), but so far that step hasn't worked. Every time the system tries to boot with this custom built kext collection (in Permissive mode), the Apple icon shows up for a few seconds and then system shutdown and then again the Apple icon shows up and this keeps continuing. I switched back to Restrictive mode to allow me to boot the regular kernel, but I'll experiment some more and see how I can debug/investigate what's preventing a successful boot - it's going to be challenging because I can't seem to locate any logs for this part of the boot process.

The issue got resolved by removing the 'Icon Files' and 'Icon names' empty entry under 'Icon Files' key in info plist. We used this earlier for supporting alternate app icons. This empty entry caused the issue when submit app build from latest 26 xcode

[quote='860281022, RickMaddy, /thread/787500?answerId=860281022#860281022, /profile/RickMaddy'] where does this all stand? [/quote] For a summary of the current state of the issues being discussed in this thread, see my 27 Aug 2025 reply. However, your questions extend beyond that, so let’s dig in. [quote='860281022, RickMaddy, /thread/787500?answerId=860281022#860281022, /profile/RickMaddy'] is there any viable way for a solo developer with one Mac to develop and test a macOS app that runs on more than one version of macOS? [/quote] Yes. As marco.masser suggested, you can boot your Mac into older versions of macOS and test there. I want to stress that, while VMs are super useful, they are not a substitute for testing on real hardware [1]. VMs have limits: Some are bugs, as we’ve been discussing on this thread. Some of them are absent features. Of these, the lack of TestFlight support is the most critical. I’ll come back to that below. Some of them are just fundamental to VMs. For example, if you’re building

In other words, is there any viable way for a solo developer with one Mac to develop and test a macOS app that runs on more than one version of macOS? You can always install another OS on a separate volume and boot from that for building and/or testing.