“build disappears”

Context: I am building an iOS productivity app using EAS Build. The project has 4 targets: the main app and 3 extensions (ShieldAction, ShieldConfiguration, ActivityMonitorExtension). The Issue: I have officially received approval from Apple for the Family Controls (Distribution) entitlement for my main Bundle ID. However, the build still fails during the Xcode phase. The Errors: Xcode reports that the generated provisioning profiles do not include the com.apple.developer.family-controls entitlement. For example: Provisioning profile *[expo] com.*.** AdHoc 177247892.... doesn't support the Family Controls capability. All 3 extensions are failing with the exact same error. What I've done: Confirmed approval from Apple for com.*.**. Enabled Family Controls and App Groups on the Apple Developer Portal for all 4 Identifiers. Cleared EAS local and remote cache using eas build --clear-cache. Deleted existing profiles on both Expo.dev and Apple Portal to force regeneration. The Qu

We have a VPN app that uses NEPacketTunnelProvider with includeAllNetworks = true. We've encountered an issue where push notifications are not delivered over Wi-Fi while the tunnel is active in a pre-MFA quarantine state (tunnel is up but traffic is blocked on server side), regardless of whether excludeAPNS is set to true or false. Observed behavior Wi-Fi excludeAPNS = true - Notifications not delivered Wi-Fi excludeAPNS = false - Notifications not delivered Cellular excludeAPNS = true - Notifications delivered Cellular excludeAPNS = false - Notifications not delivered On cellular, the behavior matches our expectations: setting excludeAPNS = true allows APNS traffic to bypass the tunnel and notifications arrive; setting it to false routes APNS through the tunnel and notifications are blocked (as expected for a non-forwarding tunnel). On Wi-Fi, notifications fail to deliver in both cases. Our question Is this expected behavior when includeAllNetworks is enabled on Wi-Fi, or is this a known issue / bug with APN

I’m interested in hearing what currently concerns other indie iOS developers, as 2026 feels both exciting and somewhat fragile to me, with the constant worry that an Apple account issue or unexpected rejection could undo years of hard work overnight. AI has made cloning apps easier than ever and even strong niches can quickly attract well funded competitors, so while I’m optimistic about building, these are the realities I often find myself thinking about.

Full Report {app_name:Exueshi PC Desktop,timestamp:2026-02-28 18:02:50.00 +0800,app_version:1.0.20,slice_uuid:4c4c4476-5555-3144-a1a1-7e047782f52d,build_version:1.0.20,platform:0,bundleID:com.exueshi.pcdesktop,share_with_app_devs:0,is_first_party:0,bug_type:309,os_version:macOS 26.1 (25B78),roots_installed:0,name:Exueshi PC Desktop,incident_id:B1529D77-1AB2-4523-A7D1-288F3CF10E88} { uptime : 33000, procRole : Default, version : 2, userID : 501, deployVersion : 210, modelCode : MacBookPro16,1, coalitionID : 4905, osVersion : { train : macOS 26.1, build : 25B78, releaseType : User }, captureTime : 2026-02-28 18:02:50.5267 +0800, codeSigningMonitor : 0, incident : B1529D77-1AB2-4523-A7D1-288F3CF10E88, pid : 10285, cpuType : X86-64, roots_installed : 0, bug_type : 309, procLaunch : 2026-02-28 18:02:50.4101 +0800, procStartAbsTime : 33974865865372, procExitAbsTime : 33974982166804, procName : Exueshi PC Desktop, procPath : /Users/USER/Documents/*/Exueshi PC Desktop.app/Contents/MacOS/Exueshi PC Desktop, b

My brand new 1.0 app is approved and pending developer release. As part of my release checks, I like to download the app store release using a promo code. On both iOS and macOS, redeeming a promo code for the respective builds gives the error you see in the screenshot: Unable to Redeem. This content is incompatible with the current software on this device. Update your device to the latest software version and try again. The app targets iOS 26.0, and my devices are running iOS 26.3, and it was built with Xcode 26.3. I'm relying on this feature for sending a build to pre-release media for reviews/articles, and am worried I'll embarrass myself. Other developers: Have you also had this issue? Do you know a work around for this issue? Apple: Please help! Is there anything I can do?

Hello everyone! I am trying to wrap a ViewModifier inside a Swift Package that bundles a metal shader file to be used in the modifier. Everything works as expected in the Preview, in the Simulator and on a real device for iOS. It also works in Preview and in the Simulator for tvOS but not on a real AppleTV. I have tried this on a 4th generation Apple TV running tvOS 26.3 using Xcode 26.2.0. Xcode logs the following: The metallib is processed and exists in the bundle. Compiler failed to build request precondition failure: pipeline error: custom_effect-fg2a5cia7fmha4: error: unresolved visible function reference: custom_fn Reason: visible function not loaded Compiler failed to build request precondition failure: pipeline error: custom_effect-fg2a5cia7fmha4: error: unresolved visible function reference: custom_fn Reason: visible function not loaded Compiler failed to build request precondition failure: pipeline error: custom_effect-fg2a5cia7fmha4: error: unresolved visible function ref

100% new here, and probably trying to jump the gun here. I've released my 1st build to TestFlight for some people to test, but till now the app is still under review. Does it always take this long (day 4 now) for a 1st build to be reviewed, or am I missing something here?

Hello, I recently submitted my Swift Student Challenge app playground (“Crest”) and realized after submission that I accidentally selected Swift Playgrounds as the software to run it, instead of Xcode 26 or later. My project builds and runs successfully in Xcode 26 using the iOS 26 SDK and simulator. However, when opening the same .swiftpm project in the Swift Playgrounds app on iPad, it does not compile because Swift Playgrounds currently only supports up to iOS 18 SDK and does not support iOS 26 APIs. The submission itself is complete, builds correctly in Xcode, and was submitted before the deadline. The incorrect selection of Swift Playgrounds was an honest mistake during the submission process. I wanted to ask whether reviewers are able to run the submission using Xcode 26 in cases like this, or if there is anything I should do. Thank you very much for your time.