Search results for

file uri scheme

79,845 results found

Post

Replies

Boosts

Views

Activity

Reply to Having trouble with USD material not showing correct color
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:
2w
Reply to Declared Age Range: How to support age verification on iOS < 26?
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:
2w
Reply to DEXT (IOUserSCSIParallelInterfaceController): Direct I/O Succeeds, but Buffered I/O Fails with Data Corruption on Large File Copies
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:
2w
Reply to URLRequest(url:cachePolicy:timeoutInterval:) started to crash in iOS 26
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:
2w
Reply to Concurrency warning in Translation API
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:
2w
Reply to Filter Packet Provider Cpu issue
None of this strikes me as particularly surprising. The packet path is extremely ‘hot’, so adding any work to it is costly. The best thing you can do to improve performance is to avoid the .delay verdict, but your test code is already doing that. Before I send you off to file a bug about this, I have a couple of things for you to check: Make sure you reproduce this on a ‘clean’ machine. I often see weird problems being reported by folks only for us to track it down to some enterprise security setup affecting their main work Mac. If you have any additional network debug logging enabled — see the various instructions on our Bug Reporting > Profiles and Logs page — make sure to disable that during your tests. Usually I test NE stuff on a VM, but in this case you’ll want to run your tests on real hardware. VMs are great, but one place where they differ from real machines is performance. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Networking Tags:
2w
Reply to System Information in macOS 26.2 RC no longer shows Wi-Fi SSIDs
[quote='809205021, vtsang2025, /thread/809205, /profile/vtsang2025'] Is it an expected behaviour or a bug in the Release Candidate? [/quote] I don’t think that actually matters, in that it’s still fundamentally the wrong behaviour )-: Please do file a bug about this. I’d appreciate you posting your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Networking Tags:
2w
Local Network Discovery Works in Debug but Not in TestFlight (Wi-Fi Speaker Connection Issue)
Hi team, I’m having an issue with my iOS app related to local network communication and connecting to a Wi-Fi speaker. My app works similar to the “4Stream” application. The speaker and the mobile device must be on the same Wi-Fi network so the app can discover and connect to the speaker. What’s happening: When I run the app directly from Xcode in debug mode, everything works perfectly. The speaker gets discovered. The speaker gets connected successfully. The connection flow completes without any problem. But when I upload the same build to TestFlight, the behaviour changes completely. The app gets stuck on the “Connecting…” screen. The speaker is not discovered. But the same code is working fine on Android It never moves forward from that state. So basically: Debug Mode: Speaker is detected and connected properly TestFlight: Stuck at “Connecting…”, speaker does NOT get connected This makes me believe something related to local network access, multicast, Wi-Fi info permissions, or Bonjour discovery is not bei
Topic: App & System Services SubTopic: Networking Tags:
1
0
139
2w
My File Provider Extension cannot be started sometimes
We use File Provider Extension in our main app, and it is working fine. We always call NSFileProviderManager.add(_:completionHandler:) function to start the extension, and NSFileProviderManager.disconnect(reason:options:completionHandler:) to temporarily quit the extension with the reason which will be shown in the Finder at the top of the FP domain folder. But sometimes, when the main app calls the above functions, the following issue cases occur, and the extension does not start/stop: The completionHandler function doesn't get called (As we noticed, we waited for 2 minutes. Then, we restarted the main app.) One of the following errors returned: i) The application cannot be used right now, ii) Couldn't communicate with the helper application, iii) No valid file provider found with identifier Here, the important thing is that restarting the main app once or twice clears the issue, and the extension starts. But it is frustrating to restart the app each time we get this issue. We want to know
Topic: App & System Services SubTopic: Core OS Tags:
1
0
633
2w
Reply to DeclaredAgeRange framework new cases and properties cause runtime crash with missing symbol
Thanks for filing FB21121092, and also for the neat shout out regarding how MetricKit aided your investigation here. As to FB21121092, your report made it into the iOS 26.2 RC Release Notes as an acknowledgement of this issue and how it affects developers using the DeclaredAgeRange APIs. There isn't anything that I can share here about the state of our investigation right now, but it is progressing, and I'll provide an update here for the community once I have more information to share. — Ed Ford,  DTS Engineer
Topic: App Store Distribution & Marketing SubTopic: General Tags:
2w
Reply to NSWorkspace openURL fails on file in iCloud Drive
@DTS Engineer Thank you for the detailed reply! It may take me a while to respond to all of your points, but here is a start: Yes, the issue here is that nothing (no app launch and/or document open) is happening. The target app is a copy of BBEdit in my ~/Applications folder. Using the open command to open the same text file with the same copy of BBEdit works fine. Regarding How did your app get that file URL? Is your app able to open the file? And is the file already downloaded or is it still dataless? The file is downloaded. My app gets the URL by drag and drop from the Finder. My app does not attempt to open the file on its own, it just forwards the URL to be opened by another app, BBEdit in this case, somewhat like what the Dock does. Dang, now all of a sudden it's working. Obviously I need to do a lot more testing.
Topic: App & System Services SubTopic: Core OS Tags:
2w