Oh yes, I used that Car Play Music Sample to add CarPlay to my app and it seems to work good but now I need to make sure Siri works with CarPlay and the main app, the watch, HomePod and everything else. I'm just running into conflicts with INPlayMediaIntent plus I'm working on a Radio app so when a user says "Hey Siri, play Beatles Radio" the phone tries to play Beatles in my music library instead of my app. I have 40 other radio stations with the word "radio" in the name, so I'm dealing with that. I'm getting lots of other errors when I try to upload to appstoreconnect, but will deal with them later: ITMS-90626: Invalid Siri Support - '' is not a supported intent type Though you are not required to fix the following issues, we wanted to make you aware of them: ITMS-90626: Invalid Siri Support - No example phrase was provided for INSendMessageIntent in the 'pt-br' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - No example phrase was provided for INAddMediaIntent in the 'fr' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: pt-br ITMS-90626: Invalid Siri Support - No example phrase was provided for INSendMessageIntent in the 'en' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases'

I fixed this by just using a different computer with XCode 16 beta 1. I did the USB connection, accepted prompts to trust the phone and device, and did a sync of any debugging symbols. I created a new app just to test, and it worked ok. Was then able to connect with my old computer and all went well.

I think I fixed this. I think the problem is because I have multiple targets in my project (iOS, tvOS, watchOS, etc) and that the watchOS project is not using my bridging header. I was getting compiler errors because I didn't realize my Swift files were being compiled for the iOS, and the watch. By making the watch target use the bridging header, that seems to help a lot.

Yes, my project compiles OK for me if I remove those lines that try calling fooTest() or try setting self.player.meteringEnabled The Github project compiles ok for me too. All I did was drag these 6 files into my project: ACBAudioProcessHelper.h ACBAudioProcessHelper.m AVPlayer+ACBHelper.h    AVPlayer+ACBHelper.m    MYAudioTapProcessor.h   MYAudioTapProcessor.m Here's the entire contents of my bridging header.h file: #import "AVPlayer+ACBHelper.h" #import "ACBAudioProcessHelper.h" #import "MyAudioTapProcessor.h" I'm totally sure those files are being used because if I put a syntax error in those files (on purpose), I get an error. I was able to download that Github thing by getting the master branch, opening ACBAVPlayerExtension.xcodeproj and building it by choosing the ACBAVPlayerExtension target and a simulator. I think I had to assign a team under the Signing and Capabilities section, but it builds ok using Xcode 12.4 and Big Sur. I've spent probably 3-4 hours on this problem. Will spend another hour or 2 tonight but I'm really stuck. Wish I could post screen shots here.

Oh, I think I just answered my own question. I used lipo from Terminal like this: % lipo AppleConnectClient -info and got this response: Architectures in the fat file: AppleConnectClient are: x86_64 arm64 arm64e