“file uri scheme”

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

Hi,The 'Host' parameter of the URI atrribute (in this example:- 'token'), can be retrirevd via the 'identifier' property of AVContentKeyRequest.This will work for Just In Time acquisition of the key(s).If you need to prefetch the keys, you will need to carry the assetId out of band or parse it from the playlist (EXT-X-KEY...)

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.

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

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...

The behavior you've described sounds like the scheme you're passing to ASWebAuthenticationSession doesn't match the scheme for the URL being redirected to. Please double check that they match. (Keep in mind that a scheme itself doesn't include any special characters, such as : or /.)

I thought reserved schemes like HTTP and HTTPS will not work if we use AVAssetResourceLoaderDelegate. It's great if these schemes also work with that mechanisms.

Actually it does the reason I didn't write https:// because site didn't allow me to write scheme that's why I write url without scheme.

[quote='806051022, DTS Engineer, /thread/764739?answerId=806051022#806051022'] What is the scheme here? [/quote] Scheme is name of my macros's target

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.

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

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! 👍