“Popping Sound”

Sorry for the confusion, and you assumed correctly that copying in the Finder works, but I actually meant something else. What I meant was this: a user of my app reported that when my app copies files from a QNAP NAS to a folder on their Mac, they get the error Result too large. When the app copies the same files from the Desktop folder, it works. Copying the files with the Finder, regardless their source location, works as well. From what the user told me, the issue only happens with some files. I actually asked them to narrow the issue down as much as possible and they found a folder with a single file, and copying that folder always causes that error. Interestingly, the destination file is actually created but has a much smaller size than the source: 250 KB instead of 34 MB. The user also shared that file as a zip archive on Dropbox with me. I ran the ls -l@ command on it to see its extended attributes and their size, the output was: com.apple.FinderInfo 32 com.apple.ResourceFork 286 com.apple.quarantine 5

Thank you a lot - I will try this weekend - I am at a client location right now - but when back I test and tell the results! Thanks a lot for the various ideas! Sounds good. Good luck and please let me know what you find. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

A user of my app reported that when my app copies files from a QNAP NAS to a folder on their Mac, they get the error Result too large. When copying the same files from the Desktop, it works. Clarifying what you mean here, are you saying that the Finder can handle the copy and while your app cannot? Or that your app is doing both copies it works to one destination (the Finder) and fails to another? Or something else? I'm going to assume the Finder works and your app fails (that's what typically happens) but please correct that if I'm wrong. I asked them to reproduce the issue with the sample code below and they confirmed that it reproduces. They contacted QNAP for support who in turn contacted me saying that they are not sure they can do anything about it, and asking if Apple can help. Can someone at Apple say anything about this? I spent some time looking into this and there does appear to be a newly reported issue (r.165759954) that sounds similar to this. In terms of next steps, I have a few sugges

It sounds like you're aware of what a routing app is, but just to confirm details: A routing app provides navigational directions between two locations. It is enabled inside of an Xcode project by going to the Capabilities tab, and adding the Maps capability, which will then show you a list of checkboxes for the transportation modes by which you're able to provide navigational directions between points. Those checkboxes correspond to values added to your Info.plist file under a key named MKDirectionsApplicationSupportedModes. It sounds like you're not providing directions, but you should check to make sure the above capability isn't enabled accidentally. And if you're not providing directions, also don't enable this capability just to try and solve this error, as I've seen people get tangled up further by trying that. If all of that looks good and that capability wasn't accidentally enabled, then the next thing you should do is to open a bug report with the details of your App ID and the bui

[quote='874071022, ball-hayden, /thread/807938?answerId=874071022#874071022, /profile/ball-hayden'] It's interesting that your guide says DevForums is not an official support channel, [/quote] That confusion is my fault, alas. Historically, DTS provided two forms of support: Formal support via technical support incidents Informal support, via the forums, mailing lists, and so on In 2024 we changed that process, putting a lot more emphasis on the forums. That way the results of our work are available to the entire developer community. As part of that we renamed technical support incidents to code-level support requests. Quinn’s Top Ten DevForums Tips was written before the 2024 change, meaning it originally used the old language. I tweaked the text slightly when that change rolled out, but re-reading it today it’s obvious that it wasn’t sufficiently clear. I’ve just updated the post to improve this. [quote='874071022, ball-hayden, /thread/807938?answerId=874071022#874071022, /profile/ball-hayden'] It sounds

One thing that I learned over the past hour or so is that dictation and emojis can pop up using fn + d and fn + e respectfully. But why would the function button be activated?

The files, both user-selected and sidecar, reside in a folder inside my user’s document folder, and I try to read the sidecar when the user opens the audio file. OK. SO, one thing I would test here is what happens if you test the same code with files that are in a directory outside of the normal user hierarchy. You can try with a directory inside your home directory, but I actually suggest using a folder ENTIRELY outside the user hierarchy— for example, on a disk image or an external volume. The issue here is that macOS has multiple independent systems of data protection, most of which are focused on user data (like the contents of ~/Documents/). Moving outside of that hierarchy means you’re looking at the basic case, which is easier to evaluate. Looking at the other cases here: I can access the sidecar file from the terminal and load its content. FYI, Terminal.app is a tricky tool to test an experiment with. The issues here are: It's not sandboxed, which exempts it from the more aggressive file prot

Your profile isn’t constructed correctly. The Enable-Private-Data is meant to be nested within a System dictionary: System Enable-Private-Data IMPORTANT Don’t enable all private data on a system you care about. While Apple strives not to log anything too precious, it’s hard to guarantee that. I usually do this sort of testing in a ‘victim’ machine. Typically that’s a VM, although that might be challenging given that you’re developing an audio accessory. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks @DTS Engineer - I appreciate your help. It's interesting that your guide says DevForums is not an official support channel, and yet when I tried to engage with Developer Code-Level Support they pushed me to DevForums implying that it is an official support channel. Do you have any way of feeding back to Code-Level Support that they shouldn't be pushing people here for official support? It sounds like all hope is lost on this issue. I guess the only workaround I can offer to affected customers is to use an Android device instead?

My general advice is that you avoid Multipeer Connectivity. I explain why, and a lot more besides, in Moving from Multipeer Connectivity to Network Framework. [quote='813963021, PellePepper, /thread/813963, /profile/PellePepper'] In real environments of athletics venues the solution is only stable in a region of about 2 meters [/quote] It sounds like you’re using it to access peer-to-peer Wi-Fi. I have three important notes on that front: Multipeer Connectivity is not the only way to access peer-to-peer Wi-Fi. I talk more about that in TN3151 Choosing the right networking API. If you just switch to Network framework, it might not actually help, because they use the same underlying Apple peer-to-peer Wi-Fi mechanism. OTOH, it might actually help because Network framework gives you great visibility into what’s happening on the ‘wire’ versus Multipeer Connectivity. We also have Wi-Fi Aware, which is a different peer-to-peer Wi-Fi mechanism. Note that Wi-Fi Aware is just there to set up the pairing, and

Hello Kevin, thx for coming here! Let me clarify: I can only access the user selected file. The sidecar file can not be accessed, due to not getting a FilePresenter (Sandbox tells failed to issue an extension for file) The files both user selected and sidecar reside in a folder inside my users document folder and I try to read the sidecar when the user opens the audio file. I can access the sidecar file from terminal and load its content. I can also load its content when opening it with a second NSOpenPanel(). So access rights are okay. Using one of my Apps from the AppStore which implements the same file access works as well. So currently I am lost why my fresh code on the fresh installed machine is not working. TIA, Volker