“translate scheme”

I'm getting following message when launching #Playgrounds canvas with Xcode 26 beta 4. Here are things I've tried: Reinstall Xcode Reinstall components Removed derived data Run Disk Utility to fix permissions Tried to change Default Actor Isolation, Approachable Concurrency Changed around settings on Schemes: Run: Options and Diagnostics Created brand new project with default settings. Filed FB19003005 in Feedback Assistant. I'm surprised to see that I didn't see any posts on this during my search. So this could be isolated matter just to me.

H there! I'm new to mergeable libraries, so sorry if I missed anything obvious. We have some really huge projects with mergeable libraries that started failing to build with Xcode 26 beta 3. After doing some research I managed to create a very small project where I was able to reproduce the issues. The project just contains a SwiftUI app and a framework. The framework includes just a class that is used from a SwiftUI view included in the app. Problems I found the following: Default configuration (no mergeable libraries) Everything works as expected Automatic mergeable libraries In this case I just set Create Merged Binary to Automatic. In this case: the application can be properly built and run in the simulator the SwiftUI preview stops working with the following report: == PREVIEW UPDATE ERROR: FailedToAnalyzeBuiltTargetDescription: Could not analyze the built target description for MLibTestCase to create the preview. buildableName: MLibTestCase ================================== | UnrecognizedLinkerArgument

hello, i am currently trying to add a hardpaywall to my app. When I test in testflight with storekit config set to none in scheme. I get an error saying unable to load subscriptions.

I am trying to integrate fastlane, which relies on xcodebuild. So this is my first experience with xcodebuild. Whenever I run a command to test or build the target in the folder where all the files of the project are stored, the action failes with Unable to find a device matching the provided destination specifier For example I might be running this command: xcodebuild -project Hoerspielzentrale.xcodeproj -scheme HoerspielzentraleUITests -destination 'platform=iOS Simulator,name=Screenshot Simulator”' test However the mentioned error is returned: xcodebuild: error: Unable to find a device matching the provided destination specifier: { platform:iOS Simulator, OS:latest, name:Screenshot Simulator” } The requested device could not be found because no available devices matched the request. I can confirm that the simulator exists, is available and it can be booted. I have tried different simulators, different schemas, referencing them by their identifier, switching Xcode Versions, reset all simulators

Hello, I seem to be in the same situation as this developer here. My account is pending termination with the following accusation: App submissions from your account have engaged in concept or feature switch schemes to evade the review process, such as dynamically populating different app content after review, submitting apps with hidden features, repeatedly submitting misleading apps, and/or submitting apps with concrete references to content that you are not authorized to provide or is otherwise not appropriate for the App Store. I believe this to be a mistake, however I'm happy to make changes to the app to remedy this. I'm an open book - there's nothing I'm hoping you won't notice. I'm aiming for full compliance with all the App Store requirements and if I'm not compliant I'll make the required changes. If the App Review team monitors this could you please take a look? Thanks, Matt

Please excuse me if this is obvious. I'm new to Apple development. Is there a SwiftUI Accessibility Inspector? I run the standard one, in Xcode 26b3, and it shows me warnings for things that I didn't create in SwiftUI. I presume that SwiftUI is primarily implemented using macros and that these things are either generated or boilerplate lower-level things. But if so, then why would they trip Accessibility Inspector warnings? Is there something I can do from SwiftUI to clear them? Or... is there a demangler somewhere that will translate from these names into something this human might recognize? I'm targeting macos, btw, if that makes any difference.

Hello everyone, I'm working on a visionOS application using RealityKit and am encountering a common coordinate system challenge when integrating 3D models created in Blender. My goal is to display and dynamically update the Transform (position, rotation, scale) of models created in Blender within RealityKit. The issue arises because Blender's default coordinate system is Z-up, and while exporting to USD/USDZ, I don't have a reliable Y-up export option that correctly reorients the model and its transform data for RealityKit's Y-up convention. This means I'm essentially exporting models with their up direction along the Z-axis. When I load these Z-up exported models into RealityKit, they are often oriented incorrectly. To then programmatically update their Transform (e.g., move them, rotate them based on game logic, or apply physics), I need to ensure that the Transform values I set align with RealityKit's Y-up system, even though the original model data was authored in a Z-up context. My questions are: What is

Hello RealityKit developers, I'm currently working on physics simulations in my visionOS app and am trying to adapt the concepts from the official sample Simulating physics joints in your RealityKit app. In the sample, a sphere is connected to the ceiling using a PhysicsRevoluteJoint to create a hinge-like simulation. I've successfully modified this setup to use a PhysicsSphericalJoint instead. The basic replacement works as expected: pin1 (attached to the sphere) rotates freely around pin0 (attached to the ceiling), much like a ball-and-socket joint should, removing all translational degrees of freedom. My challenge lies with the PhysicsSphericalJoint's angularLimitInYZ property. The documentation mentions that this property allows limiting the rotation around the Y and Z axes, defining an elliptical cone shape around the x-axis of pin0. However, I'm struggling to understand how to specify these values to achieve a desired rotational limit. If I have a sphere that is currently capable of rotating 36