I am trying to run the latest Xcode-beta in a beta 3 VM on beta 3. After expanding the XIB I get the error "Loading a plug-in failed." It appears to work correctly directly on the running macOS 15.0 Beta (24A5289g) Has anybody had any luck with this?

Bluetooth is a huge issue in Ventura that has not been fixed in 13.1 RC1. If you have more than two BlueTooth devices connected, sound to even AirPods goes to hell with crackling and interruptions. Game Controllers also lag. This is on a high-end Mac Studio. I have left "Feedback" and am really ticked off that this has not been addressed. This used to work just fine in older versions. BTW, the PowerBook M1 13" also had these issues when it was first released. The unsatisfactory solution is to connect Magic Keypad and Trackpad with Lightning USB and turn off the mouse. Has anybody else run into this? There are a lot of reports on other forums. I have deleted all devices and reinstalled them to no avail. Does anybody else have this problem or a solution?

It looks like the simulator libs are in the developer folder stored in the downloaded disk images under some UID such as: /Library/Developer/CoreSimulator/Images/3FC7F588-A6CB-4107-ABBA-FDABF615AD87.dmg How do I set up explicitly downloaded images like "watchOS_9.1_Simulator_Runtime_Release_Candidate.dmg" to be useable for Xcode. I have multiple dev machines and this would make it much faster, especially since Content Caching does not look to work for Xcode-related downloads from the Developer site.

Ventura Beta 4 is not updating to Beta 5 on a Mac Studio booting Ventura from an external Thunderbolt SSD. Previous updates worked. It gets to the first black loader screen with white progress bar, but reboots after 30 seconds. Tried several times. Any ideas?

Up to now, we have delivered our app with an installer via notarized DMG. Using the same process of signing notarization fails with just the App setting up for drag install. The app is signed and passes notarization. So does the installer. The DMG is signed with the same arguments and identity in either case. Failure is "Signature of the Binary is invalid" despite the fact it can be notarized on its own or in an installer pkg!

After a mishap where Ventura upgraded my main Monterey installation instead of installing on a second Thunderbolt SSD on my MacStudio, I cannot get the Apple Wallet to work after a clean install. Cards cannot be added due to changes in security settings despite setting them to defaults. I toggled update settings etc. Spent more time on this then I will ever save from this feature. Is Apple Wallet allowed on only one boot installation on a system? Does it make a difference whether the 2nd install is on an internal volume vs external?

The updated for Ventura Beta 4 is not showing up in Preferences on Mac Studio. Is there a way to force it. I have pulled it up multiple times.

In the old days, man pages listed the return codes of an app. That is not the case with notarytool. Is there a place where the possible return codes are listed? Apart from parsing notarytool's output, is there a way to get the submission-id returned. I am working on updating our automation scripts and would like them to be robust but also legible. Alttool output parsing was a bit of a mess in the previous version. I want this to be easy for whoever maintains this in a year or two.

I installed the public beta Profile twice wit the required reboots, but the update is not showing up in the Watch app. macOS, iOS, and iPadOS loaded fine.

Selecting a word, right clicking and picking "Look Up" used to show a dictionary entry, now it shows some web clipping.I have this on multiple systems using the GM seed.What is happening?

We are prepping to move from Developer Distribution with notarization to App Store distribution. Our product uses multiple components and is based on Qt with some hybrid Obj-C extensions. We run the app from Xcode for debugging and do not use Qt Creator at all. Up to now, I had set up build scripts that “package” the app including bundled Frameworks (MACH-O link names need adjustment, etc.), signing with entitlements (Developer ID: Application,) and notarization. That all worked fine for several years. The app has a 14-year history on macOS. I revised our project to be run and packaged completely from within Xcode. Signing is Automatic using "Developer." That worked great on the first try a couple of weeks ago. I could archive, pull up the organizer, and get the full dialog. Developer ID Distribution/Export worked great. Last week I was polishing a few items. Without any project changes, I get a crippled dialog. I used a checkout on another system with same result. I switched to a different developer account. I cleared out Xcode DT settings (' defaults delete com.apple.dt.Xcode’) and set up fresh identities for the team. I have spent hours trying variations of signing etc. BTW, another pure Obj-C iOS project has no issues. Any other ideas to track this down? I found nothing on Internet searches? What controls the configuration of the Distribution window? I am now using Monterey 12.2 and Xcode 13.2. I have tried older versions with the same problem. It must be related to the project or signing. Thanks and Happy Holidays. -- Harald

Running Xcode 13.1 under Monterey. Last week I still saw the expected distribution options for our macOS app (App Store Connect, Developer ID, Development, Copy App.) This week all I see is to copy the content/app to the desktop or copy the Archive. Signing worked fine. I used another clone on a separate machine with the same result. The project has not changed at all. What gives?

On clean we need need to remove some additional files generated during the build via a custom makefile. With the Legacy build system, we use to do that with a dependency (target) running a build script with custom actions. Is there a way to do that with the new build system? If yes please point to the docs or describe.

It looks like iOS 15 causes a continuous crash/boot loop when paired with Series 0, 1 & 2 watches. Unpairing and pairing the watch with iOS 14 resolves the issue. Has anybody here seen this, too? I am seeing it with my original AppleWatch SS and another user is seeing it with Series 1. I am presuming it's a watchOS incompatibility in the comms protocol. I actually worked with Apple Support to have the watch diagnosed and it came out perfect. They sent me a refurb anyway! But the problem persists.

I am running the latest iOS beta and the HomePod proximity handoff for music or calls completely stopped. With the previous beta I was able to fix it by resetting the Network settings, but that is not working now. I have a number of HomePods and HomePod Minis set up in Stereo mode as well as single. I have rebooted everything. Our other iPhone works with these as expected. Any ideas of a fix? I have filed a bug.