Have a look at the Info panel in the target settings, check that CFBundleVersion and CFBundleShortVersionString are what you expect. Do they differ from the values in the Info.plist file? If they are not what you expect, check the Build Settings, filter on CFBundle and check the "All" tab, so you can see how those strings are generated. There is a setting in Build Settings called "Generate Info.plist file" (under Packaging), which defaults to true. I find it best to keep it at true, and add additional keys/values using the Info tab. I'm not sure what happens if you set one value in Build Settings and another in the Info tab, or a different value directly in the Info.plist file.

You don't need to do anything. You have a version of Xcode that you downloaded from developer.apple.com, rather than a version you obtained through the Mac App Store. That's fine, just use it. I use manual downloads rather than app store downloads because I don't want the app store to automatically download a new version when I'm not ready, and I often keep older or newer (beta) versions around too.

I filed a bug report and it was returned as "behaves as designed". The default clipping behavior for views changed in Sonoma, it is in the release notes. So, yes, I fixed this by setting clip to bounds to true for some of my views. I'm pretty sure I read the release notes but ignored that item because I thought I'm not drawing outside my bounds anyway. But a background filter layer is just a layer...

I think you're talking about a macOS app, right, not an iOS app? are you the account owner? Only the account owner (not a mere admin) can create certificates and profiles for managed entitlements. Xcode can't make it automatically, and the developer portal's feedback is unhelpful on this issue. I think you want a signing certificate for Developer ID, not for Apple Distribution. The latter means on the app store, the former means you distribute it, and it is signed by a registered developer, and that signature is notarized by Apple. On the Xcode side, you leave the signing set to "Automatic", and go through the steps to make an archive. Once you have an archive, open the Organizer window, select your archive and click Distribute App. In the next dialog, select Developer ID as the method of distribution. A dialog will come up offering you the choice of automatic or manual signing. Choose manual. In the next dialog, pick appropriate Certificates and Profiles for the app and its extension. The profile you pick for the app is special - this is the one that your Account Owner has to create. You probably don't need a profile at all for the driver extension. Click Next, review your certificate and profile choices, if you are happy, upload to the notarization server and wait a little while. Good luck!

The error message clearly tells you that Thunderbolt accessories are not supported on this iPhone. What more do you need to hear? Also, this forum is for discussions about the development of software and accessories for Apple platforms; your question is not appropriate here. There are other forums for technical support and general user discussions.

What API calls are you using to execute the commands you describe from the app? After you make your script, are you making it executable? Are the scripts somewhere on the file system, or inside your app's bundle? Have you looked at the error messages in Console?

is the file inside your app's sandbox? You haven't said where it is. fileimporter (not file_importer) puts up a user interface, so the user is granting explicit permission to access the file. fopen() doesn't have UI, so it has to get the permission from somewhere else. That somewhere else can be implicit (the path leads to somewhere in the app's sandbox), or you can get the path by resolving a security scoped bookmark which you have created earlier by interacting with the user.

I think the short answer might be "no". dexts are always sandboxed. You generally can't read or write files outside the sandbox. If a user explicitly grants permission to read or write a file, you can get a security scoped bookmark for that file in your app, and give it to your app to resolve. You should be able to use the property interface to read/write configuration data. Use CopyProperties from your driver's Start(), to read the properties, and implement SetProperties in your dext. To alter the properties from the app, you should be able to use IORegistryEntrySetCFProperties from IOKitLib.h, but you may need to use IOConnectSetCFProperty or IOConnectSetCFProperties. Those two need a connection, which you get from IOServiceOpen, which in turn requires that you can make a user client from your dext, so you would have to implement code to create a user client object. I haven't tried any of these (at least not for a long while) and I can't find any sample code which does this. Good luck.

I filed a bug related to this, FB13238490. I could not reproduce exactly the same behavior in a test application. I'm using a xib based interface with Core Animation layer effects. In Ventura, a Box Blur type of Background Filter effect only affected the background directly behind the view with the filter effect - it did not extend beyond the bounds of the view. In Sonoma, the Background Filter effect blurs all the views 'behind' (in z order) the view with the filter, and the blur effect extends over the entire background.

I would: run disk first aid, reinstall Xcode, reinstall Sonoma, in that order.

not in the language itself. There are trigonometric functions in the CoreGraphics framework.

which symbols are missing? Show the the Report Navigator in Xcode Click the most recent Build output in the main panel of the window, scroll to the link error and highlight it at the extreme right side of the error, you'll see a little lozenge-shaped control that looks like lines of text in a tiny document click that to expose the details of the link error, that should help you figure out if you are missing a library or framework, and which one.

did you have a look at what other apps which can open any file are using? For example, Atom, BBEdit or HexFiend?

So you made some progress! You said "When I comment out a section of the view. The build is successful..." - what section? Initially, you were asking about a build problem. That original build problem was caused by something in that commented-out section. Figure out what exactly the problem is. Sorry, can't help you with Firebase. That may be caused by commenting out some of the code to fix your build error.

welcome to the forum! Nothing jumps out at me as obviously wrong in the code you posted. The code is incomplete, so it can't be simply copied and pasted into someone else's project so they can maybe duplicate the error you see. In situations like this, where it looks like the compiler is complaining of an error in the Form closure, I would try commenting out different elements of the Form to figure out what exactly it is complaining about. My hunch would be a typo in TLButton, which you have not shown. You asked how you receive a response. You can 'watch' a thread, by clicking the bell icon on the top right of a thread. I think the forum may now automatically email you when there's a new response to a thread that you started. Incidentally, if you want to share a YouTube video at a particular point in time, you can use the Share button on the YouTube button to generate a link. On desktop at least, there is an option to "start at", which appends a time to the URL.