eskimo

I’m presuming this is on the Mac. That’s important, because the keychain is much more complex on the Mac than it is on iOS. See TN3137 On Mac keychain APIs and implementations. I have some generic advice about how to use the keychain effectively: SecItem: Fundamentals SecItem: Pitfalls and Best Practices Looking at your code, I don’t see anything fundamentally wrong with it. The code doesn’t opt in to the data protection keychain, so it’s gonna be using the file-based keychain. Moreover, it’s likely that you created the item in the default keychain, which is usually the login keychain. Given that, you should be able to look for the keychain item using Keychain Access. That’ll tell you whether it’s there or not. If it’s not, you can’t fix that with code. You’ll have to find a keychain with the item in it. I have hints and tips on how to do that, for very different reasons, in The Care and Feeding of Developer ID. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail =

I’d like to clarify your goals here: Are you trying to control your app running on the Apple TV? Or create a virtual controller for the Apple TV as a whole? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. If you post your notary request UUID, we can check to be sure everything seems to be working as expected. As you notarise your apps, the system will learn how to recognize them, and you should see fewer delays. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I responded on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hmmm, it’s Xcode source editor day here on the forums! You go for months without a question about this tech, and then you get two on the same day. [quote='828923022, Adamc93, /thread/750811?answerId=828923022#828923022, /profile/Adamc93'] Is there a way to do this while having multiple versions of Xcode? [/quote] Absolutely. I can’t remember a time when my Mac has only had a single copy of Xcode. Right now I have 16.2 in the Applications folder, and 16.1 and 16.3b1 in my XcodeZone folder. Getting your source editor extension to show up can be tricky. However, I always seem to manage to get it working. I just tested the bring-up process myself, and it didn’t give me too much grief. See my instructions here. That should get you up and debugging. Once you get to deployment well… I have suggestions on that front too, but lets crawl before we run, eh? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Geting Xcode to recognise your source editor extension can be tricky. There are two cases to consider: Debugging Production I recommend you start with the debugging case. When you create a new source editor extension target, Xcode create a scheme for it. That scheme isn’t very useful out of the box. Do this: Use your primary copy of Xcode for this work. Ideally it’d be the one in the Applications folder. Select the extension scheme in Product > Scheme. Choose Product > Scheme > Edit Scheme. In the Run action, switch to the Info tab. On the Executable popup, choose Other and select your primary copy of Xcode. Make sure Debug Executable is not checked. Close the sheet and then choose Product > Run. Xcode should launch a second copy of itself. In the Dock, you’ll see the icon with an orangey tint. Bring that to the front. In this copy, open a test project and navigate to a source file. Your extension should be visible at the bottom of the Editor menu. I just tried this today (Xcode 16.2 on macOS 15.3

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. What I want to ensure that my multiple mallocs I will be calling will only allocate between those virtual addresses. Do you control the code calling malloc? Or do you want this to apply to all malloc calls made by a process, including calls made by system frameworks that you don’t have the source code for? Are you trying to do this for a product? Or for an experiment? That matters because some of the techniques you might want to use are not appropriate if you plan to distribute a product to a wide audience. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

When a sandboxed app spawns a child process, that process inherits the app’s sandbox. This is blocking ps from being able to do its job. This isn’t surprising. The App Sandbox is meant to provide both security and privacy, and allowing your app to list all the processes on the system runs counter to that goal. Two other notes: Normally I encourage folks to use the APIs in rather than running ps. Those APIs are also blocked by the App Sandbox, failing with EPERM. Running child processes via Process is harder than it looks. Your code might deadlock if the output from ps is large. I show one way to avoid this in Running a Child Process with Standard Input and Output. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Sorry for the long delay. I suspect I was out of the office when you originally posted this. There is no recommended replacement for LSSetDefaultHandlerForURLScheme. In some cases this functionality has been subsumed by the system. In some cases this functionality is no longer available to your app [1]. In some cases there’s no replacement because we favour Universal Links over URL schemes. If you have a use case that’s not covered by the above, you should feel free to file an enhancement request with detailed information about what you need to do. You can then continue using LSSetDefaultHandlerForURLScheme in the interim. 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 [1] Specifically, for apps on the Mac App Store, where such requests are blocked by the App Sandbox.

OK, then I think you have bigger problems. At one point we updated the sandbox to block attempts to change default URL scheme handlers. So, even if you get past this, I suspect that LSSetDefaultHandlerForURLScheme will fail [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] I vaguely remember this failing with permErr, or -54, but… Oh wow, some searching turned this up in a DTS case from 2018 (s. 701054199).

I tend to agree with darkpaw here. I’m more likely to create a new project for the app and then copy over any source code that I want to reuse in that app. As projects evolve they tend to accumulate cruft, and a new project lets you leave all that behind. Having said that, duplicating a project isn’t completely unreasonable. If you have automatic code signing enabled then the only thing you should need to change is the bundled ID, in Signing & Capabilities. But that’s only going to work for simple projects. Any complicated project is going to have additional bits that you need to think about carefully. For example: If your project has app extensions, you need to change their bundle IDs to match. If it’s a document-based app, you need to tweak all the document types. Likewise for URL scheme handlers, icons, App Intents, and many many many other things The nice thing about creating a new project is that you ‘fault’ these things incrementally, as you notice they’re missing. If you duplicate your project you

I need to clarify the specific circumstances under which you’re seeing this error. You wrote: [quote='776503021, jsflack, /thread/776503, /profile/jsflack'] when I set the target to VST3 instead of Standalone Plugin and check the Debug Executable box [/quote] Above the Debug Executable checkbox there’s an Executable popup menu. What have you selected there? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Are you trying to distribute your app directly, using Developer ID signing. If so, it’s likely you’re hitting the issue discussed in Exporting a Developer ID Network Extension DevForums. If not, I need more info about what’s actually failing. You wrote: [quote='776504021, Box1688, /thread/776504, /profile/Box1688'] I am always prompted that my description file does not contain NetworkExtension. [/quote] I’ve no idea what you mean by “description file” in this context. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There’s no official Apple sample code that meets those criteria [1]. I’m not in a position to write sample code for you. There are numerous open source projects for these technologies. I don’t maintain expertise on those so I can’t give you a specific recommendation. There’s a lot of useful docs and forums posts linked to from Network Extension Resources. I recommend that you dig into this yourself. If you have questions, search the forums for answers because I’ve helped a lot of developers with this technology over the past decade. And if you can’t find answers, feel free to post specific questions here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, there is the very old SimpleTunnel sample but: It shows the first two but not the third. It’s for iOS, not macOS. It’s suffered from significant bit rot, to the point where I don’t think it’s a good place for you to start.

OK, but that doesn’t help me help you. You have three choices here: You can dig into this yourself. That’s one of the nice things about using an open source library. You can file an issue with the library’s developers. You can file an issue with Apple. See Bug Reporting: How and Why? I can help you with the first option, but only insofar as it touches Apple APIs. If you boil this down into a specific API that’s failing, or has just changed behaviour, I’d be glad to look at that. But I can’t debug this open source library for you. From DTS’s perspective, this is your code. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com