“file uri scheme”

Dear Developers, This is a known issue that the relevant engineering team is aware of. If there is a fix available, we will make sure to update this thread. For those who have not yet filed a bug report, feel free to do so and post the FB number here, to receive automatic updates on the issue. You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see updates to your report, please see What to expect after submission. Thank you for your patience, Richard Yeh  Developer Technical Support

So if I create an alias of a folder in Finder and hand the alias to my app (I also moved the alias file to a new folder, but I did not move the original folder)... Please file a bug on this and then post the bug number back here. I can explain what's going on, but URLByResolvingAliasFileAtURL should always resolve to the same location as the Finder. Only seems to happen if the folder I move the alias to happens to contain a sibling folder that has the same title as the original folder. So, making things concrete, the actual issue here is the following configuration sequence: (1) Create an alias file to the target beside that target: target target alias NewDir target (2) Move the object into a new directory beside another object with the same name as the target: target NewDir target alias target What's going on here is that bookmark resolution is driven by heuristics, one factor of which is the relative position of the bookmark and its target. Those heuristics are what allow resoluti

FSEventStreamRef reports changes on a directory. I have some comments below, but FSEvents are a complicated topic in their own right. If you've got a product that's actually focused on monitoring and updating a large hierarchy (this isn't actually all that common), then it might be worth starting a new thread that's focused on those issues. Does it work on file reference URLs? No, it takes the opposite approach, which is basically force you to iterate the hierarchy until it happens to stabilize. The core underlying issue here is that the file system doesn't restrict how it's modified and the API it provides only provides a picture of a particular instant in time. That is, when you ask for a directories contents what you actually get is the contents at that instant without any guarantee that they're still the current contents. Most of the time the contents don't change fast enough for that to matter, but in a frequently changing directory the past and now can diverge VERY quickly. You'll note

Thanks for checking with the network team so quickly! I have filed a bug: FB22181144

Thank you for your report! I could personally reproduce in French as well. I’d encourage you to file your feedback on https://feedbackassistant.apple.com and share the FB number here for tracking.

From your answer, I realise I was overlooking the obvious: after doing the work in the fast temp directory, I then need to create a second temp directory on the slower destination volume using URL(for: .itemReplacementDirectory…), copy the file across, and then use replaceItemAt from there. Sure, that makes sense. I think this is also one of those cases where the broader context of your app and user base is really a really important factor. Some apps (smaller documents, more consumer focused) should do their best to hide all of these details from the user, as they're not really useful/relevant and they just end up creating noise. Other apps (larger documents, more expert focused) benefit from making this visible to the user, as it lets them understand what's going on both to correct any problems (for example, space loss due to save failures) and take advantage of the data you have for them (for example, failure recovery). So any attempts to use that will continue to fail until the kernel (?) has fini

Honestly, I’m not sure what’s going on here. None of this sounds at all familiar. I’d like to get a copy of your installer package so that I can poke at it myself. Can you share a link to a download site here? [1] If not, you can file a bug and attach it to your bug report, and then post the bug number here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Posty your link in the clear; see tip 14 in Quinn’s Top Ten DevForums Tips.

Thanks for filing FB22152886. Zenning on this over the weekend I realised that there’s a much easier solution here. This is based on two key factoids: The app under test must have the Local Network privilege. Local network privacy doesn’t apply to loopback connections. So, you can set up a network listener in your app that listens for incoming connections and, for each one, opens a connection to your accessory and proxies traffic between the two. Your UI test can then connect to 127.0.0.1 and talk to the accessory indirectly through the app. I prototyped this in my office and it seems to work. I recommend that you try it out and see how far you get. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Filed a feedback ticket: FB22176952

When running those commands on my M1 Mac I get this: % file /Applications/MyApp.app/Contents/MacOS/MyApp /Applications/MyApp.app/Contents/MacOS/MyApp: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64] /Applications/MyApp.app/Contents/MacOS/MyApp (for architecture x86_64): Mach-O 64-bit executable x86_64 /Applications/MyApp.app/Contents/MacOS/MyApp (for architecture arm64): Mach-O 64-bit executable arm64 and % otool -f /Applications/MyApp.app/Contents/MacOS/MyApp Fat headers fat_magic 0xcafebabe nfat_arch 2 architecture 0 cputype 16777223 cpusubtype 3 capabilities 0x0 offset 16384 size 3190880 align 2^14 (16384) architecture 1 cputype 16777228 cpusubtype 0 capabilities 0x0 offset 3211264 size 3069792 align 2^14 (16384) and ... ==== Non-writable regions for process 14835 REGION TYPE START - END [ VSIZE RSDNT DIRTY SWAP] PRT/MAX SHRMOD PURGE REGION DETAIL __TEXT 10061c000-1008a0000 [ 2576K 2048K 0K 0K] r-x/r-x SM=COW /Applications/MyApp.app/Contents/MacOS/MyA

Filed a feedback ticket: FB22176453

[quote='878607022, Nickkk, /thread/817724?answerId=878607022#878607022, /profile/Nickkk'] I'm assuming that's what you mean by Mach-O image. [/quote] A Mach-O image is code that can be mapped into memory by the dynamic linker and then run directly, as opposed to something like a .o file that contains code that must be linked before it can be run. I talk more about this in An Apple Library Primer. A Mach-O image is often stored within a universal binary, one image per architecture. So when looking at stuff like this you have to consider the image of the architecture that was running. The other thing to considered is that the dynamic linker may only map in parts of your image. A good way to see what actually gets mapped is to run the app and then run vmmap against it. Consider this: % ls -lh Pages Creator Studio.app/Contents/MacOS/Pages -rwxr-xr-x 1 root wheel 45M 16 Jan 02:44 Pages Creator Studio.app/Contents/MacOS/Pages The Pages executable is 45 MiB. And this: % file Pages Creator Studio.ap

Thanks for your input. I added the following code in the arView.renderCallbacks.postProcess callback: let depthStencilDescriptor = MTLTextureDescriptor() depthStencilDescriptor.pixelFormat = .depth32Float_stencil8 depthStencilDescriptor.width = context.targetColorTexture.width depthStencilDescriptor.height = context.targetColorTexture.height depthStencilDescriptor.usage = .renderTarget depthStencilDescriptor.storageMode = .private renderPassDescriptor.stencilAttachment.texture = device!.makeTexture(descriptor: depthStencilDescriptor) renderPassDescriptor.stencilAttachment.loadAction = .clear renderPassDescriptor.stencilAttachment.storeAction = .dontCare renderPassDescriptor.stencilAttachment.clearStencil = 0 but the app now crashes with error Assertion failed: (destDepthFormat == jet_texture_format_DepthStencil), function create_render_mode, file jet_context_Metal.mm, line 895. VTPixelTransferSession 420f sid 494 (512.00 x 512.00) [0.00 0.00 512 512] rowbytes( 512, 512 ) Color( kCGColorSpaceSRGB, 0x0