file uri scheme

Thank you for your post. If you disagree with the outcome of the review, we recommend submitting an appeal to the App Review Board. When filing your appeal, make sure to: Provide specific reasons why you believe your app complies with the App Review Guidelines. Submit only one appeal per rejection. Respond to any requests for additional information before submitting an appeal. Once you have submitted the appeal we can escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they've completed their investigation.

Hi, I have put together a pair of unit tests that run the same scenario against two separate language models: the Apple Foundation base model, my fine-tuned adapter model. While both are able to successfully complete a first prompt/reply turn, the LanguageModelSession that is running against the adapter model runs out of context window in turn 2. A very important nuance is that while both models operate with the same system prompt: a) for the unit test running against the base model, the system prompt is passed as instructions when instantiating the LanguageModelSession b) in the unit test running against the adapter model, the system prompt is baked into the training data. Here's the link to the analysis of the behaviour of the two tests and how they differ (compiled by Claude, as you'll no doubt detect from the superb over-confidence on display that is typical of AI agents) : https://github.com/MAOShea/Hello-World-Tools-Adapter-SwiftUI/blob/main/SUPPORT_REQUEST_TranscriptStorageDifference.md The two log files

More Context: Xcode 26.1.1 New standalone watchOS project - default settings. There is a project with two targets - an iOS target and a watchOS target. The iOS target is at default - no code added or taken away all certificates and profiles point to my distribution certificate and provisioning. The bundle_id's seem good. The Project and ios share a bundle id of com.myteam.myapp The watchOS bundle id is com.myteam.myapp.watchkitapp There are identifiers for both in App Store Connect. The app compiles and runs on the simulator with no errors, all sizes, all languages. I do not have a watch connected to the account, but the code has been tested and I can't imagine that the lack of a physical device is causing the problem The scheme has the 3 archs in top to botton project, ios, watchOS - all marked to do everything they can and everything I see is marked to release. This is my first swift program and xcode experience, so I am confident that the error is my understanding of the workflow. thank you anyone

[quote='866786022, DTS Engineer, /thread/807112?answerId=866786022#866786022'] Have either of your filed a bug about this yet? If so, please post the bug number. [/quote] Yes, I have reported a bug with this number: FB20987979

Here is the crash file that you requested, it is similar to the macos 12 one com.dci-network-extension_macos-11.txt

[quote='866620022, Apple_Fox, /thread/807599?answerId=866620022#866620022, /profile/Apple_Fox'] I do use URLsession. [/quote] OK. Then let’s use this thread to focus on the networking side of things. Once you’ve got that working, you can start a new thread with an appropriate subtopic and tags for your next step. URLSession is a very flexible API, so there are numerous ways you might use it to download a file. However, let’s explore a simple form. Imagine you have a button like this: Button(Download) { Task { await runDownload() } } That calls the runDownload() function, which looks like this: func runDownload() async { do { print(will run download) let url = URL(string: https://example.com)! let request = URLRequest(url: url, cachePolicy: .reloadIgnoringLocalCacheData, timeoutInterval: 60.0) let (downloadURL, response) = try await URLSession.shared.download(for: request) let httpResponse = response as! HTTPURLResponse print(did run download, status: (httpResponse.statusCode), downloadURL: (downloadU

Afogh, ehale, Thanks both you for the extra info. Have either of your filed a bug about this yet? If so, please post the bug number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I update to the latest Xcode : Version 26.1.1 (17B100) Toolchain: Swift 6.2 Release 2025-09-11 (a) and MacOS to the latest : 26.1 (25B78) and still have the same crash problem, I give the crash report to an AI to summarize it : Primary Issue Assertion Failure in Scheme Execution: The crash occurred during scheme execution operations, specifically when Xcode was trying to create an execution operation for running a scheme. Key Technical Details Crash Location Thread 0 (main thread) crashed with SIGABRT (Abort trap: 6) Trigger: Assertion failure in IDEScheme class Specific Method: -[IDEScheme _executionOperationForSchemeOperationParameters:build:onlyBuild:buildParameters:title:buildLog:dontActuallyRunCommands:restorePersistedBuildResults:deviceAvailableChecker:error:actionCallbackBlock:] Crash Sequence Assertion triggered in IDEScheme operations Assertion handler called abort() Main thread terminated with abort signal The crash appears to be an internal Xcode assertion triggered by in

[quote='807805021, 1024jp, /thread/807805, /profile/1024jp'] I’ve already filed this issue: FB21087054 [/quote] Thanks. That’s definitely the best path forward for this. It’s hard to think of a way to work around given that a) none of your code is running, and b) it affects system apps. This is likely fallout from a general effort to stop apps stealing focus from other apps. Check out the yieldActivation(toApplicationWithBundleIdentifier:) and other related method for more background on that. However, Terminal is the frontmost app, and it should be the responsible code for any command-line tools that you run, so I would expect this to work. And it does work most of the time, hence my comment that a bug report was the best path here. If you’re able to reproduce not-returning case, a sysdiagnose log from that might yield a useful insight. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thank you for the response. I've completed all the requested debugging steps nothing worked. I think it is an issue on your system where the license has not been activated yet. Steps Completed: App reinstallation: I deleted the app, reinstalled it, and ran it. The app successfully prompts for and receives camera access permission. Debug print statements: I added print statements to track execution flow: In CameraSessionManager.runCameraFrameProvider: Camera authorization is GRANTED Provider STARTS successfully Provider state remains initialized (never transitions to running) In CameraSessionManager.observeCameraFrameUpdates: No camera formats available from CameraVideoFormat.supportedVideoFormats() Code never reaches leftCameraFeed.update because no formats are returned Current setup verified: Enterprise entitlement com.apple.developer.arkit.main-camera-access.allow is present in provisioning profile Enterprise.license file (can share ID via email if you require it) is embedded in app bundle under Co

Hi @vision_pro_developer2000 Thanks for bringing this to our attention. While I investigate, I'd appreciate it if you can do some or all of the following: Delete the app, reinstall it, then run it and tell me if the app prompts you for permission to access the main camera. Add some print statements to the app to isolate the point of failure. Tell me how far you get. Specifically, in CameraSessionManager.runCameraFrameProvider determine if the provider starts. In CameraSessionManager.observeCameraFrameUpdates determine if the code reaches leftCameraFeed.update. File a bug report using Feedback Assistant, attach a sysdiagnose, and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating your bug report.