build disappears

We submitted a build on the 26th, but it stayed in “Waiting for Review” until January 3rd. Thinking something was wrong, we withdrew it and resubmitted, but after 5 days it’s still pending. We have an important campaign in January and this delay is seriously affecting us. We also emailed support but haven’t received any reply. How can we resolve this?

I have two Macs, desktop and laptop. Since they both belong to me, they both sign in with the same Apple account. I find that if I sign and notarize an app on one, the other must be powered off. Otherwise, notarization will fail. Is this intentional? If so, what is the rationale? Is there a way to fix or avoid it? Both systems run macOS Tahoe with the latest updates. Both are set up the same way for signing using the same certificates. The build process is identical on each.

I am developing a binary SDK for consumption by others. When we updated to Xcode 26, any builds which are generated cannot be consumed by Xcode 16. The specifics lie in the optionals. The following Swift code generate a .swiftmodule func affectedApi() -> Int? { return 1 } In Xcode 16 it generated the following .swiftmodule in the framework. public func affectedIntApi() -> Swift.Int? In Xcode 26 it adds an if statement. #if compiler(>=5.3) && $NonescapableTypes public func affectedIntApi() -> Swift.Int? #endif That if statement prevents Xcode16 from seeing the API, and it causes compile failures. This happens regardless of which Swift version is used, and it only affects functions which use Optionals. Is there a way to prevent the compiler from wrapping the API in that statement?

Hello all! My name is Luke, and I'm a 14 year old with a idea for SSC. This is my first SSC submission ever. I would like some feedback concerning a question. My app is an AI powered academic planner that helps you and your life. I won't give too much away, but I believe it's a really helpful concept. It uses a mini on-device LLM (built with simple if this word typed then do this logic) to help organize assignments. This is a real business I am building, and I put inside of my app simulated features such as the app saying scanning your Google Classroom.., would this go against any terms and make the app less likely to win? I also have my app fully polished, and feels like an actual app and finished product, with demo assignments pre-loaded, and most stuff is placeholders. Should the app be more like a guided simulator? Such as click here to see how this will be simulated in a final release or again should it be polished? I just want some feedback, since I only have 3 minutes, and the app needs to be

Hello all! My name is Luke, and I'm a 14 year old with a idea for SSC. This is my first SSC submission ever. I would like some feedback concerning a question. My app is an AI powered academic planner that helps you and your life. It uses a mini on-device LLM to help organize assignments. This is a real business I am building, and I put inside of my app simulated features such as the app saying scanning your Google Classroom.., would this go against any terms and make the app less likely to win? I also have my app fully polished, and feels like an actual app and finished product, with demo assignments pre-loaded, and most stuff is placeholders. Should the app be more like a guided simulator? Such as click here to see how this will be simulated in a final release or again should it be polished? I just want some feedback, since I only have 3 minutes, and the app needs to be offline, I just want to improvise. You can check out the basis of my app at my website. https://whiteb0x.me Hopefully I can get som

Does DL-TDoA ranging in the Nearby Interaction framework support building a traditional RTLS-style TDoA localization system, where a device’s absolute position is computed from time-difference measurements across multiple deployed anchors, or is DL-TDoA strictly limited to system-managed, relative ranging and direction estimation (distance/direction) between nearby devices? If DL-TDoA ranging in Nearby Interaction is not intended to support traditional RTLS-style TDoA localization, is there any public documentation or reference material that describes the intended DL-TDoA architecture, such as the expected system setup, device roles, and deployment constraints (for example, how ranging is expected to be performed between an iPhone and nearby accessories), beyond the high-level API documentation? Regards.

Hello Dear Network, We are developing a banking application and are implementing Apple Wallet In-App Provisioning with Wallet UI and Non-UI extensions. Our App Store submission fails with the error: Missing entitlement com.apple.developer.payment-pass-provisioning for both Wallet UI and Non-UI extensions. In the Apple Developer portal, we do not see the Apple Pay or In-App Provisioning capabilities available for our App ID or extension App IDs. We would like to request enablement of: Apple Pay Payment Pass Provisioning In-App Provisioning for our Apple Developer Team and related App IDs. Please let us know what we need to do for can upload build with that Entitlements, what can be problem? Thank you.

Hello, we have a product package which is structured like this: / Installer.pkg / Distribution / Main Component.pkg / Scripts / preinstall / postinstall / helper [ Mach-O executable ] / Payload / Application Bundle.app / Another Component.pkg ... The helper is our custom CLI helper tool which we build and sign and plan to use it in pre/post install scripts. I'd like to ask if we need to independently notarize and staple the helper executable or just the top level pkg notarization is sufficient in this case? We already independently notarize and staple the Application Bundle.app so it has ticket attached. But that's because of customers who often rip-open the package and pick only the bundle. We don't plan to have helper executable used outside of installation process. Thank you, o/

File Provider Extension Testing Mode -2014 Error Issue I'm developing a macOS File Provider Extension and encountering a -2014 (Extension not registered) error when using Testing Mode only. Environment macOS: 13.0+ Xcode: Latest version Developer Account: Paid Developer Account Extension Type: NSFileProviderReplicatedExtension Current Status App ID Configuration App ID: kr.it.flux.FluxDrive2.FileProvider Capabilities: ✅ com.apple.developer.fileprovider.testing-mode (enabled) ❌ General com.apple.developer.fileprovider (not visible) Extension Configuration NSExtensionPointIdentifier: com.apple.fileprovider NSExtensionPrincipalClass: FluxDrive2FileProvider.FileProviderExtension Code Signing: Valid (Team Identifier verified) Info.plist: Valid Error Message Error Domain=NSFileProviderErrorDomain Code=-2014 The operation couldn't be completed. (NSFileProviderErrorDomain error -2014.) Underlying error: Error Domain=NSFileProviderErrorDomain Code=-2001 Extension cannot be used Attempted Solutions ✅ Verified and corre