Posts under Spatial Computing topic

Post

Replies

Boosts

Views

Activity

visionOS 27: Enterprise license still reported as expired after updating to a build with a renewed Enterprise.license
Our visionOS enterprise app uses main camera access and barcode detection. Our Enterprise API license expired recently on 2026-11-01. We renewed it, got a new Enterprise.license (expires 2027-11-02), and shipped it in a new build. On visionOS 27, if the new build is installed as an update over the old one, EnterpriseLicenseDetails keeps reporting the old, expired license. All enterprise features stop working. A clean install of the same build reports the new license as valid. Environment Apple Vision Pro, visionOS 27 Xcode 27.0 Installed via [Xcode / TestFlight] Log: status=expired, expires=2026-11-01T00:00:00Z, bundledExpires=2027-11-02T22:57:46Z, approved=[barcode-detection, main-camera-access, shared-coordinate-space, window-body-follow]What we've checked Deleting the app and installing build fresh gives .valid with expiry 2027-11-02. The installed bundle definitely contains the renewed license. On visionOS 26, every version of the app works, including the old build. Impact Every customer who updates the app instead of deleting and reinstalling it loses all enterprise features. Reinstalling also deletes their local data. Questions Is the license cached at first install and not refreshed when the app is updated? Is there a supported way to make the system pick up a renewed license without a delete and reinstall? What should we do so the next renewal doesn't break existing installs?
0
1
161
2d
Why Does Apple Vision Pro Still Lack 3DoF / Head-Locked Display Support After Nearly 3 Years?
Why is this still not supported on Apple Vision Pro? For a premium device that has been on the market for nearly three years and costs thousands of dollars, it's difficult to understand why Apple still hasn't provided a basic option to disable spatial anchoring when it isn't needed. This limitation becomes particularly frustrating in moving environments such as cars, buses, trains, airplanes, and cruise ships. Users have repeatedly reported issues with virtual windows drifting, shifting, becoming unstable, or losing tracking entirely. Apple introduced Travel Mode to address some of these challenges, but reports of tracking problems persist, and certain environments remain unsupported. Why should something as simple as watching a movie or using a virtual monitor require constant 6DoF spatial tracking? Not every use case requires a fully spatial experience. Sometimes users simply want a stable virtual screen without the operating system constantly attempting to anchor it to their surroundings. At a minimum, visionOS should provide three display options: 6DoF Spatial Mode: The existing experience, with windows anchored to the physical environment. 3DoF Rotation-Only Mode: Virtual screens respond to head rotation without relying on positional tracking. Head-Locked Mode: A screen remains positioned directly in front of the user without requiring environmental anchoring. Other headsets have offered simplified tracking options for years. It's disappointing that a product at this price point still lacks comparable flexibility. Users shouldn't have to struggle with spatial tracking just to watch a movie, browse Safari, or use Mac Virtual Display, particularly when the hardware is capable of delivering an otherwise excellent viewing experience. Apple Vision Pro has been available for nearly three years. Why is such a fundamental display option still missing? Is there an actual technical limitation preventing Apple from implementing this, or has it simply not been prioritized? At this stage in the product's lifecycle, this shouldn't remain an unresolved limitation. Apple should provide users with greater control over display tracking rather than forcing every use case into the same spatial computing model. I'd like to hear whether Apple has any plans to address this in future visionOS releases.
2
0
670
3d
Some models such as 5.6-terra, 5.6-sol, 6.1-sol, 6.1-terra fail as Model Provider
Hello, I'm experimenting with the assistant in Reality Composer Pro 3.1. On the OpenAI dashboard I added an API key to a project. I was able to add my OpenAI as a Model Provider using the API key and configure RCP model list. Initially I used gpt-5.5 and it worked. I was able to generate some assets: 3D models, PBR materials, ShaderGraph shaders, and textures. gpt-5.5 runs into a high cost so I was suggested to use 6.1-terra or 6.1-sol, which are more cost effective. terra and sol do not work, the query is failed early and all I get is an error in the prompt. The feedback file generated contains this: ``` { "modelProvider" : "openai", "modelName" : "gpt-6.1-terra (openai)", "prompt" : "Create a 3d model of an art deco desk lamp, with textures. Green body, smokey glass shade.\n" } ``` "gpt-6.1-terra" does match the actual name of the model. In RCP3 I set-up the models like this: The error appears quite fast, in just a few seconds. I aso tested 5.6-terra or 5.6-sol, same result. In the OpenAI dashboard an 400 error is logged: ``` 400 - Invalid request Nov 16, 2026, 08:09 UTC rcp3-model-provider Cause: The request did not meet the endpoint's requirements. Solution: Check the request parameters against the API reference ``` (rcp3-model-provider is the OpenAI project name). In Usage I was able to see some of the queries, while others are not appearing (we are not sure the reason why some show up while others don't). I would like to debug this issue but ot sure where to start. Some hypothesis: - the request is malformed or not compatible with terra/sol models. - terra/sol models lack some feature that gpt-5.5 has, but which one I don't know. There is not much information on query formatting and recommended models. Any help is appreaciated.
6
0
422
3d
AVAudioSession interrupted with no .ended when a window changes under an open ImmersiveSpace
Title: AVAudioSession interrupted with no .ended when the window changes while an ImmersiveSpace is open Hi, I'm seeing an issue where an active voice call (mic capture + playback) goes silent as soon as the app enters its immersive experience. The system posts AVAudioSession.interruptionNotification with type .began, but .ended never arrives while the app stays in the foreground, so the audio never resumes on its own. Audio only comes back after the app goes inactive and active again (for example after leaving the immersive space). This looks like the same issue reported in https://developer.apple.com/forums/thread/761721 (2024), and it still reproduces on visionOS 26 and 27. Setup: App with a WindowGroup and an ImmersiveSpace. Voice runs on a WebRTC stack (LiveKit, AVAudioEngine-based) on top of AVAudioSession, configured as: category .playAndRecord, mode .videoChat, options [.mixWithOthers, .allowBluetoothHFP, .allowBluetoothA2DP, .allowAirPlay], then setActive(true). When the immersive space opens, an ARKitSession runs with WorldTrackingProvider, HandTrackingProvider and SharedCoordinateSpaceProvider. Steps to Reproduce: Start a voice call from the main window. Mic capture and playback both work. Open the ImmersiveSpace and replace the main window with another window (open the new window, dismiss the main one). Shortly after the space opens, interruptionNotification arrives with type .began and reason .default (0). The audio engine stops. Mic capture and playback both go silent. Expected: Audio keeps running when the window changes. If the system has to interrupt the session, .ended is posted so the app can resume. Actual: .began arrives with no matching .ended while the app remains in the foreground. Audio stays silent until the app goes inactive and active again. At that point .ended arrives with .shouldResume and the engine starts again. The same interruption sometimes hits the very first microphone start right after the session is activated, so the start times out. Nothing else in the app activates or deactivates the audio session at that point. Observation code: NotificationCenter.default.addObserver( forName: AVAudioSession.interruptionNotification, object: nil, queue: .main ) { note in let type = note.userInfo?[AVAudioSessionInterruptionTypeKey] as? UInt let reason = note.userInfo?[AVAudioSessionInterruptionReasonKey] as? UInt print("interruption type=\(String(describing: type)) reason=\(String(describing: reason))") // Logged: type=1 (.began), reason=0 (.default). No type=0 (.ended) while the app stays active. }Current workaround: On every interruptionNotification, and again on UIApplication.didBecomeActiveNotification, call setActive(true) and restart the audio engine if it isn't running. This restores audio while the immersive space stays open. Device: Apple Vision Pro visionOS version: visionOS 27.2 (24N120), also seen on visionOS 26.5 (23O471) Xcode version: Version 27.0 (27A266a) Questions: Is the app's audio session expected to be interrupted when a window closes or is replaced while an ImmersiveSpace is open? If so, why is no .ended posted while the app remains active, and is reactivating the session and restarting the engine the recommended way to resume? Thank you!
0
0
166
4d
Production LiDAR capture app affected by ARKit world-tracking drift on iOS 26.4+ (re: thread 827240) mitigation guidance and fix timeline?
Hello, and thank you for taking questions this week. We develop DeepWalk, a production App Store application that captures LiDAR depth, RGB, and ARKit camera poses while field technicians walk continuous outdoor routes (sidewalk and infrastructure assessment). Recorded ARCamera.transform values are used downstream for 3D reconstruction, so world-tracking accuracy directly determines our output quality. Problem: Beginning in early April 2026 and coinciding with the iOS 26.4 rollout across our device fleet, we observe directional, accumulating pose drift in recorded trajectories during normal walking motion. The behavior matches the regression reported in forum thread 827240 (world-tracking drift on LiDAR devices on iOS 26.4+, absent on non-LiDAR devices running identical code). Link to existing post here: https://developer.apple.com/forums/thread/827240 Our configuration is minimal: a default ARWorldTrackingConfiguration with frameSemantics = [.sceneDepth, .smoothedSceneDepth] and no other options set, running on a bare ARSession with a Metal renderer (no SceneKit/RealityKit). We measure drift directly from per-frame ARCamera.transform values, so the displacement appears in ARKit's pose output itself rather than in any rendering layer. The drift accumulates with walking distance and does not occur when the device is stationary. We've observed this across a large variety of devices (iPhone 15/16/17 Pro/Pro Max) on all iOS versions 26.4 or greater. We've also observed this on iPad Pros with updated firmware. Thread 827240 additionally reports that disabling autofocus, HDR, and plane detection and varying scene reconstruction and world alignment did not resolve it. Question Because depth capture is our core function, we cannot avoid engaging the LiDAR scanner, and we're not aware of a public API that adjusts its contribution to world tracking. We'd be grateful for guidance on three questions: Is this a known issue in iOS 26.4 and later? Did the LiDAR contribution to world tracking change in that release? For apps that require sceneDepth, is there any recommended session configuration, video format, or capture-side practice that reduces the drift in the interim? Is a fix planned, and if so, should we expect it in an iOS 26.x update or the iOS 27 cycle? This affects how we manage our deployed device fleet. We're happy to provide trajectory datasets, additional sysdiagnoses, or anything else useful. We have quantified drift-per-distance data across OS versions.
8
1
1.9k
5d
RoomPlan crash: com.apple.RoomScanCore.onlineFloorPlanGeneration EXC_BREAKPOINT
We're seeing a recurring crash inside RoomPlan during an active scan. All reports we have are on iOS 27; we haven't seen it on iOS 26 (Crashlytics for the last 90 days, Xcode Organizer going back further). The first report came in on October 1, 2026. None of our code is on the crashing thread. Feedback: FB25425119 (includes two fully symbolicated crash logs) Crash Crashed: com.apple.RoomScanCore.onlineFloorPlanGeneration EXC_BREAKPOINT (SIGTRAP) 0 RoomScanCore -[RSObjectAlign AlignWithWalls:openings:objectAsset:beautification:chairBeautification:] + 25068 1 RoomScanCore (anonymous namespace)::OptimizeBbox(...) + 168 2 RoomScanCore (anonymous namespace)::OptimizeBboxWithWall(...) + 412 3 RoomScanCore AlignBoxesToNearestWall(...) + 612 4 RoomScanCore -[RSObjectAlign AlignWithWalls:...] + 5992 5 RoomScanCore -[RSFloorPlanRender beautifyObjects:withFloorPlan:pointCloud:] + 212 6 RoomScanCore -[RSOnlineFloorPlanGenerator beautifyObjects:withFloorPlan:] + 116 7 RoomScanCore __40-[RSCaptureSession updateWithKeyframes:]_block_invoke_2 + 4176 8 libdispatch.dylib _dispatch_call_block_and_release + 32 The crash site is the same in every report. It happens while RoomPlan aligns detected objects (furniture) to the nearest wall during the live floor-plan update. Affected iOS 27.0, 27.0.1 and 27.2. No reports on iOS 26.x in our data. iPhone 15 Pro Max, iPhone 16 Pro, iPhone 16 Pro Max and iPhone 17 Pro. Setup RoomCaptureView, started with the default configuration: captureSession.run(configuration: RoomCaptureSession.Configuration()) The app is in the foreground during a normal scan. The main thread is idle at crash time. It happens in larger rooms (around 20 walls) and also within a few seconds of starting a new scan. Affected users often crash several times in a row. We can't reproduce it on demand. Questions Is this a known issue in RoomPlan on iOS 27? Is there a supported way to avoid it, for example by disabling object beautification, until a fix ships? Has anyone else seen this crash with RoomPlan on iOS 27?
1
0
864
1w
Eye tracking data access for researchers
Hi, Is there a way for researchers to get or request access to eye tracking data from the Apple Vision Pro within the boundaries of the app to be developed? I'm currently involved in research where access to eye tracking data would be beneficial (I'm aware of many existing discussions about this, but I was still wondering if there might be an option, particularly for research labs.) Thank you for your answer.
3
1
1.4k
1w
FoveatedStreamingSession headset and controller location smoothing, Velocity for OpenXR
Hi, We build a PC VR streaming app for Apple Vision Pro. It has two VR paths: our own stream (our transport, VideoToolbox decode, our compositor layer) and FoveatedStreamingSession with CloudXR, which we use for titles that benefit from foveation. On our own path we filter the head and controller poses and send velocity. Getting both right took a lot of on-device tuning, and they made a large difference to comfort and to physics-based games. On the FoveatedStreamingSession path, the pose path from tracking to the endpoint runs inside the system, so an app has no way to apply, adjust or even inspect either one. We would like to ask for that control. 1. Pose smoothing for the head and controllers What we measured on device: Vision Pro tracking picks up very small, heartbeat-rate motion (around 1.2 Hz, millimetre scale). Locally that is invisible. After a streaming round trip it comes back as a visible world shake, because the remote frame is rendered at a pose about 50 ms old and reprojection has to cover the difference. Our A/B tests showed the tremor is largely rotational. Reprojection did not fully absorb it at our latency: turning off only the rotation filter brought the shake back right away. What fixed it for us: a One-Euro filter on the head pose, applied on the client before the pose is sent, with the frame anchored at the exact pose it was rendered with, so reprojection still covers the gap to the real head at no added latency. The values we settled on after live tuning: ComponentMin cutoffBetaPosition0.1 Hz12Rotation0.5 Hz12The right values depended on the content, the user and the end-to-end latency, which is why we are asking for control rather than one fixed default. Controllers need their own settings, because the right balance between lag and steadiness differs between fast games and precise work such as aiming or drawing. What we would like on FoveatedStreamingSession: Separate smoothing settings for the head and for tracked accessories, with position and rotation set independently. A choice of system default, off, or custom parameters. A One-Euro style minimum cutoff plus speed coefficient would cover our case. Documentation of what filtering, if any, the system applies today, so apps don't filter on top of it. 2. Velocity for the head and controllers Physics titles (throws, grab-and-pull, swings) take their motion from the linear and angular velocity in the OpenXR space velocity (XrSpaceVelocity), not from changes in position. If velocity arrives as zero, throws drop at the user's feet. If it arrives noisy, the PC runtime's own extrapolation to photon time amplifies the noise, and the controllers shake at rest. We hit both cases on our own path. What fixed them: Pass the accessory anchor's velocity through. Set the pose time offset from the client's own prediction, so the PC side does not predict twice. Apply a small deadband (about 0.05 m/s linear and 10°/s angular, matching common open-source streamers). What we would like on FoveatedStreamingSession: Documentation of whether linear and angular velocity are sent to the endpoint for the head and for tracked accessories, and in which reference frame. We could not find a frame statement for AccessoryAnchor velocity in the docs or the SDK interface. Game title testing appears as though these values not being sent. App control over velocity: on/off, a gain, a deadband, and a filter (or the same smoothing settings as above). The prediction offset the session uses when it sends poses, so apps and endpoints can avoid predicting twice. 3. A possible API shape (only a sketch to try to convey the requested need) extension FoveatedStreamingSession { struct PoseFiltering: Sendable, Equatable { static var systemDefault: PoseFiltering { get } static var off: PoseFiltering { get } static func oneEuro(positionMinCutoff: Double, positionBeta: Double, rotationMinCutoff: Double, rotationBeta: Double) -> PoseFiltering } struct VelocityReporting: Sendable, Equatable { var isEnabled: Bool var linearGain: Float var angularGain: Float var linearDeadband: Float // m/s var angularDeadband: Float // rad/s var filtering: PoseFiltering } var headPoseFiltering: PoseFiltering { get set } var accessoryPoseFiltering: PoseFiltering { get set } var accessoryVelocityReporting: VelocityReporting { get set } var posePredictionInterval: TimeInterval { get } }Being able to change these during a session (not only before connect) would let users tune them from the app's own settings while wearing the headset, which is how we found our values.
2
0
613
1w
Built-in environments in the visionOS simulator
Should Environments like White Sands and Mount Hood work in the visionOS simulator? In a fresh visionOS 27.2 simulator, selecting an Environment from Home View does nothing. I saw the same behavior with visionOS 27.0. After selecting the Moon, Control Center still shows White Sands. Moving the immersion slider in Control Center changes the position of Device Hub’s sidebar slider, but that slider remains disabled and no environment appears. This happens before installing or running my app. The simulated room scenes work. The simulator logs show that the environment catalog downloads successfully, but the scenic assets are marked state=notPresent. Trying to increase immersion produces: Default environment identifier Wolf is no longer available on disk. Resetting to system default. Invalid environment Wolf requested, it does not exist or is not in correct state (Unavailable). Failed to load environment: Error Domain=RealityEnvironmentError Code=407 "Environment action not performed." (Wolf is the internal identifier for White Sands.) Is this an expected simulator limitation, a known issue, or is there a way to download and enable these environments?
1
0
395
1w
Reality Composer Pro exporting larger and larger .reality files for each reference usage
We've noticed something kind of odd related to the exported .reality file in Reality Composer Pro 3. Our exported .reality file seems to be increasing a lot in size just by referencing an imported asset or another entity in the scene. This contradicts everything we previously knew about references. Essentially it seems like our assets are being copied or duplicated on each export. Before you dive into the description of the issue, yes, I've already created feedback about this. I think it's a bug, but am willing to be corrected if this is an expected, if somewhat odd, behavior. The feedback number is FB25253483 I did a quick test with a single model (Earth.usdz from the RCP2 content library. Project A: RCPExportDupeIssues Phase 01 Created new project in RCP 3 Imported the file and added it to the default world entity Generated an Xcode linked project and used RCP3 to run the app in the simulator (this runs through the entire .reality export process.) Result: 48.4 MB Phase 02 Created AnotherScene entity Added the imported earth model to it Used RCP3 to run the app in the simulator Result: 64.5 MB Phase 03 I thought maybe if I added the earth import to a single entity and added that entity to the other two scenes, I might get some savings. This also increased the overall export size. Created EarthEntity Added the imported earth model to it Used RCP3 to run the app in the simulator Result: 80.7 MB Overall result: an RCP3 project with a single imported Earth asset, used in three otherwise empty scenes, ends up with a massive 80 MB. I even tried deleting the Earth import reference in the first two scenes. Even with only the Earth entity present, the export was still 80.7 MB. Project B: RCPExportNoDupes I tried a second project without ever adding the Earth import file to the first two scenes. I created a dedicated EarthEntity and only added that to the other two scenes. Created new project in RCP 3 Created EarthEntity Imported the file and added it to EarthEntity Added `EarthEntity to the default world entity Created AnotherScene entity and added `EarthEntity to it Generated an Xcode linked project and used RCP3 to run the app in the simulator (this runs through the entire .reality export process.) Result: 80.7 MB Apple: I provided zipped versions of the exports in the feedback item (FB25253483)
2
1
1.1k
1w
Can visionOS Performance Trace measure RealityKit frame deadlines without Instruments?
We have an immersive RealityView/RealityKit scene on Vision Pro and want to measure renderer frame deadlines, misses, and per-frame CPU/GPU timing without Instruments. Apple's “Performance Trace: visionOS” instructions describe collecting a sysdiagnose for Feedback after installing a temporary logging profile and restarting. We could not find a supported local readout or field map in those instructions. Does the archive contain attributable RealityKit renderer frame deadlines, completion or miss events, and per-frame CPU/GPU measurements? If so, what supported tool, command, or export can decode them without Instruments or xctrace? Which archive member and fields contain the measurements, and what are their clock, units, and app/scene/layer attribution? A small redacted decoded example would help us verify the method before another headset run. If the archive does not provide those measurements, is there another Apple-supported method for the existing RealityKit renderer?
2
0
429
2w
Presenting the system share sheet from a full ImmersiveSpace on visionOS 26
We are building a visionOS 26 app (deployment target visionOS 26.0). Inside a full immersive space, the user takes a spatial photo. The photo is shown on a RealityView attachment. We need the system share sheet( AirDrop, Messages, Mail, Copy, Save Image, and the item preview with Done) to appear when the user taps Share on that attachment. The immersive space is: ImmersiveSpace(id: "ImmersiveView") { ImmersiveView() } .immersionStyle(selection: $panoImageView, in: .full) .upperLimbVisibility(.visible) The review UI is a RealityView attachment, not a window: Attachment(id: "panoramaFrameCaptureReview") { PanoramaFrameCaptureReviewView(model: frameCapture) { guard let path = frameCapture.shareURL?.path else { return } dismissWindow(id: "PanoramaPhotoShare") Task { @MainActor in try? await Task.sleep(nanoseconds: 180_000_000) openWindow(id: "PanoramaPhotoShare", value: path) } } } The shared item is a stereo HEIC written with Image I/O (kCGImagePropertyGroupTypeStereoPair, left/right images, HEIF camera extrinsics and SimplifiedPinhole intrinsics). The same data displays correctly with ImagePresentationComponent and saves to Photos as a spatial photo. Share is the only part that fails. Attempt 1. ShareLink on the attachment Tapping Share does nothing. On entry to the immersive space the system logs: Presentations are not currently supported in Immersive contexts. Attempt 2. UIActivityViewController from the attachment’s hosting controller let activity = UIActivityViewController(activityItems: [fileURL], applicationActivities: nil) var presenter: UIViewController = self while let parent = presenter.parent { presenter = parent } presenter.present(activity, animated: true) presenter is UIHostingController<RootView>. The console then says: Skipping popover presentations transition, missing window or scene for <UIActivityViewController>. Failed to request default share mode for fileURL:...heic error:Error Domain=NSOSStatusErrorDomain Code=-10814 No share UI appears. presentedViewController is non-nil, so a “did it present?” check does not detect the failure. Attempt 3. A real WindowGroup whose only job is to present UIActivityViewController WindowGroup(id: "PanoramaPhotoShare", for: String.self) { path in if let path = path.wrappedValue { PanoramaPhotoShareWindow(path: path) } } .windowStyle(.plain) .defaultSize(width: 20, height: 20) .defaultWindowPlacement { _, _ in WindowPlacement(.utilityPanel) } struct PanoramaPhotoShareWindow: View { let path: String @Environment(.dismissWindow) private var dismissWindow var body: some View { PanoramaPhotoSharePresenter(url: URL(fileURLWithPath: path)) { dismissWindow(id: "PanoramaPhotoShare") } .frame(width: 8, height: 8) .background(.clear) } } final class PanoramaPhotoShareController: UIViewController { override func viewDidAppear(_ animated: Bool) { super.viewDidAppear(animated) guard view.window != nil, let url else { return } let activity = UIActivityViewController(activityItems: [url], applicationActivities: nil) activity.completionWithItemsHandler = { _, _, _, _ in self.onFinish?() } present(activity, animated: true) } } Tapping Share opens this window and the app crashes immediately. We removed the feature so users are not crashed. An earlier build that also put a ShareLink in that window logged: Attempt to present <UIActivityViewController> on <UIHostingController<...PanoramaPhotoShareWindow...>> which is already presenting <UIActivityViewController>. Question What is the supported way, on visionOS 26, to present the system share sheet while a .full ImmersiveSpace stays open? If a window is required, how should that window present the sheet without crashing, and without showing a second window that only contains another Share button?
1
0
769
2w
Improving metric scale consistency of ARWorldTrackingConfiguration on devices without LiDAR
We build a medical scanning app. A practitioner walks a slow orbit (~1 m radius, two laps, 25–35 s) around a standing subject while an ARSession runs, and we capture ~50 high-resolution stills with captureHighResolutionFrame. The ARKit camera poses for those frames are later used to set the metric scale of a photogrammetry reconstruction. We need the resulting scale to be within about 2 % of true. What we observe, measured against a printed A4 sheet on the floor in every scan: Devices with LiDAR (iPhone 16 Pro Max, iPad Pro), using the sceneDepth frame semantic as a check: scale within ±0.8 % across 11 sessions. Devices without LiDAR (iPhone 13, iPad 9th and 11th gen, plus non-LiDAR runs on the Pro devices): the world-frame metre is on average 2–3 % short of true, and varies by a further ±2 % from one session to the next, across 24 sessions in four rooms. Within a session the scale is stable: lap-to-lap variation is under 0.4 %. The error appears to be set during initialisation and held. Nothing we record about capture correlates with the error: time spent before capture, distance walked, vertical camera movement, orbit radius, rotation speed, tracking state, or the residual of our pose fit. Questions: Is there any session setup, initialisation practice, or motion during the first seconds of tracking that is known to improve the metric scale estimate on devices without LiDAR? Does the choice of video format, resolution or frame rate affect scale estimation? Is there any signal, beyond ARCamera.trackingState, that indicates how well scale has been determined for a session, so we could flag sessions rather than accept them? Does anything in the configuration above, in particular locking exposure on the capture device or using the high-resolution video format, work against tracking quality or scale?
1
0
912
2w
visionOS 27 beta 4 (24M5326g) stuck: update fails with MSU 806 MADownloadDaemonNotReady, all Apple services hang
My Apple Vision Pro is still on visionOS 27.0 beta 4 (24M5326g) and can't update or use any Apple service. Safari works. Software Update offers visionOS 27.2 (24N6120) but stays at "Update Requested". The OTAUpdate log shows: MobileSoftwareUpdateErrorDomain 806 "Failed to download update brain asset, MADownLoadResult:MADownloadDaemonNotReady". App Store can't connect, Apple TV and Games say a network connection is required, iCloud doesn't work, and Media & Purchases hangs at "Signing in to Apple Media Services". Other devices on the same network work normally. Reset All Settings didn't help. devicectl device sysdiagnose fails with CoreDeviceCLISupport.DiagnoseError 0. I don't have a Developer Strap. Has anyone recovered a Vision Pro stuck on an early beta like this without one? Filed as FB25386556.
0
0
447
3w
Reality kit Entities Appearing to Lag in a Full or Progressive Style Immersive Space When Opened with Environment Turned On
PLATFORM AND VERSION Vision OS Development environment: Xcode 16.2, macOS 15.2 Run-time configuration: visionOS 2.3 (On Real Device, Not simulator) Please someone confirm I'm not crazy and this issue is actually out of my control. Spent hours trying to fix my app and running profiles because thought it was an issue related to my apps performance. Finally considered chance it was issue with API itself and made sample app to isolate problem, and it still existed in it. The issue is when a model entity moves around in a full space that was launched when the system environment immersion was turned up before opening it, the entities looks very choppy as they move around. If you take off the headset while still in the space, and put it back on, this fixes it and then they move smoothly as they should. In addition, you can also leave the space, and then turn the system environment immersion all the way down before launching the full space again, this will also make the entity moves smoothly as it should. If you launch a mixed immersion style instead of a full immersion style, this issue never arrises. The issue only arrises if you launch the space with either a full style, or progressive style, while the system immersion level is turned on. STEPS TO REPRODUCE https://github.com/nathan-707/ChoppyEntitySample Open my test project, its a small, modified vision os project template that shows it clearly. otherwise: create immersive space with either full or progressive immersion style. setup a entity in kinematic mode, apply a velocity to it to make it pass over your head when the space appears. if you opened the space while the Apple Vision Pros system environment was turned up, the entity will look choppy. if you take the headset off while in the same space, and put it back on, it will fix the issue and it will look smooth. alternatively if you open the space with the system immersion environment all the way down, you will also not run into the issue. Again, issue also does not happen if space launched is in mixed style.
2
1
1.2k
3w
Immersive space sometimes opens with a broken world origin (world anchors fail with error 200, recenter times out)
Hi all, We're seeing an intermittent issue in a native SwiftUI + RealityKit app on Vision Pro (visionOS 27.0.1, still there on 27.2). When we open a mixed ImmersiveSpace, roughly 1 in 10–30 opens, everything ends up offset from where it should be. Sometimes it's 50 cm, sometimes several meters, sometimes it's rotated. Holding the Digital Crown to recenter fixes it immediately. We are attaching things to the camera, like we have a window following the user and that is offset in these rare cases which makes the app not usable. In the device logs, a good open looks like this: backboardd (recenter) Setting new world origin with anchor ... backboardd ARWorldTrackingProcessor: Added world anchor ... successfully (x4) backboardd (recenter) Finished (error: (null)) setting set new world origin ... A bad open looks like this: backboardd (recenter) Setting new world origin with anchor ... arkitd SLAMAnchorUpdate: Failed to add anchor request ... NSPOSIXErrorDomain Code=4 backboardd ARWorldTrackingProcessor: Failed to add world anchor ... com.apple.arkit Code=200 "Adding an object failed." (x4) backboardd (recenter) timeout exceeded. Forcing fade in. Like whenever the bad state occurs it is because adding a world anchor seems to fail. I haven't tested with visionOS26 but the same app didnt run into that problem ever. So the system seems to fail adding its own origin anchors, gives up after 2 seconds and shows the space anyway. Has anyone else run into this? And is there any way to detect it from the app or trigger a recenter in code? Thanks!
2
0
680
3w
High fidelity gaming on Apple Vision Pro
I'm looking to find the best setup for a game on AVP that gives the best quality environment with gameplay but there seems to be a mix of possible solutions each with their own drawback. My ideal scenario is a high fidelity room/environment while making use of the PS VR2 Sense controllers to track the user's hands and give them more inputs via the controllers. Eg they hold a weapon tracked to the controllers with the buttons able to use the weapon, shooting and hitting enemies in the room. I want to aim more for highest qualtiy gaming than cartoony so opted for foveated streaming from the Mac as my ideal, but this seems limited to only having some base inputs from the hands and no controller inputs for hand and positional tracking from the controller movement (as they need the data from the Vision Pro camera but the game is technically running on the Mac and streamed to the VP) The only real solution for what I want here is to go via RealityKit as a native Vision Pro app but this reduces the game quality I had in mind as the entire thing is now rendering on the VP instead of the Mac. Am I missing something here or is this a real limitation today? To reitarate I'm looking for: highest fidelity game quality (rendering as much as possible on the Mac) tracking the VR2 Sense controller's positions (to track a weapon) in 3D space
1
0
1.1k
3w
Async Entity(contentsOf:) is 15 to 20x slower while an ARView is rendering
While a non-AR ARView is on screen and rendering, await Entity(contentsOf:) takes about 26 s to load a 4.5 MB USDZ with 300 textured meshes. The same file loads in about 1.5 s with the synchronous Entity.load(contentsOf:), or with the async API while the view is hidden. iPhone 16 Pro, iOS 27.2Mac Catalyst, macOS 27.2await Entity(contentsOf:), view rendering22 to 26 s26 sEntity.load(contentsOf:), view rendering1.6 s1.1 to 1.7 sawait Entity(contentsOf:), view hidden1.4 s1.3 to 1.5 sModelEntity(contentsOf:) and Entity.loadAsync(contentsOf:) behave the same. A .reality file loads fast either way, and the iOS Simulator doesn't show it. A Time Profiler trace shows the main thread blocked in re::RenderThread::waitForFramePacing on every frame, so the @MainActor import only advances between frames. Neither workaround fits loading content into a scene the user is looking at: the sync load blocks the main thread, and hiding the view blanks it. Filed as FB25340264, with a sample project.
0
0
190
3w
visionOS 27: Enterprise license still reported as expired after updating to a build with a renewed Enterprise.license
Our visionOS enterprise app uses main camera access and barcode detection. Our Enterprise API license expired recently on 2026-11-01. We renewed it, got a new Enterprise.license (expires 2027-11-02), and shipped it in a new build. On visionOS 27, if the new build is installed as an update over the old one, EnterpriseLicenseDetails keeps reporting the old, expired license. All enterprise features stop working. A clean install of the same build reports the new license as valid. Environment Apple Vision Pro, visionOS 27 Xcode 27.0 Installed via [Xcode / TestFlight] Log: status=expired, expires=2026-11-01T00:00:00Z, bundledExpires=2027-11-02T22:57:46Z, approved=[barcode-detection, main-camera-access, shared-coordinate-space, window-body-follow]What we've checked Deleting the app and installing build fresh gives .valid with expiry 2027-11-02. The installed bundle definitely contains the renewed license. On visionOS 26, every version of the app works, including the old build. Impact Every customer who updates the app instead of deleting and reinstalling it loses all enterprise features. Reinstalling also deletes their local data. Questions Is the license cached at first install and not refreshed when the app is updated? Is there a supported way to make the system pick up a renewed license without a delete and reinstall? What should we do so the next renewal doesn't break existing installs?
Replies
0
Boosts
1
Views
161
Activity
2d
Why Does Apple Vision Pro Still Lack 3DoF / Head-Locked Display Support After Nearly 3 Years?
Why is this still not supported on Apple Vision Pro? For a premium device that has been on the market for nearly three years and costs thousands of dollars, it's difficult to understand why Apple still hasn't provided a basic option to disable spatial anchoring when it isn't needed. This limitation becomes particularly frustrating in moving environments such as cars, buses, trains, airplanes, and cruise ships. Users have repeatedly reported issues with virtual windows drifting, shifting, becoming unstable, or losing tracking entirely. Apple introduced Travel Mode to address some of these challenges, but reports of tracking problems persist, and certain environments remain unsupported. Why should something as simple as watching a movie or using a virtual monitor require constant 6DoF spatial tracking? Not every use case requires a fully spatial experience. Sometimes users simply want a stable virtual screen without the operating system constantly attempting to anchor it to their surroundings. At a minimum, visionOS should provide three display options: 6DoF Spatial Mode: The existing experience, with windows anchored to the physical environment. 3DoF Rotation-Only Mode: Virtual screens respond to head rotation without relying on positional tracking. Head-Locked Mode: A screen remains positioned directly in front of the user without requiring environmental anchoring. Other headsets have offered simplified tracking options for years. It's disappointing that a product at this price point still lacks comparable flexibility. Users shouldn't have to struggle with spatial tracking just to watch a movie, browse Safari, or use Mac Virtual Display, particularly when the hardware is capable of delivering an otherwise excellent viewing experience. Apple Vision Pro has been available for nearly three years. Why is such a fundamental display option still missing? Is there an actual technical limitation preventing Apple from implementing this, or has it simply not been prioritized? At this stage in the product's lifecycle, this shouldn't remain an unresolved limitation. Apple should provide users with greater control over display tracking rather than forcing every use case into the same spatial computing model. I'd like to hear whether Apple has any plans to address this in future visionOS releases.
Replies
2
Boosts
0
Views
670
Activity
3d
Some models such as 5.6-terra, 5.6-sol, 6.1-sol, 6.1-terra fail as Model Provider
Hello, I'm experimenting with the assistant in Reality Composer Pro 3.1. On the OpenAI dashboard I added an API key to a project. I was able to add my OpenAI as a Model Provider using the API key and configure RCP model list. Initially I used gpt-5.5 and it worked. I was able to generate some assets: 3D models, PBR materials, ShaderGraph shaders, and textures. gpt-5.5 runs into a high cost so I was suggested to use 6.1-terra or 6.1-sol, which are more cost effective. terra and sol do not work, the query is failed early and all I get is an error in the prompt. The feedback file generated contains this: ``` { "modelProvider" : "openai", "modelName" : "gpt-6.1-terra (openai)", "prompt" : "Create a 3d model of an art deco desk lamp, with textures. Green body, smokey glass shade.\n" } ``` "gpt-6.1-terra" does match the actual name of the model. In RCP3 I set-up the models like this: The error appears quite fast, in just a few seconds. I aso tested 5.6-terra or 5.6-sol, same result. In the OpenAI dashboard an 400 error is logged: ``` 400 - Invalid request Nov 16, 2026, 08:09 UTC rcp3-model-provider Cause: The request did not meet the endpoint's requirements. Solution: Check the request parameters against the API reference ``` (rcp3-model-provider is the OpenAI project name). In Usage I was able to see some of the queries, while others are not appearing (we are not sure the reason why some show up while others don't). I would like to debug this issue but ot sure where to start. Some hypothesis: - the request is malformed or not compatible with terra/sol models. - terra/sol models lack some feature that gpt-5.5 has, but which one I don't know. There is not much information on query formatting and recommended models. Any help is appreaciated.
Replies
6
Boosts
0
Views
422
Activity
3d
AVAudioSession interrupted with no .ended when a window changes under an open ImmersiveSpace
Title: AVAudioSession interrupted with no .ended when the window changes while an ImmersiveSpace is open Hi, I'm seeing an issue where an active voice call (mic capture + playback) goes silent as soon as the app enters its immersive experience. The system posts AVAudioSession.interruptionNotification with type .began, but .ended never arrives while the app stays in the foreground, so the audio never resumes on its own. Audio only comes back after the app goes inactive and active again (for example after leaving the immersive space). This looks like the same issue reported in https://developer.apple.com/forums/thread/761721 (2024), and it still reproduces on visionOS 26 and 27. Setup: App with a WindowGroup and an ImmersiveSpace. Voice runs on a WebRTC stack (LiveKit, AVAudioEngine-based) on top of AVAudioSession, configured as: category .playAndRecord, mode .videoChat, options [.mixWithOthers, .allowBluetoothHFP, .allowBluetoothA2DP, .allowAirPlay], then setActive(true). When the immersive space opens, an ARKitSession runs with WorldTrackingProvider, HandTrackingProvider and SharedCoordinateSpaceProvider. Steps to Reproduce: Start a voice call from the main window. Mic capture and playback both work. Open the ImmersiveSpace and replace the main window with another window (open the new window, dismiss the main one). Shortly after the space opens, interruptionNotification arrives with type .began and reason .default (0). The audio engine stops. Mic capture and playback both go silent. Expected: Audio keeps running when the window changes. If the system has to interrupt the session, .ended is posted so the app can resume. Actual: .began arrives with no matching .ended while the app remains in the foreground. Audio stays silent until the app goes inactive and active again. At that point .ended arrives with .shouldResume and the engine starts again. The same interruption sometimes hits the very first microphone start right after the session is activated, so the start times out. Nothing else in the app activates or deactivates the audio session at that point. Observation code: NotificationCenter.default.addObserver( forName: AVAudioSession.interruptionNotification, object: nil, queue: .main ) { note in let type = note.userInfo?[AVAudioSessionInterruptionTypeKey] as? UInt let reason = note.userInfo?[AVAudioSessionInterruptionReasonKey] as? UInt print("interruption type=\(String(describing: type)) reason=\(String(describing: reason))") // Logged: type=1 (.began), reason=0 (.default). No type=0 (.ended) while the app stays active. }Current workaround: On every interruptionNotification, and again on UIApplication.didBecomeActiveNotification, call setActive(true) and restart the audio engine if it isn't running. This restores audio while the immersive space stays open. Device: Apple Vision Pro visionOS version: visionOS 27.2 (24N120), also seen on visionOS 26.5 (23O471) Xcode version: Version 27.0 (27A266a) Questions: Is the app's audio session expected to be interrupted when a window closes or is replaced while an ImmersiveSpace is open? If so, why is no .ended posted while the app remains active, and is reactivating the session and restarting the engine the recommended way to resume? Thank you!
Replies
0
Boosts
0
Views
166
Activity
4d
Production LiDAR capture app affected by ARKit world-tracking drift on iOS 26.4+ (re: thread 827240) mitigation guidance and fix timeline?
Hello, and thank you for taking questions this week. We develop DeepWalk, a production App Store application that captures LiDAR depth, RGB, and ARKit camera poses while field technicians walk continuous outdoor routes (sidewalk and infrastructure assessment). Recorded ARCamera.transform values are used downstream for 3D reconstruction, so world-tracking accuracy directly determines our output quality. Problem: Beginning in early April 2026 and coinciding with the iOS 26.4 rollout across our device fleet, we observe directional, accumulating pose drift in recorded trajectories during normal walking motion. The behavior matches the regression reported in forum thread 827240 (world-tracking drift on LiDAR devices on iOS 26.4+, absent on non-LiDAR devices running identical code). Link to existing post here: https://developer.apple.com/forums/thread/827240 Our configuration is minimal: a default ARWorldTrackingConfiguration with frameSemantics = [.sceneDepth, .smoothedSceneDepth] and no other options set, running on a bare ARSession with a Metal renderer (no SceneKit/RealityKit). We measure drift directly from per-frame ARCamera.transform values, so the displacement appears in ARKit's pose output itself rather than in any rendering layer. The drift accumulates with walking distance and does not occur when the device is stationary. We've observed this across a large variety of devices (iPhone 15/16/17 Pro/Pro Max) on all iOS versions 26.4 or greater. We've also observed this on iPad Pros with updated firmware. Thread 827240 additionally reports that disabling autofocus, HDR, and plane detection and varying scene reconstruction and world alignment did not resolve it. Question Because depth capture is our core function, we cannot avoid engaging the LiDAR scanner, and we're not aware of a public API that adjusts its contribution to world tracking. We'd be grateful for guidance on three questions: Is this a known issue in iOS 26.4 and later? Did the LiDAR contribution to world tracking change in that release? For apps that require sceneDepth, is there any recommended session configuration, video format, or capture-side practice that reduces the drift in the interim? Is a fix planned, and if so, should we expect it in an iOS 26.x update or the iOS 27 cycle? This affects how we manage our deployed device fleet. We're happy to provide trajectory datasets, additional sysdiagnoses, or anything else useful. We have quantified drift-per-distance data across OS versions.
Replies
8
Boosts
1
Views
1.9k
Activity
5d
RoomPlan crash: com.apple.RoomScanCore.onlineFloorPlanGeneration EXC_BREAKPOINT
We're seeing a recurring crash inside RoomPlan during an active scan. All reports we have are on iOS 27; we haven't seen it on iOS 26 (Crashlytics for the last 90 days, Xcode Organizer going back further). The first report came in on October 1, 2026. None of our code is on the crashing thread. Feedback: FB25425119 (includes two fully symbolicated crash logs) Crash Crashed: com.apple.RoomScanCore.onlineFloorPlanGeneration EXC_BREAKPOINT (SIGTRAP) 0 RoomScanCore -[RSObjectAlign AlignWithWalls:openings:objectAsset:beautification:chairBeautification:] + 25068 1 RoomScanCore (anonymous namespace)::OptimizeBbox(...) + 168 2 RoomScanCore (anonymous namespace)::OptimizeBboxWithWall(...) + 412 3 RoomScanCore AlignBoxesToNearestWall(...) + 612 4 RoomScanCore -[RSObjectAlign AlignWithWalls:...] + 5992 5 RoomScanCore -[RSFloorPlanRender beautifyObjects:withFloorPlan:pointCloud:] + 212 6 RoomScanCore -[RSOnlineFloorPlanGenerator beautifyObjects:withFloorPlan:] + 116 7 RoomScanCore __40-[RSCaptureSession updateWithKeyframes:]_block_invoke_2 + 4176 8 libdispatch.dylib _dispatch_call_block_and_release + 32 The crash site is the same in every report. It happens while RoomPlan aligns detected objects (furniture) to the nearest wall during the live floor-plan update. Affected iOS 27.0, 27.0.1 and 27.2. No reports on iOS 26.x in our data. iPhone 15 Pro Max, iPhone 16 Pro, iPhone 16 Pro Max and iPhone 17 Pro. Setup RoomCaptureView, started with the default configuration: captureSession.run(configuration: RoomCaptureSession.Configuration()) The app is in the foreground during a normal scan. The main thread is idle at crash time. It happens in larger rooms (around 20 walls) and also within a few seconds of starting a new scan. Affected users often crash several times in a row. We can't reproduce it on demand. Questions Is this a known issue in RoomPlan on iOS 27? Is there a supported way to avoid it, for example by disabling object beautification, until a fix ships? Has anyone else seen this crash with RoomPlan on iOS 27?
Replies
1
Boosts
0
Views
864
Activity
1w
Eye tracking data access for researchers
Hi, Is there a way for researchers to get or request access to eye tracking data from the Apple Vision Pro within the boundaries of the app to be developed? I'm currently involved in research where access to eye tracking data would be beneficial (I'm aware of many existing discussions about this, but I was still wondering if there might be an option, particularly for research labs.) Thank you for your answer.
Replies
3
Boosts
1
Views
1.4k
Activity
1w
FoveatedStreamingSession headset and controller location smoothing, Velocity for OpenXR
Hi, We build a PC VR streaming app for Apple Vision Pro. It has two VR paths: our own stream (our transport, VideoToolbox decode, our compositor layer) and FoveatedStreamingSession with CloudXR, which we use for titles that benefit from foveation. On our own path we filter the head and controller poses and send velocity. Getting both right took a lot of on-device tuning, and they made a large difference to comfort and to physics-based games. On the FoveatedStreamingSession path, the pose path from tracking to the endpoint runs inside the system, so an app has no way to apply, adjust or even inspect either one. We would like to ask for that control. 1. Pose smoothing for the head and controllers What we measured on device: Vision Pro tracking picks up very small, heartbeat-rate motion (around 1.2 Hz, millimetre scale). Locally that is invisible. After a streaming round trip it comes back as a visible world shake, because the remote frame is rendered at a pose about 50 ms old and reprojection has to cover the difference. Our A/B tests showed the tremor is largely rotational. Reprojection did not fully absorb it at our latency: turning off only the rotation filter brought the shake back right away. What fixed it for us: a One-Euro filter on the head pose, applied on the client before the pose is sent, with the frame anchored at the exact pose it was rendered with, so reprojection still covers the gap to the real head at no added latency. The values we settled on after live tuning: ComponentMin cutoffBetaPosition0.1 Hz12Rotation0.5 Hz12The right values depended on the content, the user and the end-to-end latency, which is why we are asking for control rather than one fixed default. Controllers need their own settings, because the right balance between lag and steadiness differs between fast games and precise work such as aiming or drawing. What we would like on FoveatedStreamingSession: Separate smoothing settings for the head and for tracked accessories, with position and rotation set independently. A choice of system default, off, or custom parameters. A One-Euro style minimum cutoff plus speed coefficient would cover our case. Documentation of what filtering, if any, the system applies today, so apps don't filter on top of it. 2. Velocity for the head and controllers Physics titles (throws, grab-and-pull, swings) take their motion from the linear and angular velocity in the OpenXR space velocity (XrSpaceVelocity), not from changes in position. If velocity arrives as zero, throws drop at the user's feet. If it arrives noisy, the PC runtime's own extrapolation to photon time amplifies the noise, and the controllers shake at rest. We hit both cases on our own path. What fixed them: Pass the accessory anchor's velocity through. Set the pose time offset from the client's own prediction, so the PC side does not predict twice. Apply a small deadband (about 0.05 m/s linear and 10°/s angular, matching common open-source streamers). What we would like on FoveatedStreamingSession: Documentation of whether linear and angular velocity are sent to the endpoint for the head and for tracked accessories, and in which reference frame. We could not find a frame statement for AccessoryAnchor velocity in the docs or the SDK interface. Game title testing appears as though these values not being sent. App control over velocity: on/off, a gain, a deadband, and a filter (or the same smoothing settings as above). The prediction offset the session uses when it sends poses, so apps and endpoints can avoid predicting twice. 3. A possible API shape (only a sketch to try to convey the requested need) extension FoveatedStreamingSession { struct PoseFiltering: Sendable, Equatable { static var systemDefault: PoseFiltering { get } static var off: PoseFiltering { get } static func oneEuro(positionMinCutoff: Double, positionBeta: Double, rotationMinCutoff: Double, rotationBeta: Double) -> PoseFiltering } struct VelocityReporting: Sendable, Equatable { var isEnabled: Bool var linearGain: Float var angularGain: Float var linearDeadband: Float // m/s var angularDeadband: Float // rad/s var filtering: PoseFiltering } var headPoseFiltering: PoseFiltering { get set } var accessoryPoseFiltering: PoseFiltering { get set } var accessoryVelocityReporting: VelocityReporting { get set } var posePredictionInterval: TimeInterval { get } }Being able to change these during a session (not only before connect) would let users tune them from the app's own settings while wearing the headset, which is how we found our values.
Replies
2
Boosts
0
Views
613
Activity
1w
Built-in environments in the visionOS simulator
Should Environments like White Sands and Mount Hood work in the visionOS simulator? In a fresh visionOS 27.2 simulator, selecting an Environment from Home View does nothing. I saw the same behavior with visionOS 27.0. After selecting the Moon, Control Center still shows White Sands. Moving the immersion slider in Control Center changes the position of Device Hub’s sidebar slider, but that slider remains disabled and no environment appears. This happens before installing or running my app. The simulated room scenes work. The simulator logs show that the environment catalog downloads successfully, but the scenic assets are marked state=notPresent. Trying to increase immersion produces: Default environment identifier Wolf is no longer available on disk. Resetting to system default. Invalid environment Wolf requested, it does not exist or is not in correct state (Unavailable). Failed to load environment: Error Domain=RealityEnvironmentError Code=407 "Environment action not performed." (Wolf is the internal identifier for White Sands.) Is this an expected simulator limitation, a known issue, or is there a way to download and enable these environments?
Replies
1
Boosts
0
Views
395
Activity
1w
Reality Composer Pro exporting larger and larger .reality files for each reference usage
We've noticed something kind of odd related to the exported .reality file in Reality Composer Pro 3. Our exported .reality file seems to be increasing a lot in size just by referencing an imported asset or another entity in the scene. This contradicts everything we previously knew about references. Essentially it seems like our assets are being copied or duplicated on each export. Before you dive into the description of the issue, yes, I've already created feedback about this. I think it's a bug, but am willing to be corrected if this is an expected, if somewhat odd, behavior. The feedback number is FB25253483 I did a quick test with a single model (Earth.usdz from the RCP2 content library. Project A: RCPExportDupeIssues Phase 01 Created new project in RCP 3 Imported the file and added it to the default world entity Generated an Xcode linked project and used RCP3 to run the app in the simulator (this runs through the entire .reality export process.) Result: 48.4 MB Phase 02 Created AnotherScene entity Added the imported earth model to it Used RCP3 to run the app in the simulator Result: 64.5 MB Phase 03 I thought maybe if I added the earth import to a single entity and added that entity to the other two scenes, I might get some savings. This also increased the overall export size. Created EarthEntity Added the imported earth model to it Used RCP3 to run the app in the simulator Result: 80.7 MB Overall result: an RCP3 project with a single imported Earth asset, used in three otherwise empty scenes, ends up with a massive 80 MB. I even tried deleting the Earth import reference in the first two scenes. Even with only the Earth entity present, the export was still 80.7 MB. Project B: RCPExportNoDupes I tried a second project without ever adding the Earth import file to the first two scenes. I created a dedicated EarthEntity and only added that to the other two scenes. Created new project in RCP 3 Created EarthEntity Imported the file and added it to EarthEntity Added `EarthEntity to the default world entity Created AnotherScene entity and added `EarthEntity to it Generated an Xcode linked project and used RCP3 to run the app in the simulator (this runs through the entire .reality export process.) Result: 80.7 MB Apple: I provided zipped versions of the exports in the feedback item (FB25253483)
Replies
2
Boosts
1
Views
1.1k
Activity
1w
Can visionOS Performance Trace measure RealityKit frame deadlines without Instruments?
We have an immersive RealityView/RealityKit scene on Vision Pro and want to measure renderer frame deadlines, misses, and per-frame CPU/GPU timing without Instruments. Apple's “Performance Trace: visionOS” instructions describe collecting a sysdiagnose for Feedback after installing a temporary logging profile and restarting. We could not find a supported local readout or field map in those instructions. Does the archive contain attributable RealityKit renderer frame deadlines, completion or miss events, and per-frame CPU/GPU measurements? If so, what supported tool, command, or export can decode them without Instruments or xctrace? Which archive member and fields contain the measurements, and what are their clock, units, and app/scene/layer attribution? A small redacted decoded example would help us verify the method before another headset run. If the archive does not provide those measurements, is there another Apple-supported method for the existing RealityKit renderer?
Replies
2
Boosts
0
Views
429
Activity
2w
Presenting the system share sheet from a full ImmersiveSpace on visionOS 26
We are building a visionOS 26 app (deployment target visionOS 26.0). Inside a full immersive space, the user takes a spatial photo. The photo is shown on a RealityView attachment. We need the system share sheet( AirDrop, Messages, Mail, Copy, Save Image, and the item preview with Done) to appear when the user taps Share on that attachment. The immersive space is: ImmersiveSpace(id: "ImmersiveView") { ImmersiveView() } .immersionStyle(selection: $panoImageView, in: .full) .upperLimbVisibility(.visible) The review UI is a RealityView attachment, not a window: Attachment(id: "panoramaFrameCaptureReview") { PanoramaFrameCaptureReviewView(model: frameCapture) { guard let path = frameCapture.shareURL?.path else { return } dismissWindow(id: "PanoramaPhotoShare") Task { @MainActor in try? await Task.sleep(nanoseconds: 180_000_000) openWindow(id: "PanoramaPhotoShare", value: path) } } } The shared item is a stereo HEIC written with Image I/O (kCGImagePropertyGroupTypeStereoPair, left/right images, HEIF camera extrinsics and SimplifiedPinhole intrinsics). The same data displays correctly with ImagePresentationComponent and saves to Photos as a spatial photo. Share is the only part that fails. Attempt 1. ShareLink on the attachment Tapping Share does nothing. On entry to the immersive space the system logs: Presentations are not currently supported in Immersive contexts. Attempt 2. UIActivityViewController from the attachment’s hosting controller let activity = UIActivityViewController(activityItems: [fileURL], applicationActivities: nil) var presenter: UIViewController = self while let parent = presenter.parent { presenter = parent } presenter.present(activity, animated: true) presenter is UIHostingController<RootView>. The console then says: Skipping popover presentations transition, missing window or scene for <UIActivityViewController>. Failed to request default share mode for fileURL:...heic error:Error Domain=NSOSStatusErrorDomain Code=-10814 No share UI appears. presentedViewController is non-nil, so a “did it present?” check does not detect the failure. Attempt 3. A real WindowGroup whose only job is to present UIActivityViewController WindowGroup(id: "PanoramaPhotoShare", for: String.self) { path in if let path = path.wrappedValue { PanoramaPhotoShareWindow(path: path) } } .windowStyle(.plain) .defaultSize(width: 20, height: 20) .defaultWindowPlacement { _, _ in WindowPlacement(.utilityPanel) } struct PanoramaPhotoShareWindow: View { let path: String @Environment(.dismissWindow) private var dismissWindow var body: some View { PanoramaPhotoSharePresenter(url: URL(fileURLWithPath: path)) { dismissWindow(id: "PanoramaPhotoShare") } .frame(width: 8, height: 8) .background(.clear) } } final class PanoramaPhotoShareController: UIViewController { override func viewDidAppear(_ animated: Bool) { super.viewDidAppear(animated) guard view.window != nil, let url else { return } let activity = UIActivityViewController(activityItems: [url], applicationActivities: nil) activity.completionWithItemsHandler = { _, _, _, _ in self.onFinish?() } present(activity, animated: true) } } Tapping Share opens this window and the app crashes immediately. We removed the feature so users are not crashed. An earlier build that also put a ShareLink in that window logged: Attempt to present <UIActivityViewController> on <UIHostingController<...PanoramaPhotoShareWindow...>> which is already presenting <UIActivityViewController>. Question What is the supported way, on visionOS 26, to present the system share sheet while a .full ImmersiveSpace stays open? If a window is required, how should that window present the sheet without crashing, and without showing a second window that only contains another Share button?
Replies
1
Boosts
0
Views
769
Activity
2w
Improving metric scale consistency of ARWorldTrackingConfiguration on devices without LiDAR
We build a medical scanning app. A practitioner walks a slow orbit (~1 m radius, two laps, 25–35 s) around a standing subject while an ARSession runs, and we capture ~50 high-resolution stills with captureHighResolutionFrame. The ARKit camera poses for those frames are later used to set the metric scale of a photogrammetry reconstruction. We need the resulting scale to be within about 2 % of true. What we observe, measured against a printed A4 sheet on the floor in every scan: Devices with LiDAR (iPhone 16 Pro Max, iPad Pro), using the sceneDepth frame semantic as a check: scale within ±0.8 % across 11 sessions. Devices without LiDAR (iPhone 13, iPad 9th and 11th gen, plus non-LiDAR runs on the Pro devices): the world-frame metre is on average 2–3 % short of true, and varies by a further ±2 % from one session to the next, across 24 sessions in four rooms. Within a session the scale is stable: lap-to-lap variation is under 0.4 %. The error appears to be set during initialisation and held. Nothing we record about capture correlates with the error: time spent before capture, distance walked, vertical camera movement, orbit radius, rotation speed, tracking state, or the residual of our pose fit. Questions: Is there any session setup, initialisation practice, or motion during the first seconds of tracking that is known to improve the metric scale estimate on devices without LiDAR? Does the choice of video format, resolution or frame rate affect scale estimation? Is there any signal, beyond ARCamera.trackingState, that indicates how well scale has been determined for a session, so we could flag sessions rather than accept them? Does anything in the configuration above, in particular locking exposure on the capture device or using the high-resolution video format, work against tracking quality or scale?
Replies
1
Boosts
0
Views
912
Activity
2w
visionOS 27 beta 4 (24M5326g) stuck: update fails with MSU 806 MADownloadDaemonNotReady, all Apple services hang
My Apple Vision Pro is still on visionOS 27.0 beta 4 (24M5326g) and can't update or use any Apple service. Safari works. Software Update offers visionOS 27.2 (24N6120) but stays at "Update Requested". The OTAUpdate log shows: MobileSoftwareUpdateErrorDomain 806 "Failed to download update brain asset, MADownLoadResult:MADownloadDaemonNotReady". App Store can't connect, Apple TV and Games say a network connection is required, iCloud doesn't work, and Media & Purchases hangs at "Signing in to Apple Media Services". Other devices on the same network work normally. Reset All Settings didn't help. devicectl device sysdiagnose fails with CoreDeviceCLISupport.DiagnoseError 0. I don't have a Developer Strap. Has anyone recovered a Vision Pro stuck on an early beta like this without one? Filed as FB25386556.
Replies
0
Boosts
0
Views
447
Activity
3w
Reality kit Entities Appearing to Lag in a Full or Progressive Style Immersive Space When Opened with Environment Turned On
PLATFORM AND VERSION Vision OS Development environment: Xcode 16.2, macOS 15.2 Run-time configuration: visionOS 2.3 (On Real Device, Not simulator) Please someone confirm I'm not crazy and this issue is actually out of my control. Spent hours trying to fix my app and running profiles because thought it was an issue related to my apps performance. Finally considered chance it was issue with API itself and made sample app to isolate problem, and it still existed in it. The issue is when a model entity moves around in a full space that was launched when the system environment immersion was turned up before opening it, the entities looks very choppy as they move around. If you take off the headset while still in the space, and put it back on, this fixes it and then they move smoothly as they should. In addition, you can also leave the space, and then turn the system environment immersion all the way down before launching the full space again, this will also make the entity moves smoothly as it should. If you launch a mixed immersion style instead of a full immersion style, this issue never arrises. The issue only arrises if you launch the space with either a full style, or progressive style, while the system immersion level is turned on. STEPS TO REPRODUCE https://github.com/nathan-707/ChoppyEntitySample Open my test project, its a small, modified vision os project template that shows it clearly. otherwise: create immersive space with either full or progressive immersion style. setup a entity in kinematic mode, apply a velocity to it to make it pass over your head when the space appears. if you opened the space while the Apple Vision Pros system environment was turned up, the entity will look choppy. if you take the headset off while in the same space, and put it back on, it will fix the issue and it will look smooth. alternatively if you open the space with the system immersion environment all the way down, you will also not run into the issue. Again, issue also does not happen if space launched is in mixed style.
Replies
2
Boosts
1
Views
1.2k
Activity
3w
Immersive space sometimes opens with a broken world origin (world anchors fail with error 200, recenter times out)
Hi all, We're seeing an intermittent issue in a native SwiftUI + RealityKit app on Vision Pro (visionOS 27.0.1, still there on 27.2). When we open a mixed ImmersiveSpace, roughly 1 in 10–30 opens, everything ends up offset from where it should be. Sometimes it's 50 cm, sometimes several meters, sometimes it's rotated. Holding the Digital Crown to recenter fixes it immediately. We are attaching things to the camera, like we have a window following the user and that is offset in these rare cases which makes the app not usable. In the device logs, a good open looks like this: backboardd (recenter) Setting new world origin with anchor ... backboardd ARWorldTrackingProcessor: Added world anchor ... successfully (x4) backboardd (recenter) Finished (error: (null)) setting set new world origin ... A bad open looks like this: backboardd (recenter) Setting new world origin with anchor ... arkitd SLAMAnchorUpdate: Failed to add anchor request ... NSPOSIXErrorDomain Code=4 backboardd ARWorldTrackingProcessor: Failed to add world anchor ... com.apple.arkit Code=200 "Adding an object failed." (x4) backboardd (recenter) timeout exceeded. Forcing fade in. Like whenever the bad state occurs it is because adding a world anchor seems to fail. I haven't tested with visionOS26 but the same app didnt run into that problem ever. So the system seems to fail adding its own origin anchors, gives up after 2 seconds and shows the space anyway. Has anyone else run into this? And is there any way to detect it from the app or trigger a recenter in code? Thanks!
Replies
2
Boosts
0
Views
680
Activity
3w
High fidelity gaming on Apple Vision Pro
I'm looking to find the best setup for a game on AVP that gives the best quality environment with gameplay but there seems to be a mix of possible solutions each with their own drawback. My ideal scenario is a high fidelity room/environment while making use of the PS VR2 Sense controllers to track the user's hands and give them more inputs via the controllers. Eg they hold a weapon tracked to the controllers with the buttons able to use the weapon, shooting and hitting enemies in the room. I want to aim more for highest qualtiy gaming than cartoony so opted for foveated streaming from the Mac as my ideal, but this seems limited to only having some base inputs from the hands and no controller inputs for hand and positional tracking from the controller movement (as they need the data from the Vision Pro camera but the game is technically running on the Mac and streamed to the VP) The only real solution for what I want here is to go via RealityKit as a native Vision Pro app but this reduces the game quality I had in mind as the entire thing is now rendering on the VP instead of the Mac. Am I missing something here or is this a real limitation today? To reitarate I'm looking for: highest fidelity game quality (rendering as much as possible on the Mac) tracking the VR2 Sense controller's positions (to track a weapon) in 3D space
Replies
1
Boosts
0
Views
1.1k
Activity
3w
Async Entity(contentsOf:) is 15 to 20x slower while an ARView is rendering
While a non-AR ARView is on screen and rendering, await Entity(contentsOf:) takes about 26 s to load a 4.5 MB USDZ with 300 textured meshes. The same file loads in about 1.5 s with the synchronous Entity.load(contentsOf:), or with the async API while the view is hidden. iPhone 16 Pro, iOS 27.2Mac Catalyst, macOS 27.2await Entity(contentsOf:), view rendering22 to 26 s26 sEntity.load(contentsOf:), view rendering1.6 s1.1 to 1.7 sawait Entity(contentsOf:), view hidden1.4 s1.3 to 1.5 sModelEntity(contentsOf:) and Entity.loadAsync(contentsOf:) behave the same. A .reality file loads fast either way, and the iOS Simulator doesn't show it. A Time Profiler trace shows the main thread blocked in re::RenderThread::waitForFramePacing on every frame, so the @MainActor import only advances between frames. Neither workaround fits loading content into a scene the user is looking at: the sync load blocks the main thread, and hiding the view blanks it. Filed as FB25340264, with a sample project.
Replies
0
Boosts
0
Views
190
Activity
3w