Is there a way to display a .icon file in SwiftUI? I want to show the app icon in the app itself but exporting and including the app icon as a PNG feels redundant. This would consume a lot of unnecessary storage especially when including a lot of alternative app icons. There has to be a better way Otherwise I would file a feedback for that Thank you
Search results for
file uri scheme
79,841 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Agree that this would be great; did you file a feedback @FPST ?
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
Hello, I'm trying to adopt the new BGContinuedProcessingTask API, but I'm having a little trouble imagining how the API authors intended it be used. I saw the WWDC talk, but it lacked higher-level details about how to integrate this API, and I can't find a sample project. I notice that we can list wildcard background task identifiers in our Info.plist files now, and it appears this is to be used with continued tasks - a user might start one video encoding, then while it is ongoing, enqueue another one from the same app, and these tasks would have identifiers such as MyApp.VideoEncoding.ABCD and MyApp.VideoEncoding.EFGH to distinguish them. When it comes to implementing this, is the expectation that we: a) Register a single handler for the wildcard pattern, which then figures out how to fulfil each request from the identifier of the passed-in task instance? Or b) Register a unique handler for each instance of the wildcard pattern? Since you can't unregister handlers, any resources captured by the hand
Yes. We confirmed that kIOMaximumSegmentByteCountWriteKey was correctly set to 65536 (64 KB), and kIOMaximumSegmentCountWriteKey was set to 129. Did you? Because I didn't find IOMaximumSegmentCountWrite or IOMaximumSegmentCountWrite in either of the files you uploaded. More to the point, the class reference for UserReportHBAConstraints lists these seven keys as required: kIOMaximumSegmentCountReadKey kIOMaximumSegmentCountWriteKey kIOMaximumSegmentByteCountReadKey kIOMaximumSegmentByteCountWriteKey kIOMinimumSegmentAlignmentByteCountKey kIOMaximumSegmentAddressableBitCountKey kIOMinimumHBADataAlignmentMaskKey Your DEXT should be defining all of them and, as far as I can tell, it isn't. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic:
App & System Services
SubTopic:
Drivers
Tags:
Sounds like either it's not working right or the documentation needs to be updated to explain how to get it working. 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:
App & System Services
SubTopic:
General
Tags:
Thank you for sharing your experience. It appears that you are encountering an unusual issue with Xcode not displaying recent projects. To resolve this, please ensure that both macOS and Xcode are updated to the latest versions compatible with your system. While you have mentioned your current versions, it is advisable to double-check for any minor updates. Could you kindly provide a screenshot of Xcode when you attempt to open the “Recents” folder using the “File” menu? Please note that the screenshot should display the contents of the “Recents” folder. File -> Open Recent Please indicate whether you observe any recent projects or if the list is completely empty. Albert Pascual
Worldwide Developer Relations.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Platforms: macOS 15.x (Sequoia), Intel-Based App type: Endpoint Security (ES) client, notarized Developer ID app + LaunchDaemon Goal: Boot-time ES client that runs on any Mac (managed or unmanaged) Summary Our ES client launches and functions when started manually (terminal), but when loaded as a LaunchDaemon it fails to initialize the ES connection with: (libEndpointSecurity.dylib) Failed to open service: 0xe00002d8: Caller lacks TCC authorization for Full Disk Access We can’t find a supported way to grant Full Disk Access (SystemPolicyAllFiles) to a system daemon on unmanaged Macs (no MDM). Local installation of a PPPC (TCC) profile is rejected as “must originate from a user-approved MDM server.” We’re seeking confirmation: Is MDM now the only supported path for a boot-time ES daemon that requires FDA? If so, what’s Apple’s recommended approach for unmanaged Macs? Environment & Artifacts Binary (path placeholder): /Library/Application Support///App/.app/Contents/MacOS/ Universal (x86_64 + arm64) Notariz
I do have one question, the URL links I have for connecting online are linked directly to docx files in the site rather than just the site itself. Is that something that would cause errors for downloading the documents rather than connecting to the site first then try pulling the documents?
Topic:
App & System Services
SubTopic:
Networking
Tags:
@ericD_TRI Fantastic, a USDA file is very helpful! I think I understand what is going on, and there is indeed a divergence in how Reality Composer Pro is rendering content vs. how Finder renders. See Validating feature support for USD files for more information, but the TLDR is that there are slight differences in the renderer used in Finder (Hydra Storm) and the renderer used in Reality Composer Pro (RealityKit), and these differences are causing your USDA to look correct in Finder while looking gray in RCP. However! Your USDA file looks strange, and there are things you can do to fix it. It looks like you've merged a physics material with a rendering material, and the physics fields are causing the material to break in Reality Composer Pro (but don't break in Finder). I'm not sure how you generated this USDA file (did you edit it by hand?) but try replacing the block starting with def Material material ( with this code, which is simpler: def Material material { token outp
Topic:
Spatial Computing
SubTopic:
Reality Composer Pro
Tags:
This is the usda file for the asset. There is a diffuse color listed in the Shader but it appears RealityKit only registers the default color of (0.18, 0.18, 0.18) (from here https://openusd.org/dev/spec_usdpreviewsurface.html) ( defaultPrim = Root upAxis = Z ) def Xform Root { def Xform Red_block ( apiSchemas = [PhysicsMassAPI, PhysicsRigidBodyAPI, PhysxRigidBodyAPI] ) { float physics:mass = 1 bool physxRigidBody:disableGravity = 0 bool physxRigidBody:retainAccelerations = 0 token ui:displayGroup = Material Graphs token ui:displayName = Red_block int ui:order = 1024 float3 xformOp:rotateXYZ = (0, -0, 0) float3 xformOp:scale = (1, 1, 1) double3 xformOp:translate = (0, 0, 0) uniform token[] xformOpOrder = [xformOp:translate, xformOp:rotateXYZ, xformOp:scale] def geometry { def Cube mesh ( apiSchemas = [PhysicsCollisionAPI, PhysxCollisionAPI, MaterialBindingAPI] ) { rel material:binding = ( bindMaterialAs = strongerThanDescendants ) rel material:binding:physics = ( bindMaterialAs = strongerThanDescen
Topic:
Spatial Computing
SubTopic:
Reality Composer Pro
Tags:
Thank you, Yes, I have filed a bug report FB21249476.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
This is not legal advice, nor a statement from Apple. I will share what I'm going to do in my apps and recommend to others. How I interpret 121.056 (B) (1) is basically, use the signals when they're available. If they're not available, you can't use them. You can't do the impossible. So if you have an app update that supports iOS 26, implement it there, and < 26 you simply can't. As a developer, it is impossible to use the age signals provided by the App Store if they don't exist. If you're not comfortable with this approach, file feedback asking for support on devices < 26. Hypothetically, if Apple were to add support to, say iOS 18, it would still be something like iOS 18.8.x or higher. I am closely following the OS Usage page and waiting for an update to show the adoption of 26. https://developer.apple.com/support/app-store/ For my specific usage, I'm moving my apps to 26+ for my updates. However, I have apps that include watch extensions, and an Apple Vision Pro target. This presents its ow
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
Hi Kevin, I have filed the bug report as requested. The Feedback ID is FB21256805. I've included the IORegistry dumps showing the missing keys when using the standard API versus the successful injection using the SetProperties workaround. To answer your specific question: Are you sure you're setting all of the required key set, particularly 'kIOMaximumSegmentByteCountWriteKey'? Yes. We confirmed that kIOMaximumSegmentByteCountWriteKey was correctly set to 65536 (64 KB), and kIOMaximumSegmentCountWriteKey was set to 129. Thanks again for your help in narrowing this down. Best Regards, Charles
Topic:
App & System Services
SubTopic:
Drivers
Tags:
Hi @DTS Engineer and thanks :) I hope that your boss will get you a iPhone 17 😅 I'm trying to attach the ips-file again. I added the.txt extension to make it possible to attach it. I hope it will not screw up and make it an inline text-box when I git 'Reply' 😬 Looking at the ips-file I found that it does not show the finding that Xcode show, e.g., Thread X: Use of deallocated memory but it then misses Memory allocated by Thread 1 and Memory deallocated by Thread 1, so I am not sure the ips-file is that useful for MTE :( CrashReport-2025-11-28-141148.ips.txt
Topic:
App & System Services
SubTopic:
Networking
Tags:
This is tricky. My best guess is that translationTask(_:action:) is missing all the magic concurrency decorations required to make this work nicely. To get this to build right now you can mark the closure as sendable, like so: .translationTask(configuration) { @Sendable session in do { try await session.prepareTranslation() } catch { // Handle any errors. } } This compiles in Xcode 26.1 using the Swift 6 language mode and: Approachable Concurrency enabled Default Actor Isolation set to MainActor Note I’m using prepareTranslation() in my examples because it’s simpler, and that makes it easier to focus on the core issue. The drawback to this is that you can no longer access main-actor-isolated state from the closure. You can work around that using MainActor.run(…): try await session.prepareTranslation() … no isolation … await MainActor.run { … main-actor isolated … } Clearly this is less than ideal and I encourage you to file a bug against… actually, I think it’d be best to file a bug against
Topic:
App & System Services
SubTopic:
General
Tags: