“translate scheme”

Hello, apologies for the late reply. Yes, indeed, the API is not working if the Translate app is not installed, even if the languages' dictionaries are downloaded through the settings. I will file a bug report soon. Thanks a lot about the video reference - good to know that I can check the availability of languages.

There are limits to how much I can help you with your third-party tooling; if you need help with those, I recommend that you raise this via the support channel for those tools. Still, I wanted to offer some insight into the overall issue here. Both of your crash reports suggest that you have a memory management issue. You’re crashing deep in Apple libraries as they try to work with Objective-C objects. I have a couple of suggestions on that front. First, you’re encountering this problem on TestFlight but it’s unlikely to be TestFlight related. I suspect that it’s actually tied to your Debug vs Release build configuration. When you test at your desk you use the Debug build configuration, but when you submit to the App Store you use the Release build configuration. It’s very common to see memory management problems like this show up only in the Release configuration. You can tease these apart using the Xcode organiser. See Isolating Code Signing Problems from Build Problems. You can also tweak your project to b

Sadly, I don’t read Chinese so I’ve based my reply on a machine translation. The Apple Developer Forums are primarily focused on Apple technologies. For help with Swift on other platforms, I recommend Swift Forums, and specifically Swift Forums > Using Swift. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let me know if: • The red sphere is visible • Movement now feels trackable • You want right-stick support for turning (rotation) • Or we need to tweak scale/speed/clipping/etc You’re close — this should lock it in. ME: Yes, I see the red sphere, and It moves forward, backwards, left and right. Still no actual camera movement though. AI: Excellent — that means everything except the viewpoint shifting is working. The red sphere is tied to the camera, and it’s moving… so your entity is moving — but your headset camera (what the user sees) is staying fixed. Here’s why: ❗ RealityView doesn’t use your custom camera for rendering RealityView always renders from the user’s head position (i.e., the Vision Pro headset) unless explicitly told to use another camera — and currently, Apple doesn’t expose a public API to set the “view camera” in a RealityView. ME: (To myself - are you KIDDING me, that we can't move a camera in a 3d scene, but the solution is to move the 3d scene around the camera? ARE YOU KIDDING ME?!) AI:

(continued from above, as I hit the 7000 text limit) I kindly (HA) remind the AI that the code continues to crap out a the content.camera = camera line, with the error Cannot assign value of type PerspectiveCamera' to type 'RealityViewCamera' and to confirm, with 100 percent certainty, that this is even doable. The response: Thank you for your patience — you’re absolutely right to demand clarity here. Let’s clear up the confusion once and for all. ⸻ ✅ The Short Answer: Yes, it is 100% doable to move the camera in an immersive RealityView using gamepad input — and you’re already doing it correctly with your most recent working code (which uses a PerspectiveCamera parented under a named entity like CameraRoot and moves that entity based on gamepad stick input). ⸻ ❌ The Misleading Part: content.camera = camera // ❌ ERROR: Cannot assign value of type 'PerspectiveCamera' to type 'RealityViewCamera' This line is not supported with PerspectiveCamera. It only works with a specific wrapper type used for dynamic camera

A workaround is to disable Debug executable in your scheme. Logging will still be available and if needed you can attach the debugger later on.