“build disappears”

Posting this wondering anyone from App Review may be able to help. I submitted two builds for External TestFlight builds. My iOS build got approved within a day, but my tvOS version is still stuck in waiting for review for four days now. Wondering if there's anything I can do, perhaps remove from review and re-upload a new build or will this effectively remove me from a queue? Many thanks in advance. I'm unable to find a submission ID for this as I assume they're not available for TestFlight reviews?

Hello, I’m building an iOS video player using AVPlayer and a custom playback queue. I implemented remote controls using MPRemoteCommandCenter and enabled: nextTrackCommand previousTrackCommand playCommand pauseCommand I disabled: skipForwardCommand skipBackwardCommand seekForwardCommand seekBackwardCommand I also set queue metadata in MPNowPlayingInfoCenter: MPNowPlayingInfoPropertyPlaybackQueueIndex MPNowPlayingInfoPropertyPlaybackQueueCount Even with these commands enabled and the queue count greater than 1, the iOS lock screen continues to display the 10-second skip buttons instead of the previous/next track buttons. The commands themselves work correctly when triggered externally (Control Center, headphones, etc.), but the UI still shows the skip controls. Is there a way to force the lock screen UI to display previous / next track buttons for a video playlist? Or is this behavior expected when using AVPlayer with video content? Thanks.

My team is distributing a cross-platform app outside the Mac App Store via ZIP file. The app works perfectly on Windows, but on macOS, while the ZIP downloads and extracts without issue, the app refuses to open. Users see either the app appear in the dock then immediately disappear or a Gatekeeper prompt saying the developer cannot be verified. We suspect the root cause is related to code signing and/or notarization, but we're not entirely sure where the breakdown is occurring. We have a few questions as we work through this. For ZIP-based distribution outside the Mac App Store, is both a Developer ID certificate and Apple notarization required on current macOS versions? We've also seen references to using ditto instead of Finder's built-in Compress option when packaging the ZIP. Is that necessary to properly preserve the app bundle structure and extended attributes? Any guidance on where this process might be going wrong would be hugely appreciated. Thanks!

Hello, Does app review depend on app reviewers availability? And holidays etc? IS there a maximum number of days that an app has to be reviewed before end of that period? In other words: if an app is posted, a review HAS TO HAPPEN before x days, is a rule (hopefully) or no? Once an an app has been reviewed once, and you send a new build (that addresses the fixes) for example you add the sign in with Apple if you forgot to add it next to sign in with another method, does the second round of review have to be done by the SAME REVIEWER first time or can it be done by a second reviewer? I have posted and have been waiting since 5 days now (since 5 march) Are we allowed to post many apps at once? I mean as a developer I can take time working in multiple apps, then suddenly deciding to publish them all, that is okay right? Are their limitation or expected published flow to have? Once an app has been approved and published, will the waiting times for updates (new versions of the app) reviews smaller hopeful

I am a beta tester. I successfully tested an app this week. However, a different app, by a different developer is generating the “TestFlight is unavailable. Try again” error. I have force closed, and then deleted the TF app, and restarted A16 iPad running 26.3.1 iPadOS, then redownloaded to no effect. I have worked with an Apple Senior Support advisor, and found no network, Apple ID problems on my end after troubleshooting for nearly 2 hours. The developer tried emailing me the link - didn’t work. Now, update builds by developer are now showing the same error on other beta testers iPads, - however, one tester can download the app for beta testing on an iPad Pro M4. The app will download to my phone as well as others´ phones, running current update, but not my iPad. I changed my Apple ID password, reset my network, and nothing works.

I tried to build my project with -fsanitize=fuzzer. This failed to link with libclang_rt.fuzzer_osx.a not found when attempting to link the code. I mean really!! Why on earth would you exclude this from the version of clang that ships with XCode!

Hi everyone, We are facing a critical blocker with our macOS app processing. Since March 5, 2026, every single build we have uploaded (8 builds total) has been stuck in the Processing state for over 4 days. For our project, due to the large binary size, processing usually takes about 4 to 6 hours normally. However, we now have a long queue of builds that haven't transitioned to Ready to Submit for up to 80+ hours. Stuck Builds List: 1.0.0 (444): Mar 8, 3:09 PM (Processing) 1.0.0 (443): Mar 8, 5:36 AM (Processing) 1.0.0 (440): Mar 7, 6:37 AM (Processing) 1.0.0 (438): Mar 6, 5:01 PM (Processing) 1.0.0 (434): Mar 6, 12:04 AM (Processing) 1.0.0 (433): Mar 5, 6:26 PM (Processing) 1.0.0 (432): Mar 5, 10:51 AM (Processing) 1.0.0 (431): Mar 5, 6:11 AM (Processing) (Note: The last successful build was 1.0.0 (429) on March 4, which processed within the expected 6-hour window.) There have been no changes to our project settings, Info.plist, or entitlements since the last succ

Hey everyone, I found a possible SwiftData Release-only issue with nested sort descriptors on an optional relationship. In a minimal repro, sorting a @Query by a nested optional relationship key path like: SortDescriptor(InvestigationPhotoAsset.imageAnalysis?.overallAestheticsScore, order: .reverse) works in Debug, but crashes at runtime in Release. The surprising part is that the crash depends on file layout: if the active SwiftData models and the sort logic are kept in the same Swift file, the app works if the same models are split into separate files, the Release build crashes, 'Debug' will also work The repro was reduced to just two SwiftData models: InvestigationPhotoAsset InvestigationImageAnalysis So this looks less like an app-modeling issue and more like a SwiftData/compiler/codegen issue related to nested sort metadata in optimized builds. If useful, I can also give you a slightly more formal version with a title and code snippet block. Please check out the code example here Has an

I am building a simple iOS app that shows the total phone usage time for today using the Screen Time APIs. Architecture: Main app → requests authorization using AuthorizationCenter.shared.requestAuthorization(for: .individual) → displays a DeviceActivityReport Report extension → DeviceActivityReportExtension → calculates total usage using DeviceActivityResults → shows the number in a SwiftUI view The report works correctly. The extension successfully calculates the total usage and displays it on screen. Example logic inside the report extension: for await activityData in data { for await segment in activityData.activitySegments { totalSeconds += segment.totalActivityDuration } } let totalMinutes = Int(totalSeconds / 60) The problem: I need the main app to access that number so I can store it daily in my own database. I tried to send the value from the extension to the main app using: App Group + UserDefaults(suiteName:) App Group + shared file (FileManager.containerURL) writing inside makeConfigurati

My app was rejected because Apple’s reviewers couldn’t sign in with Google or iCloud on iOS 26.3. The problem is, I can’t reproduce the issue on any iOS 26.x version, including 26.3.1, which I suspect actually fixes whatever was broken in 26.3. I’ve replied to App Review asking for more details and a screen recording, but now I’m stuck waiting 3 days for a response while Apple’s own review system is apparently still running the buggy 26.3 build. Has anyone else been rejected for this recently? And does anyone know if there’s a way to get the iOS 26.3 simulator runtime now that Components only offers 26.3.1? Any tips for speeding up the back-and-forth with App Review in a case like this would also be appreciated.

Hi everyone, I’m looking for some insight or advice on a persistent review delay. My app, has been stuck in the Waiting for Review status since Feb 9th. I thought it got glitched or whatsoever so I rejected and resubmitted a week ago March 2nd. and yet its still in waiting for review status. I applied for expedite review with case ID: 102825200414 I have already: Verified that all metadata is complete. Ensured there are no Action Required flags or Metadata Rejected notices. Checked that the Availability date is set to As soon as it is approved. Confirmed the build runs perfectly in TestFlight.

Even when making a completely fresh Unity project, if I include ARKit and upload it to testflight, when I open it on my ipad it says 'Couldn't Load App'. If I don't include testflight the app opens fine. If I build the app directly to my ipad the app works fine. It opens if I set ARKit to 'optional' but then the AR doesn't work. I have included a camera and location usage description so it's not that. Really not sure what's going on, any help would be massively appreciated!

With Xcode 26.3, and beta 26.4 (under macOS 26.4 Beta (25E5223i)) my loaded platforms for canvas and simulators keep disappearing. Try to add platforms, and the download just sits there.