build disappears

I am having the same issue. The entire context (Action) menu has disappeared. Certainly this isn't a major oversight.

I've found that adding the following to ci_pre_xcodebuild.sh fixes the issue for me: # Get Xcode major version # `xcodebuild -version` returns something like: # Xcode 26.0.1 # Build version 17A400 XCODE_VERSION=$(xcodebuild -version | head -n 1 | awk '{print $2}' | cut -d. -f1) if [ $XCODE_VERSION -ge 26 ]; then if xcodebuild -showComponent metalToolchain >/dev/null 2>&1; then echo Metal toolchain is installed else echo Metal toolchain is not installed. Failing the build. exit 1 fi fi

I have found that adding this to ci_pre_xcodebuild.sh solves my problem when using 26.0.1: # Get Xcode major version # `xcodebuild -version` returns something like: # Xcode 26.0.1 # Build version 17A400 XCODE_VERSION=$(xcodebuild -version | head -n 1 | awk '{print $2}' | cut -d. -f1) if [ $XCODE_VERSION -ge 26 ]; then if xcodebuild -showComponent metalToolchain >/dev/null 2>&1; then echo Metal toolchain is installed else echo Metal toolchain is not installed. Failing the build. exit 1 fi fi

CloudKit Push Notifications Not Delivering - Extensive Debugging Completed Issue Summary CloudKit subscriptions are properly configured and triggering, but push notifications are never delivered to devices. After extensive debugging, I've isolated the issue to CloudKit→APNS delivery failure. Environment Xcode: 15.x iOS Target: 17.0+ watchOS Target: 10.0+ CloudKit Database: Both Public and Private Testing Devices: iPhone 15 Pro, Apple Watch Series 9 Environments Tested: Development and Production What's Working ✅ 1. CloudKit Subscriptions All 6 subscription types successfully created and visible in CloudKit Dashboard Subscriptions persist across app launches (verified in dashboard) Subscription predicates correctly configured for each record type: // Example: FriendRequest subscription NSPredicate(format: toUser == %@, userRecordID) // Example: Challenge subscription NSPredicate(format: recipientID == %@ AND status == %@, userRecordID, pending) 2. Device Registration • App successfully requests and receives pu

Regarding your first issue, I asked about that internally. It seems that there’s been a delay with it at our end. I’m hoping that we can clear that soon. I’ve sent a reminder to check on this around the middle of next week. Regarding your submission issue, your bug (FB19582905) kinda got lost )-: [1] However, App Store Connect is now accepting iOS 26 SDK uploads, so it’s possible that this has just fixed itself. Please try uploading again and reply back here with your results. IMPORTANT Don’t pass that build on to App Review, because it won’t work for them until we resolve the first issue. However, you should still be able to upload to App Store Connect. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Normally I check that bugs land in the right place when I see them mentioned here on the forums, and I did that for FB19582905. However, things went wrong after I did my check )-:

Thanks for the rapid reply! Apologies, my question was vague in hindsight, but your answers very helpful and reviewing the materials you shared plus some extra research, I have straightened out my understanding. I'm new to iOS and navigating the various audio APIs. I am building an iOS app, audio-only (no VR/AR/game engine) with a UI to play back head-tracked audio using third order ambisonics (i.e. binauralising using head position with reference to the more detailed positional information in 3OA). I'm looking to overlay other spatialised audio features which are a bit much for this thread as it's focused on ASAF and the codec, but basically I've been seeking to understand which APIs support ambisonics and where ASAF/APAC fits into the existing picture. Now I've got a grip on APAC compatibility and conversion method (I came across this as well: https://developer.apple.com/av-foundation/Apple-Positional-Audio-Codec.pdf), I'll take this away and have a play. I've also familiarised myself with ambisoni

Hello, I’m experiencing a very unusual problem when using VirtioFS with the Apple Virtualization Framework and Docker, through tools such as Lima and Tart. I’ve described the full details here: lima-vm/lima#4053 (comment), but here’s a quick summary. Steps to Reproduce Given a directory structure like this: mkdir -p local-test-dir/dir and running the following command: docker run -u $(id -u) --rm -v $PWD/dir:/mnt/dir alpine:latest sh -c ls -al /mnt the output is: total 8 drwxr-xr-x 1 root root 4096 Sep 23 22:48 . drwxr-xr-x 1 root root 4096 Sep 23 22:48 .. drwxr-xr-x 2 root root 64 Sep 19 21:34 dir # <-- INCORRECT The directory appears as root:root, which is wrong. Workaround If I add an artificial sleep of more than 0.9s before listing the directory, the issue disappears: docker run -u 501 --rm -v $PWD/dir:/mnt/dir alpine:latest sh -c sleep 0.9; ls -al /mnt Output: total 8 drwxr-xr-x 1 root root 4096 Sep 23 22:48 . drwxr-xr-x 1 root root 4096 Sep 23 22:48 .. drwxr-xr-x 2 501 root 64 Sep 19 21:34