“build disappears”

My team is evaluating an iOS companion app for our own network-connected device, and we want to understand whether the planned architecture would likely create an App Review problem under Guideline 2.5.17. Our situation is: We are building our own device and our own companion app. We do not intend to market the device as a Matter-certified device initially. We do not intend to support Apple Home or broad third-party Matter ecosystem interoperability in the first release. We are under a tight schedule and are considering reusing Matter/CSA-derived libraries, data models, and protocol concepts internally to reduce engineering effort and move faster toward eventual certification. Our current understanding is that there are already many iOS apps that communicate with LAN-connected devices using proprietary protocols, so our initial assumption is that a vendor-specific local-network device workflow should generally be acceptable. The point we are trying to clarify is whether that changes if the implementa

Hello everyone, I’m submitting an iOS app to App Review and received Guideline 2.1(b) – Information Needed. Apple says it appears the app may access or include paid digital content/subscriptions and they want details about the business model. In my project, a paywall / premium UI exists in the codebase, and subscription products are configured in App Store Connect for a future release, but in the build currently submitted: The paywall is disabled (not reachable through any UI flow / feature flags are off). There is no purchase flow (no way to subscribe in-app). There is no external purchase (no website/Stripe/etc.). Users cannot access any previously purchased subscriptions (no entitlement access / restore not exposed). Questions: Can the mere presence of a paywall screen / IAP-related code in the binary (even if disabled/unreachable) block App Review or trigger repeated 2.1(b) requests? Is it recommended to remove paywall/IAP code entirely from the review build if it’s not used yet, or is a

Hello everyone, I recently submitted my iOS app for review, but it was unfortunately rejected under Guideline 2.1(a) - Performance - App Completeness. For context, my app is a healthcare application built with Ionic. According to the App Review team's message, they found the app to be incomplete. They stated they were unable to review the app because they couldn't get past the login screen. The Root Cause: Upon investigating, we discovered the issue is related to IP Geo-blocking. Because the app handles sensitive healthcare data, our API provider strictly blocks all network traffic originating from outside of Italy to legally comply with European GDPR regulations. Since the App Review team tests from the US, their requests are being entirely blocked by the firewall, causing the login to fail and the app to look broken on their end. What I have verified so far: I have provided valid demo account credentials in the App Store Connect App Review Information section. I have tested the app thoroughly on physical de

Hello, I'm unable to kick off builds in Xcode Cloud today due to an error connecting to our SCM repo. Repository Issue Xcode Cloud is unable to connect to the repository “”. Reconnect the repository to resume builds. I can see that this is due to an HTTP 500 error on the /scm-repositories endpoint, which would normally indicate an issue in Xcode Cloud. If on the contrary this indicates an issue on my side, I'd like to hear details and what the resolution might be. Filed an issue here: FB22314855 (Xcode Cloud: HTTP 500 when connecting to SCM provider)

I'm building a hybrid iOS app using Capacitor with a native Swift IAP bridge (StoreKit 1). My SKProductsRequest consistently returns 0 products, and all product identifiers appear in response.invalidProductIdentifiers. Setup: Capacitor app with custom CAPBridgeViewController subclass handling IAP via SKPaymentQueue and WKScriptMessageHandler 5 products configured in App Store Connect (3 consumables, 2 auto-renewable subscriptions), all Ready to Submit Bundle ID matches between Xcode and App Store Connect In-App Purchase capability enabled Paid Apps agreement active Testing on physical iPad Air M3 with Sandbox Tester Products created over 48 hours ago Clean Build Folder performed before each test Product IDs: com.opencompass.basic.monthly com.opencompass.premium.monthly com.opencompass.tokens.50 com.opencompass.tokens.150 com.opencompass.tokens.500 Code snippet: let request = SKProductsRequest(productIdentifiers: Set(productIdentifiers)) request.delegate = self request.start() // Delegate fir

Hi Apple Developer Support, We are reaching out to request guidance on a testing constraint we have encountered related to iOS Universal Links and Associated Domains entitlements. As part of aligning with updated recommendations from our authentication provider, we have transitioned our mobile apps to use HTTPS redirect callbacks (Universal Links) instead of custom URI schemes. This works as expected in production and on real physical devices. However, we are encountering a significant issue in our cloud-based device testing environment. When our testing platform re-signs the app to run it on their infrastructure, the re-signing process strips the Associated Domains entitlement from the app bundle. As a result, iOS no longer honors our Universal Links, which breaks the authentication redirect flow — the callback cannot route back into the app after the user authenticates. We have identified a potential workaround that would involve disabling app re-signing in the testing platform, but this requires provisioni