file uri scheme

I figured it out. The scheme that I was using was originally intended to handle the WidgetKit Intent configuration. So in the scheme itself, it had a Siri Intent Query inside the run step. So all I had to do was create a new scheme that was intended to test the Widget, and the query was no longer there. It then ran without triggering it.

Hi there. Your Xcode Cloud build may be failing this way because the workflow is still looking for that scheme. Can you confirm that your workflow's build actions reference the correct scheme? Please ensure that you have pushed any changes to your scheme to relevant branches that your Xcode Cloud workflows build from.

Yes, with something like this ...xcodebuild test -scheme YourAppScheme -destination platform=iOS Simulator,OS=9.0,name=iPhone 6Replace your project's scheme name in for 'YourAppScheme'Used to be you had to export/share the scheme (go to manage schemes in Xcode) to get this to work. Not sure if that is still the case. Just a warning.You can play with the destination settings to pick different devices, etc.Cheers.

I haven't seen the same message till now.Me neither, although it seems likely that the “testable” mentioned here relates to the Xcode scheme.@dpeace1982, you should check to see if the tests referenced by your scheme (in Product > Scheme > Edit Scheme > Test > Info > Tests) make sense.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Xcode Product -> Scheme - > Edit Scheme- > Profile - >Info -> Build Configuration must be Debug checked

By default, StoreKit Testing in Xcode is disabled. After enabling this by selecting the StoreKit Configuration file for the scheme, you will then be able to complete purchases in both iOS and watchOS for this Backyard Birds project. For information see StoreKit Testing in Xcode. If you continue to have issues, please provide what errors you are seeing and how to reproduce them.

Turns out it is one scheme setting that leads to this error: Debug Executable Steps: Choose the problematic scheme Edit Scheme Choose Run Uncheck “Debug executable” Clean Derived Data: ⌘ Cmd + ↑ Shift + K Run the app again: ⌘ Cmd + R

I couldn’t find a deep link tag There is Universal Links, but that’s not entirely accurate because your focus is on URL schemes. For URL schemes I recommend Core Services, which is vague but at least it’s something I track (-: You’re asking about iOS, right? Because on macOS we have the activateFileViewerSelecting(_:) method an NSWorkspace. I have some general advice on this topic in this post, and the posts its links to. AFAIK none of the documented schemes do what you want. I recommend that you file a bug requesting an iOS equivalent to the above-mentioned NSWorkspace API. IMPORTANT Don’t ask for NSWorkspace as a whole. That’s unlikely to happen on iOS. Rather, focus on that specific API. 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

Delete and recreate the Scheme for your Project.1) Click on the Project Target Name at the top of the Xcode window.2) Select Manage Schemes and Highlight the Scheme Name and click the Minus Sign to Delete it.3) Click on the Project Target Name at the top of the Xcode window, Again.4) The Plus sign at the bottom of the Aut0 Create Scheme and select your project from the list that appears.This should fix your issue.

site didn't allow me to write scheme that's why I write url without scheme. I see. A really annoying restriction.

Check whether your runner scheme in Xcode also displays the simulators next to you physical devices? If not recreate the runner scheme by clicking New scheme .... The simulators should be available again. Otherwise delete derived data folder under Xcode > preferences > location