Search results for

xcode github

94,729 results found

Post

Replies

Boosts

Views

Activity

Reply to Technical Inquiry regarding iPhone LiDAR Specifications and ARKit Data Integrity
Googling 3 words of apple dtof doe will help you. Apple LiDAR 3D camera has 64 (16x4) physical laser emitters (VCSEL) They are multiplied with 3x3 by DOE to 576 laser pulses. They are interpolated with live RGB images to generate 256x192 depthMap 60 Hz. We used an empirical error model of base_error(distance) = a + b * distance * 2 // the distance is in meters. a = 0.001 and b = 0.00005 . For demo Apps, explore the GitHub repo; https://github.com/CurvSurf/FindSurface-iOS
Topic: Spatial Computing SubTopic: ARKit
3w
Xcode Cloud Export Archive Fails with Xcode 26.2 RC
Export archive step fails in Xcode Cloud when using Xcode 26.2 (17C48) RC. The same project exports successfully when switching back to Xcode 26.1 in Xcode Cloud workflow settings. The same project exports successfully when using Xcode 26.2 RC locally. Projects without Apple Watch app do not encounter this issue (not so sure about this). From Xcode Cloud UI: Exporting for App Store Distribution failed. Please download the logs artifact for more information. Run command: 'xcodebuild -exportArchive ... Command exited with non-zero exit-code: 70 From xcodebuild-export-archive.log: error: exportArchive Automatic signing cannot update bundle identifier io.***.***.watchkitapp. error: exportArchive No profiles for 'io.***.***.watchkitapp' were found error: exportArchive Automatic signing cannot update bundle identifier io.***.***. error: exportArchive No profiles for 'io.***.***' were found ** EXPORT FAILED ** IDEDistribution: App Store Connect request for store
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
10
0
828
3w
Reply to Testflight builds getting stuck in processing
Guys I got mine to work in the following way: (Apple clearly isn't coming to the rescue, they're like the DMV at this point, so maybe this will help somebody...) NOTE: All my apps use Expo and eas build (which I run locally). I had 4 builds for the same app stuck in Processing purgatory. So I tested another app in another dev account, and it worked. This was a clue. I tried making swift changes, bundle version changes, everything, and it didn't work at all. So I ran expo prebuild, opened the app in Xcode, old school method, I didn't change any code at all, just the bundle version AND build number, and I ran Archive. Then I submitted it to App Store Connect from inside Xcode, and it worked. Who knows why, but it worked, and my other builds are still endlessly processing. There you go. Good luck out there everyone
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
3w
Reply to Xcode Cloud builds stuck at App Store Connect
same issue on my self-hosted server via fastlane. Build stucked for 4h and no results. Just wrote infinity: [11:15:51]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) [15:38:00]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) But sometimes it can successfully upload new build... Xcode 26.2.
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
3w
Reply to Xcode Cloud builds stuck at App Store Connect
Same issue here. I've been trying to build a new version with xcode cloud since last night (14 hours ago). They all get stuck at 93%. I've tried with a fresh branch, retried existing builds, nothing seems to work. The changes seems minimal (just some small UI things). It really seems like xcode cloud is having issues, but nothing is reported on the xcode cloud status page.
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
3w
Reply to Xcode 26 CompileMetalFile failed
Encountered the same problem here. Looks like we require elevated rights to mount the toolchain, and maybe Xcode's helper doesn't have the privileges? I resorted to writing a Launch Service to auto-mount the toolchain for me. https://christiantietze.de/posts/2026/01/auto-mount-metal-toolchain-using-launchd-because-xcode-wont/
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3w
Reply to Library not loaded: @rpath/libswiftCompatibilitySpan.dylib – Building bundle target
I figured out a workaround: Add a new “Copy Files” build phase to the target with the destination “Frameworks” with the following file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift-6.2/macosx/libswiftCompatibilitySpan.dylib That is, copying the libswiftCompatibilitySpan.dylib file manually into the “Frameworks” directory of the bundle. The bundle now loads on older OS versions like macOS 15. However, this workaround is not a good solution as it requires me to manually find the libswiftCompatibilitySpan.dylib file and ensure to keep its path updated in the Xcode project settings each time the toolchain is updated. Ideally, Xcode would recognize that libswiftCompatibilitySpan.dylib is linked using rpath and include the file in the “Frameworks” directory automatically. Maybe there is a build setting that I need to enable that would do this, but I could not find anything.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3w
Reply to Universal Links are not working in the Xcode 26 simulators
We have validated the below cases, Updated the Xcode to the latest version Cleared simulator cache Verified AASA file using above terminal command Couldn't obtain any info from the Console logs as well. Note: In the same Xcode version, universal links for working fine in different application. Issue occurring only for our application. We need info about where can we verify the universal link setup of my simulator.
Topic: Community SubTopic: Apple Developers
3w
Reply to Xcode Cloud builds stuck at App Store Connect
I think we're having the same problem. Xcode Cloud build was stuck on Prepare Build for App Store Connect for 13 hours. App Store Connect was showing the build as Processing. This morning I cancelled the build. Xcode Cloud status is Cancelled, but App Store Connect still showing as Processing. Started a new build. Same issue. So now we have two builds stuck on Processing. I contacted support with details. Case ID is 102802250079
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
3w
Reply to Incorrect packet handling in SMBClient MacOS 26.
If I’m reading FB21249476 correctly, there should be improvements in this space in Xcode 26.3b2 (25D5101c) [1]. I recommend that you re-test with that build. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] This only just started seeding, so Feedback Assistant hasn’t had time to notify you about it.
Topic: App & System Services SubTopic: Core OS Tags:
3w