“file uri scheme”

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.

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.

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

Try creating a new scheme in which your tests are the only target. It worked for me. Also, ensure that your test target is part of your current scheme.

I was able to stop the crash by adding KEYFORMAT=indentity to the #EXT-X-KEY tag in the .m3u8 files. (I'm guessing the bug involves an Xcode assumption that we're using FairPlay for encryption when utilizing a custom url scheme.) Still can't get AVAssetResourceLoaderDelegate to fire in the Simulator, though...

I don't know what was the problem but I figured out how to solve it. Basically, you need to recreate the target. In my case, I was using the old approach with watchOS app and extension app. Now Xcode 14 offers only a single target - maybe that was the problem. Steps that I used: Copy all files from your watchOS app to another location. Delete folder, target, and schemes, remove all remainings from watchOS app. Add watchOS app target using new Xcode. Add copied files from step. 1 Configure build settings, signing, and assets (whatever you need). Very important: set bundle identifier prefixed by your iOS bundle identifier. Very important: set WKCompanionAppBundleIdentifier in info.plist that equals your iOS app bundle identifier. Super important: go to your main iOS app target, general tab, frameworks, libraries... and click + and add your watchOS app. Now I like to use first watchOS scheme to install watchOS app first, then change scheme and install iOS app. Now you

Here are some possibilities:— Wrong target membership for files that are in the project.— Incomplete or inconsistent designation of frameworks header files as private or public vs. project.— Improperly updated include or frameworks header paths in the build settings.— Improper file referencing styles for the frameworks (e.g. absolute where you need build-products-relative, etc)— Inconsistent or unexpected use of modules (off/on) for frameworks.— Incorrect or conflicting module names for frameworks (it got parameterized a couple of Xcodes ago).— Errors/inconsistencies in schemes.I'd suggest you try working through your targets individually, starting with the ones that have no other project framework dependencies, then moving on to the ones that depend on them. Check (or create) the scheme for each target, set it as the current scheme and make sure you can build each framework in turn.Worst case, you can start looking at the compiler invocation lines for steps in the

I'm sorry, I didn't explain. Just go to openradar . appspot . com and login with a Google account. I didn't put a link to avoid moderation. To simplify filing and duplicating bugs, use the excellent QuickRadar . com app. It not only allows you to file a bug simultaneously to Apple and OpenRadar but also supports the rdar URL scheme. If the respective bug is published on OpenRadar, it automatically fetches the information so you can file a dupe in just 2 seconds.

Edit scheme -> Test -> press the + button and add the test (choose test targets to add to this scheme)

Interesting... When creating a new project from scratch and then trying to add the extension, I've seen a dialog with the following message that hasn't shown when I was trying to add the extension in my other project: Activate “WidgetTestWidgetExtension” scheme? This scheme has been created for the “WidgetTestWidgetExtension” target. Choose Activate to use this scheme for building and debugging. Schemes can be chosen in the toolbar or Product menu. I was just trying to run the App's target because I didn't even had a scheme to run the extension's one... But if I manually create a scheme to run the extension's target, I get the same result. Yeah, I'd totally like to bump the deployment target, we might do soon, but for now, it is a requirement from the company so not much I can do there sadly... Thanks for having taken some time to look into this! 👍

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.

I figured it out guys. Never mind. For debugging, you should edit the current scheme and set the working directory to something easy to find, like a folder in your home directory. (Product / Scheme / Edit Scheme / Run / Options / Use Custom Working Directory)