does this affect you: https://developer.apple.com/help/account/manage-profiles/provisioning-profile-updates/. ? also, have a look at https://developer.apple.com/documentation/technotes/tn3125-inside-code-signing-provisioning-profiles

did you check https://www.apple.com/support/systemstatus/ when the problem occurred? Does it still not work? It works for me now, but you posted a day ago

IOServiceNameMatching is a convenience function which creates a matching dictionary with the contents [ "IONameMatch": ], so it is behaving exactly as it should. It does not return an IOService with name matching . The "IOService" prefix serves as a poor man's namespace. You need to take the matching dictionary and pass it to IOServiceGetMatchingServices, which will return an iterator. You walk through that iterator to get the actual services (if found).

this is a forum where developer can ask software development related questions, and sometimes get answers. if you have feedback about Apple software or hardware, you can use Feedback Assistant to send that feedback to Apple, or less formally using the web interface at https://www.apple.com/feedback/

if you think it is a bug, file a bug report with Feedback Assistant. If you want it to wait for user input, attach the breakpoint before you run the program.

Well, there's UIDevice.model, but then you'd need to know all the possible model strings. Also UIKit might lie on a Mac... The bigger question is - why do you need to know this? What is it about the running on a Mac which should make your app behave differently? You should test for the specific difference, not "is this a Mac", because the specific difference might disappear in iOS 18 or macOS 15.

Your example of the Arduino IDE (from arduino.cc) is a bit strange. This is not a sandboxed application, it doesn't need to ask for permission to access the Documents folder. If I open System Settings/Privacy & Security/Files and Folders, Arduino IDE is not listed there. I don't understand how you managed to disallow access to ~/Documents for that app. Maybe if you set your Security preference to "Allow applications downloaded from App Store", rather than "Allow applications downloaded from "Allow applications downloaded from App Store and identified developers" you might get behavior closer to what you want/expect?

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.