“build disappears”

Hi everyone, We recently submitted an update for our existing iOS application and just wanted to verify that everything looks correct on our side in App Store Connect. The previous version of the app was approved and is currently live on the App Store. This new submission is a small update that improves some UI elements and adds minor usability improvements for our customers. At the moment the build is still waiting for review, and since we are coordinating this update with our client rollout schedule, we wanted to confirm that there are no issues with the submission metadata or the selected build. If anyone from the App Review team happens to see this and can confirm that the submission looks complete, we would really appreciate it. App ID: 6759172913 Thank you very much for your time and support. Kind regards, José Rodríguez

When building a SwiftUI project in Xcode 26.3, Swift compilation fails in the Release configuration with Optimization Level set to -O, when the iOS deployment target is lower than iOS 26 (e.g. iOS 16, 17, or 18). The failure occurs when using a generic class conforming to ObservableObject that contains a @Published property. The same code: Compiles successfully in Xcode 16.3 (Release, -O) with iOS 16/17/18 Compiles successfully in Xcode 26.x when the deployment target is set to iOS 26 Compiles successfully in Xcode 26.x Debug configuration (-Onone) Compiles successfully in Xcode 26.x Release when optimization is disabled (-Onone) However, in Xcode 26.3, the build consistently fails in Release (-O) when targeting iOS 16, 17, or 18. This appears to be a Swift compiler optimization issue related to generics, ObservableObject, @Published, and back-deployment to iOS versions prior to iOS 26. STEPS TO REPRODUCE Create a new SwiftUI App project using Xcode 26.3. Leave all project settings at defaul

I'm struggling to build a driver for iPadOS in a particular project configuration. If I put the driver code and dext target into the same Xcode project which contains the iPad app, all is well. This is the way the Xcode driver template does it. However, I'd like to build and debug the dext on macOS, while eventually deploying on iPadOS. So I put the dext into a different project, which has a macOS target, a minimal iPadOS target and a DriverKit target. I made a workspace which contains both projects. I dragged the macOS project into the iPadOS project so that I can refer to the products of the macOS project (specifically, its driver target) as a dependency of the iPadOS target. Note that the main iPad app target depends on the driver target. So the workspace organization looks like this: Workspace iPad project main iPad app target (depends on driver) test project reference test project test macOS/iPad app target DriverKit dext target When I build the iPadOS target, it builds

I use spm manage swift package, now i want my macos app support arm64e,so i add arm64e in Build Srtting -> Architectures. but i got error Could not find module 'SwiftyJSON' for target 'arm64e-apple-macos'; found: arm64-apple-macos, x86_64-apple-macos Apparently, if no limit in Package.swift, SPM will only compile versions for x86 and ARM64 architectures by default. now, how should I configure SPM to compile the arm64e version? thanks

Hello everyone, I’m experiencing an issue with the review process for my app on App Store Connect. My app has been stuck in “Waiting for Review” for over 30 days, and the review process has not started yet. Initially, I submitted the build on February 9, but the status remained “Waiting for Review” for a long time and never moved to “In Review.” Because of this, I canceled the submission and resubmitted the build on February 17. However, even after resubmitting, the app is still stuck in “Waiting for Review.” I also submitted a request for an expedited review, but unfortunately I have not received any response regarding that request either. Since the app status is still “Waiting for Review,” the Resolution Center option is not available yet, so I cannot contact the App Review team directly from there. I also attempted to contact Apple Developer Support but have not received a response yet. Has anyone experienced a similar situation where the app remained in “Waiting for Review” for this long

gettitng this error and also more than 30day longs wait on build reviews { errors : [ { id : , status : 422, code : ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING, title : Beta contract is missing for the app., detail : Beta Contract is missing. } ] }

Our app Miiro (App ID: 6759159052) was rejected for Guideline 3.1.2(c) on March 13. We fixed the pricing hierarchy on the paywall (yearly price now displayed as primary, monthly equivalent as subordinate) and resubmitted the same day at 2:25 PM CET. We also replied in the Resolution Center explaining the fix. The build moved to In Review shortly after but has been stuck there for over 29 hours with no status change. We requested an expedited review on March 14. This is our first app submission. We are a small two-person team and the app is ready for launch. Any help moving this forward would be appreciated.

I'm just looking for help/guidance on what if something I did wrong in my build submission? The first test flight build I submitted went through in about 1 day, 2 build updates after that went through and were deployed for my test flight participants each in less than 24 hours. The last build I have submitted has been 6 days now. I have had to submitted multiple builds and cancel a few of them as I keep making progress on my app. I have submitted a ticket for assistance, and called the help number. Thank you in advance for any help. I appreciate the community.

Hello, We are building a new app that would be kinda extension of the other and we want to let our community share the same account in between. We use Apple Sign in and we want Appel sign in system to give the same identity when people use apple relay. One of our app is alreadey released, can we still do it to share the same Apple login?

The man page of copyfile sates the following: COPYFILE_CLONE [..] Note also that there is no support for cloning directories COPYFILE_CLONE_FORCE [...] Note also that there is no support for cloning directories: if a directory is provided as the source, an error will be returned. Now the man page for clonefile: > Cloning directories with these functions is strongly discouraged. Use copyfile(3) to clone directories instead. -- So am I to enumerate the content of a directory build subfolders along the way in the target destination and clone each file inside individually? If I recall NSFileManager seems to clone a large directory instantly (edit actually I remembered wrong NSFileManager does not do this. Finder seems to copy instead of clone as well). On further inspection, clonefile states that it can do this, but it is discouraged. Interesting. I wonder why. If src names a directory, the directory hierarchy is cloned as if each item was cloned individually. However, the use of clonefile(2) to clone