Search results for

“build disappears”

51,296 results found

Post

Replies

Boosts

Views

Activity

Unable to submit for App Review
Hi. I’m unable submit to a new Version of my App. If i want to Add for Review, i get the Error Message: “Unable to Add for Review The items below are required to start the review process: This build is using a beta version of Xcode and can’t be submitted.” The new Version is Uploaded from the Latest Version of Swift Playground for iPad(4.7). No Betas
1
0
56
6d
Xcode fails to compile Blender-exported USDZ in .rkassets with misleading "permission" error — Xcode 26.3
The error: When building a RealityKitContent package that contains a USDZ file exported from Blender, Xcode throws the following error: error: [xrsimulator] Exception thrown during compile: Cannot get rkassets content for path .../RealityKitContent.rkassets because 'The file RealityKitContent.rkassets couldn't be opened because you don't have permission to view it.' error: Tool exited with code 1 The error message mentions permission — but permissions are not the issue. This appears to be a misleading error from realitytool masking a USD validation failure. What I've ruled out File permissions — all files are -rw-r--r--, user has Read & Write on the folder Extended attributes / quarantine flag — other files with the same @ flag work fine Corrupted archive — unzip -t confirms the USDZ is valid (board.usdc + textures) Stale build cache — deleted DerivedData and com.apple.DeveloperTools cache, no change Key observations The same file builds successfully on my colleague's machine ru
1
0
576
6d
API Rate Limits
We regularly submit builds, manage provisioning profiles, and query build statuses for a large number of applications across multiple store accounts. We rely on automated tooling (Fastlane / App Store Connect API) to manage this pipeline efficiently. Recently, we have been experiencing HTTP 5xx errors when making requests to Apple's APIs (App Store Connect, Spaceship). We believe these failures are caused by rate limiting applied to our outbound IP addresses, as the errors correlate with periods of higher submission activity. We have already taken steps on our side to mitigate the issue - including distributing requests across multiple external IP addresses - but we continue to encounter these errors during peak release periods, which delays application delivery to our clients and their end users.
0
0
29
6d
Migration to Xcode 26: Requirements, Internal Distribution, and Compatibility Concerns
Is it mandatory for all developers to migrate to Xcode 26 starting from April 28, 2026? What happens if a developer submits or distributes a build created using Xcode 16 after April 28, 2026? Will it still be accepted or supported? Our app is distributed only via an internal company portal (not through the App Store). In this case, are we still required to build and distribute the app using Xcode 26 after April 28, 2026? If a hotfix is required before our next planned release (July 2026), how safe is it to use the UIDesignRequiresCompatibility flag as a temporary solution, assuming Xcode 26 becomes mandatory? Are there any risks or limitations associated with this approach? What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration challenges in such a mixed environment? If the UIDesignRequiresCompatibility flag is used as a temporary workaround, what would be the
1
0
49
6d
Network Extension "Signature check failed" after archive with Developer ID — works in Xcode debug
I have a macOS VPN app with a Network Extension (packet tunnel provider) distributed outside the App Store via Developer ID. Everything works perfectly when running from Xcode. After archiving and exporting for Developer ID distribution, the extension launches but immediately gets killed by nesessionmanager. The error: Signature check failed: code failed to satisfy specified code requirement(s) followed by: started with PID 0 status changed to disconnected, last stop reason Plugin failed What makes this interesting: the extension process does launch. AMFI approves it, taskgated-helper validates the provisioning profile and says allowing entitlement(s) due to provisioning profile, the sandbox is applied, PacketTunnelProvider is created — but then Apple's Security framework internally fails the designated requirement check and nesessionmanager kills the session. Key log sequence: taskgated-helper: Checking profile: Developer ID - MacOS WireGuardExtension taskgated-helper: allowing entitlement(s) for com.xx.xx.W
3
0
61
6d
Reply to sysextd: "no policy, cannot allow apps outside /Applications" - NEFilterDataProvider system extension on macOS 26
It sounds like you’re using Developer ID signing for day-to-day development. That’s a mistake on multiple levels. I talk about this in general in The Care and Feeding of Developer ID, but there are extra issues with system extensions, where system policy requires that Developer ID signed sysexen be notarised. So my advice in this case. Use Apple Development code signing for day-to-day development. Use Developer ID for pre-release testing and distribution. There are a couple of key benefits with this approach: It lets you build and debug without enabling development mode, which is a big win IMO. Xcode’s automatic code signing works well with Apple Development signing. Even if you’re not using Xcode, you can create a small test project in Xcode, get it working, and then follow the same path it took. See Debugging a Network Extension Provider for specific advice on how to bring up a provider in Xcode. One thing that Xcode doesn’t handle is the -systemextension suffix )-: To learn more about that, read E
6d
Reply to CKQuerySubscription on public database never triggers APNS push in Production environment
Hi Ziqiao, thanks for looking into this! I've verified using CKFetchSubscriptionsOperation.fetchAllSubscriptionsOperation() on both Development and Production (TestFlight) devices. All 5 subscriptions are present and correctly configured in both environments. The output is identical between both environments. Here are all 5 subscriptions as returned by CKFetchSubscriptionsOperation: fr-sub-v3 (FriendRequest) Predicate: receiverID == [userID] AND status == pending badge=true, sound=default, contentAvail=false locKey=FRIEND_REQUEST_BODY, locArgs=[senderUsername] category=FRIEND_REQUEST, desiredKeys=[senderID, senderUsername] rec-sub-v3 (MediaRecommendation) Predicate: receiverID == [userID] AND status == pending badge=true, sound=default, contentAvail=false locKey=RECOMMENDATION_BODY, locArgs=[senderUsername, mediaTitle] category=RECOMMENDATION, desiredKeys=[mediaTitle, mediaType, senderID, senderUsername] fs-a-sub-v3 (Friendship) Predicate: userAID == [userID] badge=true, sound=default, contentAvail=false locK
6d
Custom Capacitor 6 plugin with SPM: "plugin is not implemented on ios" despite being compiled
Hi everyone, I'm building an iOS app using Capacitor 6 with Swift Package Manager (SPM). I have a custom native plugin (AppleIAPPlugin) for StoreKit 2 In-App Purchases that lives in the App target (not as an SPM package). Despite compiling successfully, the JavaScript bridge throws: AppleIAP plugin is not implemented on ios Setup AppleIAPPlugin.swift: swift import Foundation import Capacitor import StoreKit @objc(AppleIAPPlugin) public class AppleIAPPlugin: CAPPlugin, CAPBridgedPlugin { public let identifier = AppleIAPPlugin public let jsName = AppleIAP public let pluginMethods: [CAPPluginMethod] = [ CAPPluginMethod(name: getProducts, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: purchase, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: restorePurchases, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: getCurrentEntitlements, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: openManageSubscriptions, returnType: CAPPluginReturnPromise), ] @objc func getProduc
1
0
32
6d
Xcode 26.4 cannot run app-hosted unit tests on physical iOS 16 devices ("Logic Testing Unavailable")
Summary: After upgrading to Xcode 26.4, app-hosted XCTest execution on physical devices running iOS 16 fails at test-planning time with Logic Testing Unavailable. The same project and same device work under Xcode 26.2. The failure reproduces with a standalone minimal Xcode project, which suggests this is an Xcode regression rather than a project-configuration issue. Environment: Xcode: 26.4 (17E192) macOS: Tahoe 26.4 Failing device: iPhone 11 (iPhone12,1), iOS 16.0.3 Working comparisons: Xcode 26.2 + same iPhone 11 (iOS 16.0.3): works Xcode 26.4 + iPad Pro 11-inch (4th generation) on iOS 26.3: works Regression: Yes. Works on Xcode 26.2. Fails on Xcode 26.4. Same project, same signing setup, same physical iOS 16 device. Minimal reproduction: A minimal sample project with: one iOS app target one app-hosted unit-test target one UI-test target (for comparison; not required to reproduce) Steps for the unit-test repro on a physical device running iOS 16: Build for testing: xcodebuild -project TestProject.x
1
0
250
6d
Native Wind Animation Layer for Apple Maps / MapKit
Hey Apple team, I'd love to see a native wind animation layer added to Apple Maps and MapKit. A built-in, system-level wind visualization — similar to the animated weather layers seen in third-party apps — would be an incredibly powerful tool for developers building weather, aviation, marine, outdoor recreation, and navigation apps. Having this baked natively into MapKit would mean smoother performance, better battery efficiency, and a consistent experience across iOS, iPadOS, and macOS — rather than every developer having to reinvent the wheel with custom particle systems or third-party SDKs. Please Apple — this would be a fantastic addition to the Maps ecosystem. 🌬️🗺️
1
0
45
6d
Reply to Why don't my os_log entries show up until the second time my driver loads?
Why is this and To be perfectly honest, I have no idea. There's a thread about logging in DriverKit logging here that might be worth reviewing, but that's primarily about issues with IOLog redaction, which is different than you're describing. I can't think of any reason why we'd redact the first run but not later runs. I suspect there is some kind of bug involved, but I'm going to run this by Quinn to see what he thinks. Bonus Thought: How are you signing your DEXT? Are you using automatic signing with the Development Only profiles (modern/good) or disabling SIP (old/bad)? This a blind guess, but it's possible the old (SIP disabled) approach might cause something weird like this, depending on exactly how the build was signed. See this post for more information on how to sign DEXT. However, I do have two ideas for this: more importantly, how can I fix it? The post above mentions this in passing, but Quinn's Recording Private Data in the System Log post describes how you can manually control how redact
Topic: App & System Services SubTopic: Drivers Tags:
1w
Reply to 3.2(f) triggered — account pending termination despite repeated attempts to comply
Thanks for the response, for context it was around 15 submissions over a few months and 30ish messages. I get your example, but I think my situation’s a bit different. The updates weren’t just micro changes trying to slip something through, there was a mix of both small tweaks and broader changes. The issue was the feedback stayed very generic (“overtly sexual”) without pointing to specific elements, so each update was essentially a best guess at what might be triggering it. Especially early on, when only metadata was flagged, I assumed the issue was relatively minor. By the end, I actually went in the opposite direction of evasion & submitted a build with everything unlocked and included screenshots showing all content upfront, so review had full visibility, as requested during a phone call. It’s possible I missed a couple of screenshots in earlier messages, but nothing was intentional. That’s why the 3.2(f) decision caught me off guard, there was no intent to hide or mislead, just trying to int
1w
90919: Invalid entitlement error in ASC
I have an existing app in App Store Connect. I added the SharedWithYou functionality to the app code and tested it on several devices. Everything is working as expected. One of the first steps was to add the com.apple.developer.shared-with-you entitlement to the Entitlements.plist file. This required a round of updates for app identifiers and provisioning profiles. When I upload the production build for testing in TestFlight I receive the following error: 90919: Invalid entitlement. The “” bundle has the com.apple.developer.shared-with-you entitlement, but it doesn’t use the Shared with You framework. Please remove the entitlement and upload a new build. I'm using SWHighlight, SWHighlightCenter, and SWAttributionView in several places throughout my app... I filed an issue in the Feedback Assistant but so far, have not received any response.
1
0
354
1w
xcodebuild fails if build tool plugins are installed
After having built the SwiftUI project numerous times from Xcode and allowing the plugins after the first build post install using xcodebuild -scheme build fails with: The following build commands failed: Validate plug-in “SwiftLintBuildToolPlugin” in package “swiftlintplugins” Validate plug-in “OpenAPIGenerator” in package “swift-openapi-generator” How are we supposed to grant the plugins permission to run in the CLI? Everything I'm getting from Gemini is for packages, not apps.
0
0
22
1w
Unable to submit for App Review
Hi. I’m unable submit to a new Version of my App. If i want to Add for Review, i get the Error Message: “Unable to Add for Review The items below are required to start the review process: This build is using a beta version of Xcode and can’t be submitted.” The new Version is Uploaded from the Latest Version of Swift Playground for iPad(4.7). No Betas
Replies
1
Boosts
0
Views
56
Activity
6d
Xcode fails to compile Blender-exported USDZ in .rkassets with misleading "permission" error — Xcode 26.3
The error: When building a RealityKitContent package that contains a USDZ file exported from Blender, Xcode throws the following error: error: [xrsimulator] Exception thrown during compile: Cannot get rkassets content for path .../RealityKitContent.rkassets because 'The file RealityKitContent.rkassets couldn't be opened because you don't have permission to view it.' error: Tool exited with code 1 The error message mentions permission — but permissions are not the issue. This appears to be a misleading error from realitytool masking a USD validation failure. What I've ruled out File permissions — all files are -rw-r--r--, user has Read & Write on the folder Extended attributes / quarantine flag — other files with the same @ flag work fine Corrupted archive — unzip -t confirms the USDZ is valid (board.usdc + textures) Stale build cache — deleted DerivedData and com.apple.DeveloperTools cache, no change Key observations The same file builds successfully on my colleague's machine ru
Replies
1
Boosts
0
Views
576
Activity
6d
API Rate Limits
We regularly submit builds, manage provisioning profiles, and query build statuses for a large number of applications across multiple store accounts. We rely on automated tooling (Fastlane / App Store Connect API) to manage this pipeline efficiently. Recently, we have been experiencing HTTP 5xx errors when making requests to Apple's APIs (App Store Connect, Spaceship). We believe these failures are caused by rate limiting applied to our outbound IP addresses, as the errors correlate with periods of higher submission activity. We have already taken steps on our side to mitigate the issue - including distributing requests across multiple external IP addresses - but we continue to encounter these errors during peak release periods, which delays application delivery to our clients and their end users.
Replies
0
Boosts
0
Views
29
Activity
6d
Migration to Xcode 26: Requirements, Internal Distribution, and Compatibility Concerns
Is it mandatory for all developers to migrate to Xcode 26 starting from April 28, 2026? What happens if a developer submits or distributes a build created using Xcode 16 after April 28, 2026? Will it still be accepted or supported? Our app is distributed only via an internal company portal (not through the App Store). In this case, are we still required to build and distribute the app using Xcode 26 after April 28, 2026? If a hotfix is required before our next planned release (July 2026), how safe is it to use the UIDesignRequiresCompatibility flag as a temporary solution, assuming Xcode 26 becomes mandatory? Are there any risks or limitations associated with this approach? What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration challenges in such a mixed environment? If the UIDesignRequiresCompatibility flag is used as a temporary workaround, what would be the
Replies
1
Boosts
0
Views
49
Activity
6d
Network Extension "Signature check failed" after archive with Developer ID — works in Xcode debug
I have a macOS VPN app with a Network Extension (packet tunnel provider) distributed outside the App Store via Developer ID. Everything works perfectly when running from Xcode. After archiving and exporting for Developer ID distribution, the extension launches but immediately gets killed by nesessionmanager. The error: Signature check failed: code failed to satisfy specified code requirement(s) followed by: started with PID 0 status changed to disconnected, last stop reason Plugin failed What makes this interesting: the extension process does launch. AMFI approves it, taskgated-helper validates the provisioning profile and says allowing entitlement(s) due to provisioning profile, the sandbox is applied, PacketTunnelProvider is created — but then Apple's Security framework internally fails the designated requirement check and nesessionmanager kills the session. Key log sequence: taskgated-helper: Checking profile: Developer ID - MacOS WireGuardExtension taskgated-helper: allowing entitlement(s) for com.xx.xx.W
Replies
3
Boosts
0
Views
61
Activity
6d
Reply to sysextd: "no policy, cannot allow apps outside /Applications" - NEFilterDataProvider system extension on macOS 26
It sounds like you’re using Developer ID signing for day-to-day development. That’s a mistake on multiple levels. I talk about this in general in The Care and Feeding of Developer ID, but there are extra issues with system extensions, where system policy requires that Developer ID signed sysexen be notarised. So my advice in this case. Use Apple Development code signing for day-to-day development. Use Developer ID for pre-release testing and distribution. There are a couple of key benefits with this approach: It lets you build and debug without enabling development mode, which is a big win IMO. Xcode’s automatic code signing works well with Apple Development signing. Even if you’re not using Xcode, you can create a small test project in Xcode, get it working, and then follow the same path it took. See Debugging a Network Extension Provider for specific advice on how to bring up a provider in Xcode. One thing that Xcode doesn’t handle is the -systemextension suffix )-: To learn more about that, read E
Replies
Boosts
Views
Activity
6d
Reply to iPhone 17 Pro on iOS 26.3 stays unavailable in xcrun devicectl list devices even with Xcode 26.4 beta 2
Have you solved it ? I am facing same issue with IPhone 14 (26.04) and Xcode (26.4). CoreDevice / devicectl layer the device remains unavailable, and Xcode cannot use it for on-device build/run.
Replies
Boosts
Views
Activity
6d
Reply to CKQuerySubscription on public database never triggers APNS push in Production environment
Hi Ziqiao, thanks for looking into this! I've verified using CKFetchSubscriptionsOperation.fetchAllSubscriptionsOperation() on both Development and Production (TestFlight) devices. All 5 subscriptions are present and correctly configured in both environments. The output is identical between both environments. Here are all 5 subscriptions as returned by CKFetchSubscriptionsOperation: fr-sub-v3 (FriendRequest) Predicate: receiverID == [userID] AND status == pending badge=true, sound=default, contentAvail=false locKey=FRIEND_REQUEST_BODY, locArgs=[senderUsername] category=FRIEND_REQUEST, desiredKeys=[senderID, senderUsername] rec-sub-v3 (MediaRecommendation) Predicate: receiverID == [userID] AND status == pending badge=true, sound=default, contentAvail=false locKey=RECOMMENDATION_BODY, locArgs=[senderUsername, mediaTitle] category=RECOMMENDATION, desiredKeys=[mediaTitle, mediaType, senderID, senderUsername] fs-a-sub-v3 (Friendship) Predicate: userAID == [userID] badge=true, sound=default, contentAvail=false locK
Replies
Boosts
Views
Activity
6d
Custom Capacitor 6 plugin with SPM: "plugin is not implemented on ios" despite being compiled
Hi everyone, I'm building an iOS app using Capacitor 6 with Swift Package Manager (SPM). I have a custom native plugin (AppleIAPPlugin) for StoreKit 2 In-App Purchases that lives in the App target (not as an SPM package). Despite compiling successfully, the JavaScript bridge throws: AppleIAP plugin is not implemented on ios Setup AppleIAPPlugin.swift: swift import Foundation import Capacitor import StoreKit @objc(AppleIAPPlugin) public class AppleIAPPlugin: CAPPlugin, CAPBridgedPlugin { public let identifier = AppleIAPPlugin public let jsName = AppleIAP public let pluginMethods: [CAPPluginMethod] = [ CAPPluginMethod(name: getProducts, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: purchase, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: restorePurchases, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: getCurrentEntitlements, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: openManageSubscriptions, returnType: CAPPluginReturnPromise), ] @objc func getProduc
Replies
1
Boosts
0
Views
32
Activity
6d
Xcode 26.4 cannot run app-hosted unit tests on physical iOS 16 devices ("Logic Testing Unavailable")
Summary: After upgrading to Xcode 26.4, app-hosted XCTest execution on physical devices running iOS 16 fails at test-planning time with Logic Testing Unavailable. The same project and same device work under Xcode 26.2. The failure reproduces with a standalone minimal Xcode project, which suggests this is an Xcode regression rather than a project-configuration issue. Environment: Xcode: 26.4 (17E192) macOS: Tahoe 26.4 Failing device: iPhone 11 (iPhone12,1), iOS 16.0.3 Working comparisons: Xcode 26.2 + same iPhone 11 (iOS 16.0.3): works Xcode 26.4 + iPad Pro 11-inch (4th generation) on iOS 26.3: works Regression: Yes. Works on Xcode 26.2. Fails on Xcode 26.4. Same project, same signing setup, same physical iOS 16 device. Minimal reproduction: A minimal sample project with: one iOS app target one app-hosted unit-test target one UI-test target (for comparison; not required to reproduce) Steps for the unit-test repro on a physical device running iOS 16: Build for testing: xcodebuild -project TestProject.x
Replies
1
Boosts
0
Views
250
Activity
6d
Native Wind Animation Layer for Apple Maps / MapKit
Hey Apple team, I'd love to see a native wind animation layer added to Apple Maps and MapKit. A built-in, system-level wind visualization — similar to the animated weather layers seen in third-party apps — would be an incredibly powerful tool for developers building weather, aviation, marine, outdoor recreation, and navigation apps. Having this baked natively into MapKit would mean smoother performance, better battery efficiency, and a consistent experience across iOS, iPadOS, and macOS — rather than every developer having to reinvent the wheel with custom particle systems or third-party SDKs. Please Apple — this would be a fantastic addition to the Maps ecosystem. 🌬️🗺️
Replies
1
Boosts
0
Views
45
Activity
6d
Reply to Why don't my os_log entries show up until the second time my driver loads?
Why is this and To be perfectly honest, I have no idea. There's a thread about logging in DriverKit logging here that might be worth reviewing, but that's primarily about issues with IOLog redaction, which is different than you're describing. I can't think of any reason why we'd redact the first run but not later runs. I suspect there is some kind of bug involved, but I'm going to run this by Quinn to see what he thinks. Bonus Thought: How are you signing your DEXT? Are you using automatic signing with the Development Only profiles (modern/good) or disabling SIP (old/bad)? This a blind guess, but it's possible the old (SIP disabled) approach might cause something weird like this, depending on exactly how the build was signed. See this post for more information on how to sign DEXT. However, I do have two ideas for this: more importantly, how can I fix it? The post above mentions this in passing, but Quinn's Recording Private Data in the System Log post describes how you can manually control how redact
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
1w
Reply to 3.2(f) triggered — account pending termination despite repeated attempts to comply
Thanks for the response, for context it was around 15 submissions over a few months and 30ish messages. I get your example, but I think my situation’s a bit different. The updates weren’t just micro changes trying to slip something through, there was a mix of both small tweaks and broader changes. The issue was the feedback stayed very generic (“overtly sexual”) without pointing to specific elements, so each update was essentially a best guess at what might be triggering it. Especially early on, when only metadata was flagged, I assumed the issue was relatively minor. By the end, I actually went in the opposite direction of evasion & submitted a build with everything unlocked and included screenshots showing all content upfront, so review had full visibility, as requested during a phone call. It’s possible I missed a couple of screenshots in earlier messages, but nothing was intentional. That’s why the 3.2(f) decision caught me off guard, there was no intent to hide or mislead, just trying to int
Replies
Boosts
Views
Activity
1w
90919: Invalid entitlement error in ASC
I have an existing app in App Store Connect. I added the SharedWithYou functionality to the app code and tested it on several devices. Everything is working as expected. One of the first steps was to add the com.apple.developer.shared-with-you entitlement to the Entitlements.plist file. This required a round of updates for app identifiers and provisioning profiles. When I upload the production build for testing in TestFlight I receive the following error: 90919: Invalid entitlement. The “” bundle has the com.apple.developer.shared-with-you entitlement, but it doesn’t use the Shared with You framework. Please remove the entitlement and upload a new build. I'm using SWHighlight, SWHighlightCenter, and SWAttributionView in several places throughout my app... I filed an issue in the Feedback Assistant but so far, have not received any response.
Replies
1
Boosts
0
Views
354
Activity
1w
xcodebuild fails if build tool plugins are installed
After having built the SwiftUI project numerous times from Xcode and allowing the plugins after the first build post install using xcodebuild -scheme build fails with: The following build commands failed: Validate plug-in “SwiftLintBuildToolPlugin” in package “swiftlintplugins” Validate plug-in “OpenAPIGenerator” in package “swift-openapi-generator” How are we supposed to grant the plugins permission to run in the CLI? Everything I'm getting from Gemini is for packages, not apps.
Replies
0
Boosts
0
Views
22
Activity
1w