“file uri scheme”

Select the phone scheme first, then select the watch scheme.

Thanks for your reply. I am creating a custom playlists (m3u8) & passing it to player and it is working fine with the custom scheme. In this method shouldWaitForLoadingOfRequestedResource when there is a call for ts segment with the custom scheme . I am replacing the custom scheme with the https. NSURLRequest *redirect = nil; NSString *url = loadingRequest.request.URL.absoluteString; NSRange tldr = [url rangeOfString:@//]; if (![url hasPrefix:@http] && tldr.location != NSNotFound) { url = [url stringByReplacingCharactersInRange:NSMakeRange(0, tldr.location) withString:@https:]; } redirect = [NSURLRequest requestWithURL:[NSURL URLWithString:url]]; [loadingRequest setRedirect:redirect]; NSHTTPURLResponse *response = [[NSHTTPURLResponse alloc] initWithURL:[redirect URL] statusCode:302 HTTPVersion:nil headerFields:nil]; [loadingRequest setResponse:response]; [loadingRequest finishLoading]; and it is working fine .. My question is how I can pass downloaded ts file. i

I have a ton of issues Importing and Exporting Localisation files, and have burnt too many evenings ! I usually resort to the XCode command line , that seems pretty reliable .... I do a clean build maybe -SkipMacroValidation helps I cant recall ! /usr/bin/xcodebuild -sdk iphoneos -skipMacroValidation -configuration Debug -workspace my.xcworkspace -scheme myScheme build CODE_SIGNING_ALLOWED=NO Then an Import or export /usr/bin/xcodebuild -sdk iphoneos -configuration Release -workspace my.xcworkspace -scheme myScheme -importLocalizations -localizationPath path-to/my.xcloc CODE_SIGNING_ALLOWED=NO

Are you trying to submit the archive build using the Watch scheme or the iOS scheme?

I may have found a workaround, detailed here Confirmed to fix FirebaseAnalytics installed via SPM, now my watchOS previews work. Not sure why this isn't default, only annoying thing is having to switch schemes for the relevant file, but not a huge breaker.

This would appear to be a content authoring issue or .m3u8 playlist issue. For debugging purposes only, to determine if it is a content authoring issue we recommend you set your EXT-X-KEY tag KEYFORMAT attribute in the .m3u8 playlist to identity instead of com.apple.streamingkeydelivery, add the initialization vector (IV) of the key you are using to the IV attribute, and set the URI attribute to an http URL pointing to a (16-byte) resource containing only the raw, unencrypted AES key. For example, instead of something like this:#EXT-X-KEY:METHOD=SAMPLE-AES,URI=skd://key67,KEYFORMAT=com.apple.streamingkeydelivery,KEYFORMATVERSIONS=1do something like this:#EXT-X-KEY:METHOD=SAMPLE-AES,URI=http://mysite.com/my16ByteKey.bin,KEYFORMAT=identity,IV=0xA30FE123ECBF1BE323A775A119C553BCand make your 16-byte key available on your mysite.com web server.This allows the client to receive the same content, but instead of decrypting it with FairPlay Streaming it decrypts it with a clear text AES key

Sad nobody responded.What I ended up doing was creating several Core Data configurations:* Cache* Cloud* LocalCloud of course has the syncing enabled on it. So in your scenario, users can start off on Local and have it sync against the Cloud configuration in the background. Are you actually storing the entire file contents within Core Data? If so, you might want to move to a model of storing just a URI to an iCloud document, after-which a user accessing it can trigger a separate iCloud sync.I'm also fairly sure I saw documentation that there is a hard restraint on cloudkit record sizes as well.

FWIW I ran into this issue today on Xcode 26.6. What worked for me was selecting the target scheme in Product > Scheme > {select target scheme}. This seemed to trick it into associating it with the correct bundle ID

It sounds like you've performed the right steps: Create the .storekit file Add the product metadata to the file Select the .storekit configuration file in your scheme's run options Run the app If you're not seeing it at this point, would you be able to collect a sysdiagnose - https://download.developer.apple.com/OS_X/OS_X_Logs/sysdiagnose_Logging_Instructions.pdf and then submit feedback - https://feedbackassistant.apple.com with that sysdiagnose attached? If you reply with the feedback ID we can take a look at it.