Search results for

“build disappears”

51,300 results found

Post

Replies

Boosts

Views

Activity

Reply to Unable to install Metal toolchain through Xcode Cloud
removing the script didn't fix for me. the script had been holding it together till now, but something changed recently. Ok — since this sounds like a recent change, it would be helpful for us to get a bug report from you so we can look into this further. It would be helpful if you could detail the exact configuration you've set for this build environment (macOS version and Xcode versions), and a link to a specific build. Once that's filed, please post the FB number here so I can locate your report. — Ed Ford,  DTS Engineer
3w
Reply to New project with new AppIntent throws build error
To see what happened here, I used Xcode 26.4 beta 3 to create a new multi-platform app. I added a new file, added an import statement for App Intents, and then copied in the snippet of getting started code from the documentation. Indeed, this fails to compile. That new project's default build setting configuration is: Swift Langage Version: Swift 5 Approachable Concurrency: Yes Default Actor Isolation: MainActor To allow this to compile, I change the Default Actor Isolation build setting to nonisolated instead. This is worth a bug report — please use Feedback Assistant to report it, and post the FB number here so I can follow up on it. — Ed Ford,  DTS Engineer
3w
Reply to Live Activity doesn't open watchOS app
I struggled for some time as well. Just follow what they explain in their video from WWDC 2024 Bring your Live Activity to Apple Watch. There they explain that you need a key: WKSupportsLiveActivityLaunchAttributeTypes as written above. But setting it in the Info.plist is not enough for my project. It only works if you: go to your watch target -> build settings. Select all. Under Info.plist Values you will find the key: Supports Launch for Live Activity Attribute Types. To add an empty value there did not work for me. So, as in the video, I added my Attributes in my case called NameofmyappAttributes. Having this set, now tapping on the LA on the watch starts the watch app. Took me many hours to figure that out.
3w
Reply to Getting a basic URL Filter to work
Still banging my head on this 😬 Thanks to the author of the gateway software I’m using we figured out those errors, and everything seems good on that front. Still getting a lot of Bad Request, Evaluation key not found errors during queries. The sample project documentation says these should happen when the server is restarted bc old keys are cached, but they happen all the time. Still, this is only on the /queries endpoint, which is not involved in setup (afaik). The client is still at times throwing this on TestFlight builds: : -[NEPIRChecker start:responseQueue:completionHandler:] - failed to register with PIR for Group site.kaylees.Wipr2 usecase site.kaylees.Wipr2.url.filtering The thing is, all other endpoints always work with no issues: /.well-known/private-token-issuer-directory, /token-key-for-user-token, /issue, /config, and /key are always successful. As far as I can tell, this should be enough for registration. What exactly does the failed to register with PIR error mean?
3w
App stuck in “Ready for Review” for many days – is there currently a delay in App Review?
Hello everyone, I would like to ask if other developers are currently experiencing long delays to approve an app. In my case, my macOS app update (version 1.1) has been stuck in “Ready for Review” for more than 8 days without entering the review phase. Timeline: • Feb 21 – Initial submission • Feb 22 – In Review • Feb 25 – Rejected • Feb 25 – Resubmitted • Mar 2 – In Review • Mar 2 – Rejected • Mar 5 (Wednesday) – Submitted again → Ready for Review • Today – Still Ready for Review, never entered In Review All issues mentioned in the previous rejections were fixed and the build was resubmitted successfully. What also confuses me is that in the App Review section I see a red exclamation mark, even though there are no unresolved messages and the build shows as submitted. I would like to ask: • Are others currently seeing unusually long delays? • Could this indicate a queue issue or system problem? • Has Apple changed something recently in the review pipeline? Normally my previous versions were
0
0
42
3w
Reply to Xcode Devices "Download Container" no longer works on latest Xcode 26.0 (24228) (Build 17A324)
I have same problem with Xcode 26.3 Bun on Xcode 16.4 - Download Container worked User Info: { DVTErrorCreationDateKey = 2026-03-11 14:49:00 +0000; NSURL = file:///Users/alexander/Developer/..../AppData/Library/SplashBoard/Snapshots/; } -- The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { NSURL = file:///Users/alexander/Developer/..../AppData/Library/SplashBoard/Snapshots/; } -- The request from the client is missing one or more required fields: A valid filename cannot end in a path separator character Domain: com.apple.dt.remoteservices.error Code: 11015 -- System Information macOS Version 15.7.4 (Build 24G517) Xcode 26.3 (24587) (Build 17C529) Timestamp: 2026-03-11T17:49:00+03:00
3w
Increase Contrast reduces List selection contrast in dark appearance in SwiftUI NavigationSplitView
[Submitted as FB22200608] With Increase Contrast turned on, the selected row highlight in a List behaves inconsistently between light and dark appearance on iPad. In light appearance the blue selection highlight correctly becomes darker, but in dark appearance it becomes lighter instead. The text contrast ratio drops from about 3:1 to about 1.5:1, well below accessibility guidelines. This reproduces both in the simulator and on a physical device. The sample uses a standard SwiftUI List inside NavigationSplitView with built-in selection styling. No custom colors or styling are applied. REPRO STEPS Create a new Multiplatform project. Replace ContentView with code below. Build and run on iPad. Select an item in the list. Turn on Dark appearance (Cmd-Shift-A in Simulator). Turn on Increase Contrast (Cmd-Control-Shift-A in Simulator). Observe the selected row highlight. ACTUAL In light appearance, the blue selection highlight becomes darker when Increase Contrast is on, improving contrast as expected. In
4
0
260
3w
App not showing on App Store Connect
Why is my App new build not showing on App Store Connect if it is ready for Distribution? It only shows the previous build. I received this confirmation email about 12 hours ago. Dear Our Maids, Inc., The following build has completed processing: Platform: iOS App Name: OurMaids Build Number: 10 Version Number: 1.1.1 App SKU: com.ourmaids.mobileapp App Apple ID: 6760357291 You can now use this build for TestFlight testing or submit it for distribution. If you have any questions regarding your app, contact us.
0
0
32
3w
Please, Apple. I am begging you. Fix the broken Text-To-Speech in macOS
Every new build of macOS 26 further breaks some part of text-to-speech or voice control. I have filed multiple bug reports on this, yet the situation gets worse, not better, with each new build. I am begging you to fix this! I am disabled and rely on these features to work. Accessibility in macOS is more than 50% of my reasons for choosing Macs over Windows. Here's some of what is currently broken: Speak announcements only works if the Samantha voice is selected. If other voices are selected either the announcements don't speak, or they default to the Samantha voice. This became broken with 26.1. Announce the time only works with some voices. I would like to use Australian English Siri 2 but with that voice selected it defaults to Samantha. This became broken with 26.4. With voice control enabled there are two menu bar icons. The blue voice control icon and an orange microphone an application is accessing the microphone icon. This orange icon started appearing with 26.3. For four years of ma
9
0
2.5k
3w
Reply to Initial stack construction
I've done a lot more work on this, and I have the impression that this is a bug in macOS, at least on 12 and 13 Intel. #include #include #include #include #include #include // used for debugging apple pointer issues, see // https://bugs.kde.org/show_bug.cgi?id=517304 #define DEBUG_ENV // On Darwin there's this secret fourth argument, 'apple'. // That's kind of like a cut down obfuscated version of auxv. // For the moment we only support the first entry, executable_path= int main(int argc, char *argv[], char *envp[], char *apple[]) { char *pargv = calloc((PATH_MAX+1), sizeof(char)), *pappl = calloc((PATH_MAX+1), sizeof(char)); int i; for (i = 0; envp[i]; i++) { #if defined(DEBUG_ENV) fprintf(stderr, apple-main-arg: i %d &envp[i] %p envp[i] %sn, i, &envp[i], envp[i]); #endif } #if defined(DEBUG_ENV) fprintf(stderr, 2 slots after envpn); fprintf(stderr, apple-main-arg: i %d &envp[i] %p envp[i] %sn, i, &envp[i], envp[i]); fprintf(stderr, apple-main-arg: i %d &envp[i] %p envp[i] %sn, i+1,
3w
Build stuck in “Waiting for Review” for weeks (resubmission also waiting) - anyone seeing this recently?
Hello everyone, I want to check whether other developers are seeing similar App Review delays recently. Timeline: Feb 3, 2026: Submitted initial build Feb 3 - Mar 7, 2026: Stayed in Waiting for Review (never entered active review) Mar 7, 2026: Cancelled and resubmitted a new build As of now: New build is still in Waiting for Review I contacted Developer Support; they said system status appears normal and advised me to continue waiting. I’m not asking for expedited approval here. I just want to understand: Are others seeing the same pattern in this period? Is this likely a broader queue slowdown rather than a submission-specific issue? Any recent data points are appreciated. Thanks.
4
0
192
3w
Unable to access sourceIcon URL in AccessoryNotification.File - AccessoryError error 0
Environment iOS Version: 26.4 Beta (Build 17E5170d) Xcode Version: 26.4 Beta Framework: AccessoryNotifications, AccessoryTransportExtension Description When implementing AccessoryNotifications.NotificationsForwarding.AccessoryNotificationsHandler, I'm unable to retrieve the URL for sourceIcon from AccessoryNotification. The file.url property throws AccessoryError error 0 with the message unable to get file URL. Code Sample func add( notification: AccessoryNotification, alertingContext: AlertingContext, alertCoordinator: any AlertCoordinating ) { Task { if let sourceIcon = notification.sourceIcon { do { let url = try await sourceIcon.url // Throws AccessoryError error 0 let data = try Data(contentsOf: url) // Process icon data... } catch { print(Failed to get sourceIcon URL: (error)) // Error: The operation couldn't be completed. // (AccessoryNotifications.AccessoryError error 0.) } } } } Observed Behavior The sourceIcon property is present and its type is correctly reported as public.image: │ sourceI
0
0
66
3w
Reply to Build stuck in “Waiting for Review” for weeks (resubmission also waiting) - anyone seeing this recently?
Hi, thanks for sharing this. Since Apple mentioned the issue has been resolved, I was wondering if your build has been reviewed or approved yet?
Replies
Boosts
Views
Activity
3w
Reply to Unable to install Metal toolchain through Xcode Cloud
removing the script didn't fix for me. the script had been holding it together till now, but something changed recently. Ok — since this sounds like a recent change, it would be helpful for us to get a bug report from you so we can look into this further. It would be helpful if you could detail the exact configuration you've set for this build environment (macOS version and Xcode versions), and a link to a specific build. Once that's filed, please post the FB number here so I can locate your report. — Ed Ford,  DTS Engineer
Replies
Boosts
Views
Activity
3w
Reply to New project with new AppIntent throws build error
To see what happened here, I used Xcode 26.4 beta 3 to create a new multi-platform app. I added a new file, added an import statement for App Intents, and then copied in the snippet of getting started code from the documentation. Indeed, this fails to compile. That new project's default build setting configuration is: Swift Langage Version: Swift 5 Approachable Concurrency: Yes Default Actor Isolation: MainActor To allow this to compile, I change the Default Actor Isolation build setting to nonisolated instead. This is worth a bug report — please use Feedback Assistant to report it, and post the FB number here so I can follow up on it. — Ed Ford,  DTS Engineer
Replies
Boosts
Views
Activity
3w
Reply to auto-renewable subscriptions
Have you searched this site? I've answered similar questions several times in the past. Once you click on the submission button, the said section will disappear.
Replies
Boosts
Views
Activity
3w
Reply to Live Activity doesn't open watchOS app
I struggled for some time as well. Just follow what they explain in their video from WWDC 2024 Bring your Live Activity to Apple Watch. There they explain that you need a key: WKSupportsLiveActivityLaunchAttributeTypes as written above. But setting it in the Info.plist is not enough for my project. It only works if you: go to your watch target -> build settings. Select all. Under Info.plist Values you will find the key: Supports Launch for Live Activity Attribute Types. To add an empty value there did not work for me. So, as in the video, I added my Attributes in my case called NameofmyappAttributes. Having this set, now tapping on the LA on the watch starts the watch app. Took me many hours to figure that out.
Replies
Boosts
Views
Activity
3w
Reply to Getting a basic URL Filter to work
Still banging my head on this 😬 Thanks to the author of the gateway software I’m using we figured out those errors, and everything seems good on that front. Still getting a lot of Bad Request, Evaluation key not found errors during queries. The sample project documentation says these should happen when the server is restarted bc old keys are cached, but they happen all the time. Still, this is only on the /queries endpoint, which is not involved in setup (afaik). The client is still at times throwing this on TestFlight builds: : -[NEPIRChecker start:responseQueue:completionHandler:] - failed to register with PIR for Group site.kaylees.Wipr2 usecase site.kaylees.Wipr2.url.filtering The thing is, all other endpoints always work with no issues: /.well-known/private-token-issuer-directory, /token-key-for-user-token, /issue, /config, and /key are always successful. As far as I can tell, this should be enough for registration. What exactly does the failed to register with PIR error mean?
Replies
Boosts
Views
Activity
3w
App stuck in “Ready for Review” for many days – is there currently a delay in App Review?
Hello everyone, I would like to ask if other developers are currently experiencing long delays to approve an app. In my case, my macOS app update (version 1.1) has been stuck in “Ready for Review” for more than 8 days without entering the review phase. Timeline: • Feb 21 – Initial submission • Feb 22 – In Review • Feb 25 – Rejected • Feb 25 – Resubmitted • Mar 2 – In Review • Mar 2 – Rejected • Mar 5 (Wednesday) – Submitted again → Ready for Review • Today – Still Ready for Review, never entered In Review All issues mentioned in the previous rejections were fixed and the build was resubmitted successfully. What also confuses me is that in the App Review section I see a red exclamation mark, even though there are no unresolved messages and the build shows as submitted. I would like to ask: • Are others currently seeing unusually long delays? • Could this indicate a queue issue or system problem? • Has Apple changed something recently in the review pipeline? Normally my previous versions were
Replies
0
Boosts
0
Views
42
Activity
3w
Reply to Xcode Cloud: Unable to Notarize macOS App (Stuck in Infinite Waiting)
Similar issue. No errors, notarization just stalls with the message: Processing the build submission...
Replies
Boosts
Views
Activity
3w
Reply to Xcode Devices "Download Container" no longer works on latest Xcode 26.0 (24228) (Build 17A324)
I have same problem with Xcode 26.3 Bun on Xcode 16.4 - Download Container worked User Info: { DVTErrorCreationDateKey = 2026-03-11 14:49:00 +0000; NSURL = file:///Users/alexander/Developer/..../AppData/Library/SplashBoard/Snapshots/; } -- The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { NSURL = file:///Users/alexander/Developer/..../AppData/Library/SplashBoard/Snapshots/; } -- The request from the client is missing one or more required fields: A valid filename cannot end in a path separator character Domain: com.apple.dt.remoteservices.error Code: 11015 -- System Information macOS Version 15.7.4 (Build 24G517) Xcode 26.3 (24587) (Build 17C529) Timestamp: 2026-03-11T17:49:00+03:00
Replies
Boosts
Views
Activity
3w
Increase Contrast reduces List selection contrast in dark appearance in SwiftUI NavigationSplitView
[Submitted as FB22200608] With Increase Contrast turned on, the selected row highlight in a List behaves inconsistently between light and dark appearance on iPad. In light appearance the blue selection highlight correctly becomes darker, but in dark appearance it becomes lighter instead. The text contrast ratio drops from about 3:1 to about 1.5:1, well below accessibility guidelines. This reproduces both in the simulator and on a physical device. The sample uses a standard SwiftUI List inside NavigationSplitView with built-in selection styling. No custom colors or styling are applied. REPRO STEPS Create a new Multiplatform project. Replace ContentView with code below. Build and run on iPad. Select an item in the list. Turn on Dark appearance (Cmd-Shift-A in Simulator). Turn on Increase Contrast (Cmd-Control-Shift-A in Simulator). Observe the selected row highlight. ACTUAL In light appearance, the blue selection highlight becomes darker when Increase Contrast is on, improving contrast as expected. In
Replies
4
Boosts
0
Views
260
Activity
3w
App not showing on App Store Connect
Why is my App new build not showing on App Store Connect if it is ready for Distribution? It only shows the previous build. I received this confirmation email about 12 hours ago. Dear Our Maids, Inc., The following build has completed processing: Platform: iOS App Name: OurMaids Build Number: 10 Version Number: 1.1.1 App SKU: com.ourmaids.mobileapp App Apple ID: 6760357291 You can now use this build for TestFlight testing or submit it for distribution. If you have any questions regarding your app, contact us.
Replies
0
Boosts
0
Views
32
Activity
3w
Please, Apple. I am begging you. Fix the broken Text-To-Speech in macOS
Every new build of macOS 26 further breaks some part of text-to-speech or voice control. I have filed multiple bug reports on this, yet the situation gets worse, not better, with each new build. I am begging you to fix this! I am disabled and rely on these features to work. Accessibility in macOS is more than 50% of my reasons for choosing Macs over Windows. Here's some of what is currently broken: Speak announcements only works if the Samantha voice is selected. If other voices are selected either the announcements don't speak, or they default to the Samantha voice. This became broken with 26.1. Announce the time only works with some voices. I would like to use Australian English Siri 2 but with that voice selected it defaults to Samantha. This became broken with 26.4. With voice control enabled there are two menu bar icons. The blue voice control icon and an orange microphone an application is accessing the microphone icon. This orange icon started appearing with 26.3. For four years of ma
Replies
9
Boosts
0
Views
2.5k
Activity
3w
Reply to Initial stack construction
I've done a lot more work on this, and I have the impression that this is a bug in macOS, at least on 12 and 13 Intel. #include #include #include #include #include #include // used for debugging apple pointer issues, see // https://bugs.kde.org/show_bug.cgi?id=517304 #define DEBUG_ENV // On Darwin there's this secret fourth argument, 'apple'. // That's kind of like a cut down obfuscated version of auxv. // For the moment we only support the first entry, executable_path= int main(int argc, char *argv[], char *envp[], char *apple[]) { char *pargv = calloc((PATH_MAX+1), sizeof(char)), *pappl = calloc((PATH_MAX+1), sizeof(char)); int i; for (i = 0; envp[i]; i++) { #if defined(DEBUG_ENV) fprintf(stderr, apple-main-arg: i %d &envp[i] %p envp[i] %sn, i, &envp[i], envp[i]); #endif } #if defined(DEBUG_ENV) fprintf(stderr, 2 slots after envpn); fprintf(stderr, apple-main-arg: i %d &envp[i] %p envp[i] %sn, i, &envp[i], envp[i]); fprintf(stderr, apple-main-arg: i %d &envp[i] %p envp[i] %sn, i+1,
Replies
Boosts
Views
Activity
3w
Build stuck in “Waiting for Review” for weeks (resubmission also waiting) - anyone seeing this recently?
Hello everyone, I want to check whether other developers are seeing similar App Review delays recently. Timeline: Feb 3, 2026: Submitted initial build Feb 3 - Mar 7, 2026: Stayed in Waiting for Review (never entered active review) Mar 7, 2026: Cancelled and resubmitted a new build As of now: New build is still in Waiting for Review I contacted Developer Support; they said system status appears normal and advised me to continue waiting. I’m not asking for expedited approval here. I just want to understand: Are others seeing the same pattern in this period? Is this likely a broader queue slowdown rather than a submission-specific issue? Any recent data points are appreciated. Thanks.
Replies
4
Boosts
0
Views
192
Activity
3w
Unable to access sourceIcon URL in AccessoryNotification.File - AccessoryError error 0
Environment iOS Version: 26.4 Beta (Build 17E5170d) Xcode Version: 26.4 Beta Framework: AccessoryNotifications, AccessoryTransportExtension Description When implementing AccessoryNotifications.NotificationsForwarding.AccessoryNotificationsHandler, I'm unable to retrieve the URL for sourceIcon from AccessoryNotification. The file.url property throws AccessoryError error 0 with the message unable to get file URL. Code Sample func add( notification: AccessoryNotification, alertingContext: AlertingContext, alertCoordinator: any AlertCoordinating ) { Task { if let sourceIcon = notification.sourceIcon { do { let url = try await sourceIcon.url // Throws AccessoryError error 0 let data = try Data(contentsOf: url) // Process icon data... } catch { print(Failed to get sourceIcon URL: (error)) // Error: The operation couldn't be completed. // (AccessoryNotifications.AccessoryError error 0.) } } } } Observed Behavior The sourceIcon property is present and its type is correctly reported as public.image: │ sourceI
Replies
0
Boosts
0
Views
66
Activity
3w