what exactly does your distribution profile look like? And what does your entitlement claim? the message is saying that the contents don't match as expected. Follow the instructions here https://developer.apple.com/documentation/technotes/tn3125-inside-code-signing-provisioning-profiles to extract a readable copy of your profile and its signing certificate. Have you requested the USB DriverKit entitlement for your vendor ID from Apple? Confusingly, the entitlement (granted by Apple to your development team) and the entitlement (claimed by an app) both have the same name but are two different things. You can claim an entitlement in an entitlements plist. In many cases, Xcode will automatically generate a corresponding entitlement in the provisioning profile for your app and everything will Just Work. Managed entitlements, like com.apple.developer.driverkit.transport.usb, are special. For development, you can just claim the entitlement by putting any vendor ID into the plist entry. Xcode will match that to the "*" in the development provisioning profile. Such a profile is not valid for distribution. For distribution, the Team Owner needs to create a profile with the appropriate managed entitlements enabled. Mere Team Admin roles cannot do this, but the portal doesn't tell you that.

the only documentation is in the header files CoreMediaIO/CMIOHardwareObject.h. You set up a listener proc with an array of property addresses you want to be notified about. You can use a block-based or straightforward function-based callback. In your callback function or block, you'll get a list of property addresses which have notified you, but no further information (such as the property values). All that the callback is telling you is "this property changed", you have to make a call into your extension to get the value of the property of properties you have been notified about.

bDeviceClass = 0xef, which means "Miscellaneous". This isn't a standard communications device so the in-box drivers on macOS don't know what to do with it. It needs a driver from the vendor, Acer. Acer's web site does not claim macOS compatibility for this device, so I wouldn't hold your breath. Incidentally, this isn't an appropriate question for this forum, which is for questions relating to developing software for Apple platforms. End user support forums are elsewhere.

Even if Xcode can handle 400 projects in one workspace, do you really want to make and manage 400 projects? Even if you automate their creation, once created, each project is separate - if you make a change you would like to have in each project, you have to make that change 400 times. You could edit each project using a script, but that approach is horribly fragile. I would prefer a single project which makes a generic target, with additional Run Script build phases to the target which make the target's output customer-specific, perhaps based on an environment variable. You can set environment variables from the Run Scheme, so you don't have to drop into the command line to build for a new customer from Xcode. This should make adding a new customer reasonably painless, and avoid duplication.

you can override connectClient and disconnectClient if you want to monitor connected clients. Make the number of connected clients a property of your extension. To communicate this asynchronously to your app, you can call notifyPropertiesChanged in your extension. In the app, install a notification handler using CMIOObjectAddPropertyListener.

"This example is a scene from Prehistoric Planet that has been converted to 3D for playback on Apple Vision Pro. Watch Prehistoric Planet in 2D on Apple TV+, where available. ". You're trying to play it back on a Mac.

if you open the Xcode Devices and Simulators window, find your phone in there, can you see any crash logs from the phone that tell you anything useful?

attach .onAppear to the contents of your details, kinda like this minimal example struct ContentView: View { var body: some View { NavigationSplitView( sidebar: { Text("Sidebar") }, detail: { Text("detail") .onAppear { print("details appeared") } }) } }

This doesn't usually happen to me, but I also don't have this icon in the top of my Xcode window: might that have something to do with it?

in another Terminal window: log stream --predicate '((process beginswith "tcc") and (message contains "<bundle ID of your tool>"))' then run the tool, should give you some clues

You signed with an Apple Development certificate, you can't notarize apps signed for development. They must be "signed with a valid Developer ID certificate", as the error message says. Development signing is for development, for use on your own computer or other computers mentioned explicitly in the Apple Development certificate. Distribution signing uses a different certificate, enabling the app to be launched without complaint on any machine.

I can't figure out what you're trying to do here. I tried to put your TestView() into a template project's ContentView, but nothing animated at all and your print statements were not called. Your code didn't compile because previousOffset = offSet should read previousOffset = oldValue could you post or provide a link to complete code which works, and provide an explanation of what you're actually trying to do? There would appear to be much simpler ways to offset a view with an animation.

You don't, usually. The first time your app uses the camera (e.g.makes a AVCaptureDeviceDiscoverySession ), the OS will figure out whether you have an entitlement to use the camera (com.apple.security.device.camera) and a usage string (com.apple.security.device.camera, or INFOPLIST_KEY_NSCameraUsageDescription). The OS will show the permission dialog, using your app's usage string. If you want to make this a bit more explicit, you can make a button in your own UI which deliberately provokes this OS behavior, perhaps as part of an onboarding flow. But you don't have direct control over it, because the OS is asking for user permission, your app is just awaiting user permission or an error.

Instead of layer.addSublayer(previewLayer) write self.layer = previewLayer in your CameraPreviewLayer.

You said "My ultimate goal is to examine the detailed error message " The error message will appear in the system log, along with all the other messages from numerous processes on your Mac. You could use the Console app to look at the log, but its filtering is a bit rudimentary. The only tool you need is the command line tool log. Try man log for starters, then go looking on the Internet for "macOS log predicate example" or something like that. You probably want to look for logs emitted by tccd (the Transparency, Consent and Control daemon) with the text "disable-library-validation" in the message field. You can also cause the problem, then quickly use sudo log collect --last 1m. This will write a .logarchive file into the current directory (it won't overwrite one that is there already), giving you an archive you can poke around in at your leisure. A minute of logs is still a pretty huge database, but it might be a good way to find out what predicate you should be using.