I'm running into this issue now, too. I disabled SIP and manually edited the TCC.db, removing all trace of my app's bundle ID (since tccutil said it couldn't find it), and it still shows up in System Settings -> Privacy & Security -> Accessibility. Double entries for each of two old apps. It must also be recorded somewhere else. Apple needs to be much more transparent about how this stuff works.

I'm trying to use Combine on macOS to get notified of change to app group UserDefaults when made from another process. I've had no end of trouble doing this. There are half a dozen guides online for how to do this in Swift, and I got it working within a single process (with the caveat that the change dictionary always has nil values). But making a change from another process (e.g. with defaults write) does not result in my KVO or Combine sub getting called (both do get the initial value). Now, I'm calling .observe() and .publisher(for:) on my UserDefaults object. Apple’s example for block-based KVO calls observe() on self. where self is an NSObject observer subclass, and it observes a key path through its reference to the object with the changing property. Does that matter? I decided to try DistributedNotificationCenter. It also does not fire when another process sends a notification.

What solved it for me (on Xcode 15, not sure if this works on earlier versions) was to set the shown destinations. I'm not really sure why this option exists.

Still happens in Xcode 15b6

This answer fixed it for me: https://stackoverflow.com/a/75602571/251914

To reiterate, there is a pressing need to be able to install beta macOS versions for development and testing. Ideally, there would be complete integration with Xcode, allowing me to write in, say 13.4, targeting 14(b1), Run, have it launch in the 14 VM, and connect the debugger. It's the only practical way to develop for unreleased macOS versions. iOS has the simulator. But macOS has either dual-booting, or buying a second Mac. Neither is practical. I'd be okay with it being a special VM built into Xcode, and not something that would work on Parallels, for example, although I'm sure that restricts a lot of other use cases. @eskimo, is there a way to build my macOS app locally and then copy it over to a VM to at least try to run it?

I don't have any, despite trying to create them manually on the portal or implicitly via Xcode.

Ah, sorry I wasn't clear before. Yes, the LLC is an Organization, and I am the account holder (I created this account), as shown in the Membership Details:

Confusingly, Xcode shows both a "Personal Team" and a team for my LLC. I always use the LLC, and I have only one login in the developer portal/app store connect. Both of these attempts were using my LLC team.

I created a brand new Multiplatform project. Built and ran it for macOS, then Archived it. Tried same steps as above to export it: Archive, Distribute App: Developer ID -> Export -> Automatically Manage Signing -> FAIL I get the same failure: Communication with Apple failed You are not allowed to perform this operation. Please check with one of your Team Admins, or, if you need further assistance, please contact Apple Developer Program Support. https://developer.apple.com/support No signing certificate "Developer ID Application" found No "Developer ID Application" signing certificate matching team ID "" with a private key was found.

Still fails, unfortunately.

I just ran into this problem, a year later. I'd happily let Xcode handle this, but it fails.

Oh I'm quite aware that the sample code isn't intended to be a "real" application; I only used it to test the approach, and to see if it was any better than Parallels at the same task (it is, because I was able to directly create the VM from the the beta image). In fact, it was very exciting to have so much functionality in sample code. What's lacking is Parallels' VM. It doesn't share the clipboard, and doesn't allow dragging and dropping of files between the host and guest Finders, something that does work for the other guest OSes like Windows. What is lacking in the macOS virtualization framework is documentation. It's not clear, for example, how one would change the display configuration of a running VM (e.g. in response to a VM window size change), or how to set up the shared clipboard, or what a "memory balloon" device is. I've already filed a bug about not being able to log into iCloud, which has also been reported on this forum by many others. FB12006346 Looking at the Console, it definitely seems to be a self-signing issue. So I go to sign my app, but I can't. I don't know why, but I get errors saying it couldn't communicate with Apple, which seems unlikely, and that no provisioning profile for my app was found. But it's supposed to be managing that automatically. THIS IS TOO HARD.

@eskimo Enhancement request: FB11800863

@eskimo I was unable to import into "login", "System", or "iCloud" keychains, but was able to import into "accountsKeychainExport". What is that? It seems very sus. In any case, I have TWO of these "accountsKeychainExport" keychains in my system, and both are empty, even after import. I had the inspiration to try dragging the .cer file from the Finder into my login keychain, and that seemed to work, but it says the certificate is not trusted: (I’ve redacted identifying info; note that the selected cert replaces the last cert in that list, set to expire in a month.) Ah, I had to DL a newer Apple intermediate certificate from here (specifically, the G4 cert). That seems clunky. macOS 21F79 on M1 Max MBP.