Search results for

file uri scheme

78,515 results found

Post

Replies

Boosts

Views

Activity

Reply to Can I save data to an App Group container from a ILClassificationRequest classifier?
Thanks very much, Kevin. It does seem like a bit of a miss that you can send the data off-device to train a filter, but can't do so on-device, especially given all the new on-device ML support. Perhaps there's a good reason for it. The issue here is that, for obvious reasons, the user’s message data is considered particularly sensitive. Sending it off-device is obviously a serious concern, but if that's going to happen, the best way to mitigate that is by minimizing the ability to relate messages to each other... and the best way to ensure that is to ensure that the extension doesn't have any content to relate or share. That leads to here: but if not, I'd love to be able to do this in a future version. I don't know if it's feasible or not, but if you're willing to commit being ENTIRELY on-device, the obvious alternative here would be to allow you to store data but completely disable all network access. If that's an approach you'd be interested in implementing, then I'd recommend filing a bug asking f
Topic: App & System Services SubTopic: Core OS Tags:
2w
Clean up render files saved to PHContentEditingOutput.renderedContentURL
I discovered when editing photos with the PhotoKit API, PHContentEditingOutput's renderedContentURL is a file in the app container's tmp directory with a filename that seems to follow the format render..JPG, and that file does not get deleted if the edit does not complete successfully (the user cancels the edit request, an error occurs, the app crashes, etc). I understand the system is supposed to automatically delete tmp files every once in a while, but some users are noticing my app's Documents & Data inflates, so I'm considering deleting these render files each time the app is launched. But I don't want to delete everything in the tmp directory as there could possibly be other data in there. What's the best way to remove those temporary files? Does the filename always start with render. no matter the device language? I thought I'd delete files in NSTemporaryDirectory() with that prefix but then I discovered in Mac Catalyst the location is not the tm
0
0
45
2w
tensorflow 2.20 broken support
Hi, testing latest tensorflow-metal plugin with tensorflow 2.20 doesn't work.. using python Python 3.12.11 (main, Jun 3 2025, 15:41:47) [Clang 17.0.0 (clang-1700.0.13.3)] on darwin simple testing shows error: import tensorflow as tf Traceback (most recent call last): File , line 1, in File /Users/obg/npu/venv-tf/lib/python3.12/site-packages/tensorflow/init.py, line 438, in _ll.load_library(_plugin_dir) File /Users/obg/npu/venv-tf/lib/python3.12/site-packages/tensorflow/python/framework/load_library.py, line 151, in load_library py_tf.TF_LoadLibrary(lib) tensorflow.python.framework.errors_impl.NotFoundError: dlopen(/Users/obg/npu/venv-tf/lib/python3.12/site-packages/tensorflow-plugins/libmetal_plugin.dylib, 0x0006): Library not loaded: @rpath/_pywrap_tensorflow_internal.so Referenced from: <8B62586B-B082-3113-93AB-FD766A9960AE> /Users/obg/npu/venv-tf/lib/python3.12/site-packages/tensorflow-plugins/libmetal_plugin.dylib Reason: tried: '/Users/obg/npu/venv-tf/lib/python3.12/site-
1
0
396
2w
Issue with StoreKit 2 Purchases: "unfinalized statements / unfinished backups" SQLite Crash
Hi, I’m running into a persistent error while implementing StoreKit 2 renewable subscriptions in my SwiftUI app. Context I have a two-screen flow: Screen 1: user selects a subscription plan (monthly / yearly). Screen 2: user fills out personal information and taps Subscribe that triggers the purchase function. On first launch or the first couple of purchases (on both Storekit's local and Sandbox testing), everything works fine. The App Store popup appears, the purchase goes through, and I get the transaction result. But after a few runs (3rd or 4th purchase attempt onward), my app crashes the moment the App Store purchase popup appears. Error Logs When the crash happens, the console shows: `unable to close due to unfinalized statements or unfinished backups BUG IN CLIENT OF libsqlite3.dylib: database integrity compromised by API violation: vnode unlinked while in use: /private/var/mobile/Containers/Data/Application/D8D97A11-DF06-4EF2-AC55-138C4739A167/Library/d6d2e85a60f0480c4c17834eeb827a14_MPDB.sqlite inval
1
0
61
2w
Reply to ProgressView Tint doesn't work on macOS
Thank you for sharing your experience. I believe that there may have been an issue with a beta? But you are currently using macOS 26.0.1. Could you please provide a simple, focused project and file a bug report? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
2w
Reply to Xcode 26.0 unknown type name 'sqlite3_context'
The file shown in your screenshot is part of the iOS SDK, so it does not normally have compile errors like this. That indicates that the problem is elsewhere in your build configuration, and this file is an innocent victim of a problem elsewhere. I see a build error that says failed to emit precompiled module, so maybe start there and work backwards. Since your project involves Cocoapods, it's possible that tool's configuration is also adding to this issue, so you should work to determine if their configuration set up by their tool is part of the source here, and if that turns out to be the case, you'll want to get in contact with their support resources. — Ed Ford,  DTS Engineer
2w
SSO Extension Fails XPC Connection to System Daemon (mach-lookup exception used)
Hello, I'm running into an issue with a complex macOS application (non-AppStore) structure involving an unsandboxed system daemon and a sandboxed SSO Extension attempting to communicate via XPC Mach service. The macOS app is composed of three main components: Main App: unsandboxed, standard macOS application. System Daemon: unsandboxed executable installed with a .plist to /Library/LaunchDaemons/ and loaded by launchd. It exposes an XPC Mach Service. SSO Extension: a sandboxed Authentication Services Extension (ASAuthorizationProviderExtension). Main App to System Daemon communication works perfectly. The unsandboxed main app can successfully create and use an XPC connection to the System Daemon's Mach service. But SSO Extension cannot establish an XPC connection to the System Daemon's Mach service, despite using the recommended temporary exception entitlement. I have added the following entitlement to the SSO Extension's entitlements file: com.apple.security.temporary-exception.mach-lookup.global-na
2
0
77
2w
Reply to The operation couldn’t be completed. (Mach error -308 - (ipc/mig) server died)
Thank you for your assistance. The Simulator only has a Device menu, which does not provide any other options to change devices. Xcode, on the other hand, allows you to change devices in the target. Therefore, let’s attempt to identify the root cause of this issue. To do so, we should start by creating a reproducible case and a crash file that can be analyzed or at least used to generate a bug report. If you have the mentioned crash file. Kindly submit a comprehensive crash report, adhering to the guidelines outlined in Posting a Crash Report. https://developer.apple.com/forums/thread/688669 If not a reproducible screen recording will be appreciated as well so I can reproduce it in my machine. Thanks again for all your help. Albert Pascual
  Worldwide Developer Relations.
2w
Reply to xcodebuild -exportLocalizations Fails Due to Cross-Platform Dependencies
Hi - thanks for the quick response. I'll try to answer as best as I can. Could you tell me more about these watchOS targets? My primary curiosity is how they are able to build successfully even during a normal build, if their dependencies do not support watchOS. I mentioned at the bottom of my original post that our app is [a mixture of] SPM packages and traditional target structure. This is mostly because SPM was introduced after our app was already published and created. We've slowly been migrating old features to SPM, and new features get added to SPM. The reason we love SPM is it introduces modularity for us, and enables greater code sharing. The way we decided to structure SPM within the context of all of our targets is one shared Package.swift file. This is because so many of our targets share the same code, it seemed easier at the time to keep all our various libraries within one SPM package (I hope that makes sense). So our one Package.swift declares all platforms like this: platforms: [ .iOS
2w
Reply to CarPlay Image Issue on iPhone 17?
Thank you for your post. For help with the CarPlay , please post in the Apple Support Community. The Apple Developer Forums are for questions about APIs and features intended specifically for developers. https://discussions.apple.com/welcome If you are using a beta version of iOS (please provide the version and build) with CarPlay , please file bug reports through Feedback Assistant. https://feedbackassistant.apple.com/ Hope this helps and you find the solution quickly. Albert Pascual
  Worldwide Developer Relations.
Topic: Community SubTopic: Apple Developers Tags:
2w
Reply to Issue with Rendering Annotations Outside the page bounds
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: UI Frameworks SubTopic: UIKit Tags:
2w
Reply to AlarmKit alarm UI strings are lost after updating OS
It turns out the situation is worse than I thought: it's not the OS update that triggers the bug, but merely restarting the device! If I schedule an alarm with the above code and then restart my device, the alarm triggers at the correct time, but the UI shows the localization keys instead of the strings. I just installed the iOS 26.1 beta (23B5044I) and it's still broken, so I've filed a bug report: FB20472264 As a temporary workaround, I will set my localization keys to English language strings.
2w
Reply to Core Text omits all remaining content and breaks rendering when truncation is enabled and after encountering a line containing only spaces
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: UI Frameworks SubTopic: General Tags:
2w
Reply to Metal 4 support in iOS simulator
Thanks for the details regarding this. I tried import Metal in the swift test, as well as the following Objective C test code: #import ViewController.h #import Metal/Metal.h @interface ViewController () @property id commandBuffer; @property id commandQueue; @end @implementation ViewController - (void)viewDidLoad { [super viewDidLoad]; // Do any additional setup after loading the view. } @end No dice with this either. I'll file the bug, thanks for looking into this!
Topic: Graphics & Games SubTopic: Metal Tags:
2w
Reply to Apple Pay JS API - applePayCapabilities no longer working
This smells like a Safari-side change/regression in the capability probe, not in the payment sheet itself. Treat applePayCapabilities() as advisory only for now. Implement a graceful fallback: always show the button when Apple Pay is supported, then try to launch a session. Use canMakePayments() (and optionally canMakePaymentsWithActiveCard) only to influence prominence, not eligibility. This is consistent with Apple’s guidance and long-standing WebKit advice. File a bug with reproducibles via Feedback Assistant. Assume this is a Safari capability-probe issue (and possibly anti-fingerprinting collateral) rather than your integration. Don’t block Apple Pay on the probe; keep the button visible and let the session tell you the truth. This both fixes your users today and aligns you with Apple/WebKit’s recommended UX.
Topic: Safari & Web SubTopic: General Tags:
2w