“translate scheme”

On iOS there’s no supported way to construct paths to items outside of your apps containers. The only supported way to get such paths is to ask the user for them, using the file selection API from the UI framework you’re using. Furthermore, this is a concern: [quote='781930021, delingren, /thread/781930, /profile/delingren'] I know the URL scheme is shareddocuments [/quote] AFAIK this is not a a documented URL scheme. I discuss that topic in more detail in Supported URL Schemes. WARNING Don’t build a product that relies on unsupported implementation details like. It’s very likely that your product will break in future releases of iOS and, if it does, there’s a good chance that there’ll be no path forward for your app. If you’d like us to add a supported mechanism to achieve this goal, I encourage you to file an enhancement request describing your requirements. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Appl

There’s no general-purpose mechanism for you, as a user, to set environment variables on apps. Such a mechanism doesn’t really make sense on the Mac, because Mac apps aren’t supposed to rely on the Unix environment. Of course, that stance breaks down when you start talking about developer tools. It’s not uncommon for developer tools to rely on environment variables. And because of that GUI developer tool will often provide a mechanism for setting environment variables. Xcode is a good example of this, where you can set environment variables for the app you’re debugging in the scheme editor. It’s possible that your developer tool actually has similar support. I recommend that you ask that question via the vendor’s support channel. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

FB17303841 (iOS 18 System Bug Causes URL Scheme Failure)

Due to the existence of a framework that cannot be replaced temporarily in the project, I can only exclude arm64 in order to run it on the M-series chip simulator and reproduce this issue. Manifested as the emulator running on arm64 architecture and the project architecture being x86 At present, the image selector can only be used on real machines. The above is from automatic translation.

I have a command-line app experiencing this issue. It uses CVDisplayLink to render directly to a window through Metal. Apple recently deprecated CVDisplayLink and introduced a new recommended API, CAMetalDisplayLink. It has the same restrictions as CADisplayLink and prevents the user from having true low-level control over frame synchronization. The other apps mentioned with this bug rely on OpenGL and other frameworks, which likely delegate directly to CVDisplayLink. This might explain why a strange subset of all apps are affected by the bug. The solution for my use case, was to launch the app from swift run on command-line w/ SwiftPM, which is how it would run on non-Apple platforms as well. But my solution may not be the best for other people. Alternatively, you can add an intentional ≥350 ms delay upon app startup. The workaround sleep(1) worked because it introduced a 1000 ms delay, ~three times what is actually needed. https://github.com/philipturner/molecular-renderer/commit/655e367ef5a33218d7fc5654ded

I experienced the same issue in my environment (XCode 16.2, Intel MBP, iOS Simulator). However after getting Couldn't find the Objective-C runtime library in loaded images at the first breakpoint, manually attaching the debugger allowed subsequent breakpoints to function properly. Therefore, I'm using the following workaround by running without a debugger and attaching manually: Product > Scheme > Edit Scheme... Choose Run from left pane. In the Info tab of right pane, uncheck Debug executable Run Application Debug > Attach to Process > (Choose Your Simulator from the top of the list) Since I've just started using this method, I can't guarantee it will always work, but it might be helpful for debugging except for the very initial startup phase.

Hi @cuo001 There are many ways to do this. Here's a snippet to get you started. It uses SpatialEventGesture and a hand AnchorEntity. When a person begins the pinch gesture, the code appends the entity to an anchor entity attached to the index finger, mantaining its world position, then animates the entity to a position near the index finger. When the pinch ends, the code appends the entity to its previous parent and animates the entity to its previous position. Create a custom component to store the state related to the custom interaction. struct SummonComponent: Component { let leftAnchor: AnchorEntity let rightAnchor: AnchorEntity var isHolding = false var parentEntity: Entity? var previousTransform: Transform? } Implement the interaction. struct ImmersiveView: View { @State var spatialTrackingSession = SpatialTrackingSession() var body: some View { RealityView { content in // Create the entity to summon. let box = ModelEntity(mesh: .generateBox(size: 0.15), materials: [SimpleMaterial(color: .red, isMetalli