file uri scheme

I use one taskIdentifier per file, and when the file fails, I can retry the task and have it continue where it left off. This is not what I would do. The problem here is that you're not going to be able to start new tasks once you enter the background, so you're not going to be able to retry once you enter the background. I would use the background task to handle the whole operation, including retries. (I am reusing the taskIdentifier here for retries, let me know if I shouldn't be doing that.) Yeah, don't do that. The problem is that you don't really know when we're done with any particular task ID, which means you don't know when it's safe to reuse that ID. These task IDs will never be user visible, so I'd just append a value to the string to force uniqueness. Case in point on the done front: What I would have expected is that the failure task is REPLACED with the new task and new progress. Instead what I see is TWO ContinuedBackgroundProcessingTasks, one in the failure state and one in pr

Does Finder's I/O behavior trigger specific SCSI command sequences or timing issues that CLI tools do not? Sort of. The difference here isn't caused by any fundamental difference between the Finder and “CLI tools“ - at the level you're interacting with, they're both just processes doing reads and writes. Indeed, ironically, I believe we moved copying out of process a few releases ago, so as far as most of the system can tell, the actual copying is occurring from very similar components. What is different is that they’re almost certain to have different I/O patterns. On the CLI side, I'd cp is using copyfile() and as are many of our higher-level APIs (notably, I believe NSFileManager has converted to it). On the other hand, the Finder uses its own copy engine both because it's older and because the details of its behavior are different than most APIs (for example, it preflights copies and uses VNOP_COPYFILE for smb copies). The big thing I'd keep in mind here is that the reason you tend to see common I/O patte

Thank you for your post. We are unable to locate the appeal you submitted. If you could, please submit an appeal to the App Review Board. When filing your appeal, make sure to: Provide specific reasons why you believe your app complies with the App Review Guidelines. Submit only one appeal per rejection. Respond to any requests for additional information before submitting an appeal. Once you have submitted the appeal we can escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they've completed their investigation.

Hi, Sorry to hear you are having problems getting previews working. The best next step will be to file a feedback with diagnostics so we can take a look. We will need the diagnostics Xcode Previews generates in order to make sure we understand the error the previews system is encountering. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appear, click the Diagnostics button in that banner; or (b) if you're not seeing an error but you still want to provide diagnostics you can get the same diagnostics window by going under the

We are experience a similar issue. Feedback assistant bug: FB21235642 What I filed in that bug report: We are seeing installation of our PKGs that have been working for years across multiple OS versions are now failing to install on macOS 26.1. This can be reproduced with the Chip-Osc Installer Mac.pkg in the attached Chip-Osc.iso. This issue is happening with hundreds of our ISO/PKG installers; Chip-Osc is one with small file size that reproduces the issue. When run with GUI by double-clicking the Chip-Osc Installer Mac.pkg in Finder we see the following error message: The installation failed. The Installer could not install the software. The Installer could not install the software because there was no software found to install. We also see a failure when running from the command line. The following command: sudo installer -pkg /Volumes/Chip-Osc/Chip-Osc Installer Mac.pkg -target / -verbose Fails with this error: timestamp file successfully generated! installer: Package name is Ch

I team! Do we have any updates regarding this? We've installed the last version of the Transporter APP available from the official site and checked the documentation (https://help.apple.com/itc/transporteruserguide/en.lproj/static.html). But seems very outdated regarding the last changes performed with Apple Connect API authentication. Many of companies that work with hybrid platforms (highcode/lowcode) doesn't have any MacOS systems with Transporter app, that allow deliver ipa files to Apple Store Connect (for test or production). It would be important to cover this scenarios. We already tried some commands, but seems that somethink is still missing. Executing comands like this ones always retrieved errors: iTMSTransporter.cmd -upload -assetFile .mobile-appapp.ipa -apiKey -apiIssuer -sigingKey -v eXtreme -assetDescription [2025-12-02 15:34:24 WET] DEBUG: Setting System property: DataCenters = contentdelivery02.itunes.apple.com [2025-12-02 15:34:24 WET] DEBUG: Setting System property: DataCenters.h

[quote='867839022, MoLotus, /thread/808485?answerId=867839022#867839022, /profile/MoLotus'] I clicked 'Accepted Answer' by mistake and can't undo it? [/quote] Indeed )-: See tip 12 in Quinn’s Top Ten DevForums Tips for more about that. [quote='867839022, MoLotus, /thread/808485?answerId=867839022#867839022, /profile/MoLotus'] Note that the comment facility here is failing to post comments [/quote] Well, they post but there’s a bug causing them to not show up immediately (i. 98940414)-: In general, I recommend that you reply as a reply. See tip 5 for more on that. Coming back to your technical issue, this seems to be working for me in Xcode 26.1. Here’s what I did: Using Xcode 26.1 on macOS 15.7.1, I created a new project from the macOS > Command Line Tool template, selecting C as the language. I changed main.c to this: #include #include __attribute__((constructor(200))) void foo(void); __attribute__((constructor(101))) void bar(void); void foo(void) { printf(foon); } void bar(void) { printf(barn); } int

It is also failing on iOS 26.2 Beta 3. I've filed a Feedback Assistant issue: FB21233240

[quote='867789022, AckwelFoley, /thread/808594?answerId=867789022#867789022, /profile/AckwelFoley'] any chance you could give some details on how FSKit knows that a particular FSKit module is enabled for a given user [/quote] No, sorry, these are very much implementation details and thus not something I can encourage folks to rely on. IMPORTANT macOS works hard to prevent users from running code unexpectedly, hence the existence of System Settings > General > Login Items & Extensions. Given that, it wouldn’t surprise me if the files that back these setting were protected by MAC [1], or become so protected in the future. Regarding your overall goal, there’s a deeper architectural concern in play. Settings like this are usually stored in the user’s home directory, which results in an a clear chicken’n’egg problem if your FSKit module is responsible for mounting that home directory. Hence my suggestion for an ER, and specifically the option to use a sysex, which is global to the system as a wh

Thanks for filing FB21229146. FWIW, I tried reproducing this here in my office — using a private browsing window and a new non-Apple test account — and I didn’t see it. Clicking “Remind me later” took me to the root of the forums with the ‘welcomes to the forums’ tour sheet, which is what I’d expect. So I’m not sure why it’s affecting you. How did you manage to escape the “Remind me later” loop? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

If you have multiple issues, it’s generally best to put them in different threads. That’s because different folks have different expertise, and it’s unlikely that any one person will be able to help you with all of your issues at once. In this case, I can address your second question: [quote='808920021, chps67, /thread/808920, /profile/chps67'] In Xcode 16 why is it no longer possible to arrange my files as I did before [/quote] I’m not 100% sure I understand this, but I suspect it’s because Xcode now has two ways to organise items in the Project navigator: Groups, as used by older versions of Xcode Folders, which are new [1] With groups you can explicitly manage the position and order of items in the Project navigator. With folders, Xcode does that implicitly, replicating the file system hierarchy and showing all the items alphabetically. Folders have some really important advantages — most notably, they radically reduce the number of project file merge conflicts — but if you don’t

Well, that's your opinion. I've managed to release a number of Swift apps without seeing the issues you describe. I've got no idea why you can't organise your folders properly. What's the problem? You ask why it's no longer possible to do something, but you haven't really explained what it is that you're missing. You can still right-click a file or folder and create a new group, new group from selection, new folder, and new folder from selection. And you can drag files and folders onto the Project pane and choose how they're added. I don't understand what it is that you're having a problem with? Rather than posting here, why not raise feedback tickets and explain where you're seeing issues? Give Apple a record of the problems and a chance to fix them. You can do that at: https://feedbackassistant.apple.com/ then post the FB number(s) here. Also, Xcode 26 is out, so you could try that out and see if any of your issues are fixed.

This is only with the new NetworkConnection API, right? So things work if you use the older NWConnection? If so, my advice is that you file a bug against the new API. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com