“file uri scheme”

Thank you for your post. When utilizing Universal Links to initiate a call to your application, the delegate that will be invoked in SwiftUI is: func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) { You can see that and how it works in the link: https://developer.apple.com/documentation/xcode/supporting-universal-links-in-your-app In case you are using deep linking to call your app, how have you registered the link in the info.plist? Scene Matching Rules: The handlesExternalEvents(matching:) modifier is used to specify which external events a scene should respond to. Ensure Correct URL Schemes: Double-check that the URL schemes you're trying to handle match exactly with what your app is set up to receive. For deep links like Companion://, ensure that this scheme is properly registered in your Info.plist under the CFBundleURLTypes key.
xml
 Review Scene Initialization: Your URLHandlerScene is initialized with a tem

Thank you! I should have noticed that. For the benefit of anyone else reading this, I have just experimented as follows. Create a file called lldbinit containing the single line settings set target.process.thread.step-avoid-regexp ^std::|^string:: Place it in the same directory as my .xcodeproj file In the field you mentioned in Product > Scheme > Info, I set the LLDB Init File field to $(SRCROOT)/lldbinit And indeed, when single-stepping, it now steps over functions in the string namespace instead of stepping into them.

The problem seems to be that extension targets that contain swift code aren't being handled properly.There's a workaround for this given in stackoverflow:You can put the following in your scheme so that it executes with every build:rm -rf ~/Library/Developer/Xcode/DerivedData/YourAppName-*/Build/Products/Debug-iphoneos/com.yourcompany.Name.extension.*Or, alternatively:touch ${PROJECT_DIR}/SOME SWIFT FILE IN EXTENSION.SWIFTYou need to add either of these, making adjustments for your particular project of course, here:Edit scheme... > Expand the Run mode in the sidebar > Pre-actions > Click '+' > New Run Script Action.It doesn't solve the underlying issue, but perhaps Apple will if they recieve bug reports.

Update: It’s better to use preferredColorScheme(), otherwise you need to style the status bar and some swiftui view’s don’t style properly with colorScheme(). So, my strategy is to cache the current device color scheme on load (by reading the .colorScheme environment variable) and basically revert the color scheme to that when the end user wants to go back to ‘auto’ mode. However, it seems that you ultimately need to pass nil to preferredColorScheme() to react to system color scheme changes (this isn’t documented), so you can kick off a background task to set this to nil after you revert to the cached original color scheme. The only edge case where this doesn’t set the correct color scheme is if the system color scheme changes after your app launched.

Go to Product -> Scheme -> Edit Scheme. Select Build in left side column and uncheck Find implicit dependencies But this flag should remain checked when you are building the project for first time..This workaround works great.One thing I notice is that I have to do a clean before the first build, otherwise won't work. After first build, uncheck Find implicit dependencies. The following 10 builds take no more than 30s 😉 . Unfortunately, after about 10 builds, it will start recompiling all swift files. Not sure if some changes I made trigger recompile or something else.

This is driven by the Optimization Level setting in the build settings for the target that contains the file you're editing. One of two things is happening… That value accidentally got set to something other than Onone for your debug build The scheme you're using has a configuration set that isn't your debug one. By default, projects come with a Debug and Release config. The Debug config is configured to build Onone, which means without optimizations. And the Release config is configured to build with optimizations. You just need to double check the build configuration selected for your scheme is your debug (usually Debug) one.

Sorry I didn’t reply sooner. At the time this thread started I wasn’t supporting universal links. [quote='763107021, kariaduu, /thread/763107, /profile/kariaduu'] Does hide app feature support custom URL scheme and universal link? [/quote] Another developer filed a bug about this (FB14973639) and the conclusion there is that this is behaving correctly. When an app is hidden, the system behaves as if the app isn’t installed. This affects a variety of features, including URL schemes and universal links. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I've the same problem. Preview on iOs scheme is working fine but if I switch to macOS scheme I got the same error. Did you find a fix?

You can disable that log with: 1 - From Xcode menu open: Product > Scheme > Edit Scheme 2 - On your Environment Variables set OS_ACTIVITY_MODE = disable

I resolved this issue by moving my pre-action and post-action bash scripts in the Build step of my scheme to scripts in the Build Phase. I added the following pre-action script in the Build step of each configuration.# TEST corresponds to the current Xcode scheme (Test). environmentFile=${PROJECT_DIR}/BuildProcess/CurrentEnvironment.txt echo TEST > $environmentFileI check my CurrentEnvironment.txt file to determine which configuration is active from the Build Phase scripts. I don't know how else to determine the active configuration from a Build Phase Run Script. If anyone knows of a better way, please respond.

This is a different issue, which a long-standing bug in Xcode Intelligence. Many model providers don't support the /v1/models uri, and Xcode chokes on it. You can probably work around the problem with a proxy like tingly-box, but it's one more thing to set up.

I have an app which basically download a file, and when it finish it sends a callback to the first applet url = URL(string: mainapp://downloaded-finished?now=true) NSWorkspace.shared.open(url!) NSApp.terminate(nil)At this point the alert popups stating that there is no app which is able to open that url scheme