Search results for

xcode github

94,729 results found

Post

Replies

Boosts

Views

Activity

'__abort_with_payload' from CompositorNonUI on visionOS 26.2 (device + simulator, Omniverse streaming)
I am developing a custom app for Apple Vision Pro using Compositor Services to stream content from NVIDIA Omniverse. The app is based on: https://github.com/NVIDIA-Omniverse/apple-configurator-sample Environment: Device: Apple Vision Pro OS Version: visionOS 26.2 Xcode Version: 26.2 The Issue: The application crashes hard (__abort_with_payload) in libsystem_kernel.dylib on Task 6 immediately after initialization. This appears to be a deliberate abort triggered by the compositor, not a typical crash. The issue occurs on both physical device and simulator. Important detail: The console output shows a specific CLIENT BUG assertion. By checking the metadata of the warning, I found that it is related to Library: CompositorNonUI. Relevant console output before abort: Missed 'FrameLimiter' target of 90.0 Hz running compositor services to get IPD, FOV, etc fence tx observer 14f27 timed out after 0.600000 fence tx observer bc1b timed out after 0.600000 BUG IN CLIENT: For mixed reality experiences please use c
0
0
90
3w
Reply to provision profile deleting from the file mac
In most cases you don’t need to install provisioning profiles on your Mac (or on iOS for that matter). Rather, Xcode embeds the profile within the app you’re running and the OS picks it up from there. So, what are you trying to achieve by installing a provisioning profile? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
3w
Reply to Xcode Using 90GB with ~/Library/Developer — What Can I Safely Clean?
What Scott said plus: DocumentationCache is pretty much what it says on the tin. You can delete it, but Xcode will have to rebuild it (although that rebuild is likely to be smaller). If you do delete it, I recommend that you delete DocumentationIndex at the same time. For CoreSimulator, it’s probably best to not monkey with that yourself but instead manage it via either Window > Devices & Simulators in Xcode or the simctl command-line tool. And in all cases, make sure that Xcode is quit before you start deleting stuff behind its back. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
3w
Debugging help: BUG IN CLIENT: For mixed reality experiences please use cp_drawable_compute_projection API
Hi, we've been developing an XR application for Apple Vision Pro which has worked fine so far. Now that the SDKs have updated to 26.2 (for Xcode and AVP versions) we've run into an error that prevents the app from launching. I get the following error when running the application in the AVP Simulator (building for destination Apple Vision Pro (26.2), and my colleague gets the same error when building for the device itself and launching there. BUG IN CLIENT: For mixed reality experiences please use cp_drawable_compute_projection API Type: Error | Timestamp: 2026-01-13 09:21:57.242191+02:00 | Process: My XR App | Library: CompositorNonUI | TID: 0x75e2c (copied with all metadata) How can we debug this further? The error in the console doesn't seem to give any stack trace or clear pointer to the code which relates to it. I've tried searching for CompositorNonUI, but that doesn't yield any results in our project (nor Google nor the Apple developer forums). There is one post in the forum that has a similar
1
0
122
3w
SwiftUI Instruments Template doesn't work
I am profiling a simple SwiftUI test app on my new iPhone through my new MacBook Pro and everything is version 26.2 (iOS, macOS, Xcode). I run Instruments with the SwiftUI template using all of the default settings and get absolutely zero data after interacting with the app for about 20 seconds. Using the Time Profiler template yields trace data. Trying the SwiftUI template again with the sample Landmarks app has the same issue as my app.
2
0
146
3w
App Store submission validation failed: Missing info.plist value WKApplication
I've developed a Multiplatform app under Xcode 26 (currently using 26.2 17C52). The current destinations of the single target are Mac, iPad and Mac(designed for iPad). The minimum deployments are MacOS 15.6 and iOS 18.6. All destinations build and perform correctly on physical devices (running OS 26 versions). The MacOS version has been submitted successfully to the AppStore for TestFlight usage. However, the iPad version shows a submission validation failure: Missing Info.plist value. A value for the key “WKApplication”, or “WKWatchKitApp” if your project has a WatchKit App Extension target, is required in “xxxxx.app/xxxxx.app” bundle. For details, see: https://developer.apple.com/documentation/watchkit/creating_independent_watchos_apps/setting_up_a_watchos_project (ID: 4911506c-39c3-4b69-a8bb-5e5dcd3dc2fb) The app has no WatchKit version (although one's planned for a future release). The Target's Build Settings include a watchOS Deployment Target and Info.plist values related to WatchKit. The Build
2
0
117
3w
Reply to Upload for App Store Connect: App Record Creation Error
The issue is indeed related to my account having administrative permissions under another company's account. My personal account has been assigned administrative permissions (with the authority to manage certificates) under another company's account. Yesterday, I tried to remove my account from that company's account. Today, when I tried to package and submit, Xcode prompted me to access my certificate (presumably the certificate for my personal account). After I agreed, everything proceeded smoothly. It seems that when my account has administrative permissions for multiple accounts, Xcode uses the wrong certificate.
3w
Companion watch app missing when publishing via xcode 26
Hi Forum I am working on an ios app with a companion watchos app. The watchos app was made in 2018, it uses watchkit and has a watchkit app target and a watchkit app extension target. When I started working on it, the app was already published and running. More importantly, the watch app was installing on the users watch automatically, when the app was installed on their phones. I came in and made some changes, updated some things and added some smaller features. After uploading to testflight and testing the app there, we sent it for review and updated the app. This updated app, introduced the issue that when users now downloaded the app, the watch app seems to be missing. For me, downloading this new version on either testflight or app store works fine, but whenever my boss or a new user does it, the watch app is missing. I have tried to go back to the older version of the app I started with, but this doesn't seem to change anything. My coworker tried to do do the same thing, uploading the old version, but w
1
0
134
3w
Reply to Library not loaded: @rpath/libswiftCompatibilitySpan.dylib – Building bundle target
Based on your description, you are encountering an issue with loading the library and deploying it into macOS versions 15? Correct. Can you confirm that when you deploy the app built in Xcode 26.2 to macOS 15, you still encounter this bug? That is the case. I sm compiling with Xcode 26.2 using macOS 26.2 (25C57) SDK (Built-in) targeting macOS 12 and later. The error occurs on macOS 15.7.3 but not on macOS 26. I suspect this is because macOS provides the Span API natively and thus does not need to access the backdeployment dylib, unlike macOS 15 where this API is not available natively. Talking to people working on Swift, they interpreted this to be an Xcode issue, stating: Xcode should (somehow) bundle libswiftCompatibilitySpan with it, but it doesn’t, leading to the failure on macOS 15.x.
3w
Reply to Library not loaded: @rpath/libswiftCompatibilitySpan.dylib – Building bundle target
Thanks for the post. Based on your description, you are encountering an issue with loading the library and deploying it into macOS versions 15? I believe there was a bug on previous versions of Xcode, but that should have been fixed. Are you using Xcode 26.2 to build the app? The error message indicates that the library cannot be found at runtime, despite being included in your build setup. If you are getting this error on macOS Sonoma with the app build in Xcode 26.2, it means the bug is on that version of macOS. If you are not getting the error in macOS Tahoe, the bug has been fixed. The good news is that the bug has been fixed, but the bad news is that the bug is also in macOS 15? And it was not just Xcode as I initially thought. Can you confirm that when you deploy the app built in Xcode 26.2 to macOS 15, you still encounter this bug? Albert Pascual
  Worldwide Developer Relations.
3w
Reply to TestFlight Incorrectly Linking to Personal Apple ID After Latest Apple Updates.
Thank you for your post. I believe the primary focus of your post is on the simplicity of how easy is to set the incorrect account in the dropdown menu for the account you are currently using in Xcode. As a personal recommendation, I only suggest using a separate device (computer and test devices) dedicated to your Business Apple ID to avoid potential conflicts. Ensure that your personal account is never connected to this devices. This approach will prevent any accidental mixing of accounts, in my modest opinion. You can manage your Business Apple ID independently and use it exclusively for redeeming TestFlight invites related to your business projects. Additionally, if you are using beta versions of iOS, ensure that the profiles associated with your Business/Managed Apple ID are correctly installed and active on the device. To implement these steps, navigate to Xcode > File > Settings > Apple Accounts and remove your personal account. By maintaining separate devices for your person
3w
Reply to SwiftUI Instrumentation Fails to start
Updating to XCode 26.2 and macOS Tahoe 26.2 and im now greeted with Trace file had no swiftui data this occurs if I profile with XCode and chose a template I profile with XCode and chose a blank template and manually choose SwiftUI I manually run the Instruments, manually run the app, attach and open a document in my swiftUI app however, if i DO NOT load a document (macOS based swiftui app), im able to get swiftui traces my feeling here is theres something going on with complicated traces that cause an issue modelling the data stream, or capturing the trace? Im not familiar with the nuances here but this isnt working for anything that NEEDS profiling.
3w
Library not loaded: @rpath/libswiftCompatibilitySpan.dylib – Building bundle target
I am building a bundle target for macOS 12 and later using Xcode. The bundle is not a standalone app, but a plug-in that is loaded by a host app. The code is written in Swift and uses the new Span API which is available in the OS-provided standard library in macOS 26 and backdeploys to macOS 10.14.4+. Xcode should instruct the linker to include libswiftCompatibilitySpan.dylib in the compiled bundle to provide this backdeployment, but that does not happen. SwiftPM does this additional linking by adding an rpath. When trying to load the bundle using the NSBundle.loadAndReturnError() API, I get the following error on macOS 15 (and no error on macOS 26): Error Domain=NSCocoaErrorDomain Code=3588 dlopen(.../MyBundle.someBundle/Contents/MacOS/MyBundle, 0x0109): Library not loaded: @rpath/libswiftCompatibilitySpan.dylib Referenced from: .../MyBundle.someBundle/Contents/MacOS/MyBundle Reason: tried: '/usr/lib/swift/libswiftCompatibilitySpan.dylib' (no such file, not in dyld cache), '/System/Volumes
8
0
347
3w
Reply to Foundation Model Framework
Hi all! For all of these weird errors, you'll need a matching Xcode version, Simulator version, and macOS version for everything to work. You also need all versions to be at least 26.0, otherwise the model assets simply aren't there. e.g. Xcode 26.2, iOS 26.2 simulator, macOS 26.2 After you update Xcode and simulator, those should work right away.... but when you update your physical device or VM expect some delay. Once you update the correct version of the model assets have to finish downloading, which could take a few hours depending on your network and device power.
3w