“translate scheme”

Hello, Does the Game Controller framework provide access to the Home button on your JoyCon? If so, it seems like remapping the Home button in your app's control scheme to another action would suffice i.e. override the default value/action in your app. This way your app responds as expected even when the Home button is pressed.

Hey, thanks, I really appreciate you responding. Our use case is this: we use a 3rd-party web app (Autodesk Flow Production Tracking) that uses a custom URL scheme to launch a desktop app (RV). This works fine. However, it is not uncommon for more than one version of the desktop app to be installed on any given machine for various reasons (feature requirements for different different projects, testing, troubleshooting). In addition, the desktop app supports site-customized scripted add-ons that require context-dependent environment variables to work properly. So historically, we have used LSSetDefaultHandlerForURLScheme to point the custom URL scheme to an in-house app that did the environment setup work and then launched the required version of the desktop app. Now, we are finding it hard to keep the custom URL scheme reliably pointed to our environment setup app. Since it registers the same custom URL scheme as the Autodesk desktop app, what actually gets launched is now

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 m

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 pro

For anybody encountering this in the future, it turned out that the .mov being in a different folder than the project (Downloads vs Documents) was causing Xcode to silently fail. I had never rejected permissions for Xcode to access a folder. Temporary solution: Putting the .mov into a public folder such as /Users/Shared/... and re-adding it to the scheme seems to have fixed the issue. This doesn't explain why it worked once but not in subsequent runs.

Custom URL schemes seem to work a bit better than universal links. In all the cases where the universal link attempts to open the web page and adds a page banner saying Open in APP, the custom URL scheme instead presents a blank grey page with a popup saying Open in APP?. Although both involve the same number of taps for the user, the latter is much more better in practice as it's obvious what the user has to do.

I found this old thread: https://developer.apple.com/forums/thread/684693 which suggests that window.open() might work. It hasn't worked for me yet, but they were discussing custom URL schemes rather than universal links. Might that be significant?

window.open(universal-link) not working for me in 2025. Might a custom URL scheme behave differently than a universal link?

If this is the case, then using a custom scheme with WKURLSchemeHandler to access local resources on an https page will be disallowed. In that case, what is the purpose of WKURLSchemeHandler? It cannot intercept schemes like https, http, or file, nor can it intercept custom schemes. Are there any alternative solutions?