Search results for

“sandbox”

10,542 results found

Post

Replies

Boosts

Views

Activity

StoreKit 2 Product.displayPrice returns USD while purchase dialog shows EUR
Hi, I'm testing my first auto-renewable subscription using StoreKit 2 and TestFlight. When loading products via: let products = try await Product.products(for: ids) the product is returned successfully, but product.displayPrice shows: $4.99 even though: My App Store account is located in Germany. The app is only intended for the German market. The native Apple purchase sheet displays the correct price in EUR. The subscription pricing is configured correctly in App Store Connect. The subscription is still in Ready to Submit / Prepare for Submission state and has not yet been approved. Example: print(product.displayPrice) returns: $4.99 while the StoreKit purchase dialog shows: 5,99 € Has anyone seen this behavior before? Is this expected for new subscriptions in TestFlight/Sandbox before the first App Review approval, or could there be another reason why displayPrice differs from the actual purchase dialog? Thanks!
1
0
756
May ’26
APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
I’m trying to diagnose an APNs provider authentication issue that began after APNs had previously been working. Summary: My iOS app can register for remote notifications and successfully sends its device token to my server. The app has the Push Notifications capability enabled in Xcode, the Bundle ID has Push Notifications enabled in Certificates, Identifiers & Profiles, and the APNs key is active in the Apple Developer portal. However, every server-side APNs send attempt now fails with: HTTP 403 {reason:InvalidProviderToken} This happens against both sandbox and production APNs endpoints. App / account details: Bundle ID / apns-topic: app.terrasignal Team ID: 837F2XGDX Current APNs Key ID: HNW7XPK2H3 APNs key type: Apple Push Notifications service (APNs) Key configuration: Team scoped, Sandbox & Production Xcode signing team: David Buck / Team ID 837F2XGDX Push Notifications capability is enabled in Xcode Device token environment tested: sandbox Server clock verified agains
7
0
892
May ’26
StoreKit 2 currentEntitlements persists after Sandbox Purchase History reset in TestFlight
I am testing a StoreKit 2 non-consumable IAP through TestFlight. Product ID: com.metabolla.plus.lifetime Type: Non-Consumable Environment: TestFlight / Sandbox Transaction.currentEntitlements keeps returning an active entitlement for this product even after: configuring a Sandbox Apple Account clearing Sandbox Purchase History reinstalling the app rebooting the device Important detail: the first TestFlight purchase was completed before configuring the Sandbox Apple Account on the device. If I temporarily change the Product ID in code, the entitlement disappears, so the issue seems tied to the original Product ID/account/receipt. Question: Can a non-consumable TestFlight purchase made before Sandbox Apple Account configuration remain associated with the original TestFlight/Apple ID identity? Is there any supported way to clear this entitlement for testing?
5
0
1.4k
May ’26
Reply to Mac Catalyst App No longer start : Cause bugs in App Store and weird macOS behaviour
I deleted all the files that contains the name of my app from the terminal using the find command. Sometimes it does start and crash and I can get a crash dump. Other times it does nothing. But I will check from the terminal to see if I can get more infos. It will take a while to test again since I don't have access to the user computer. macOS should have a way to uninstall an app for real, not leave hidden things all over the place. Apple decided to force us to use their store, then it is their responsibility to install them properly and clean them properly. macCatalyst app are sandboxed, I cannot to that myself. Thanks for the help.
Topic: App & System Services SubTopic: General Tags:
May ’26
Reply to Mac Catalyst App No longer start : Cause bugs in App Store and weird macOS behaviour
[quote='828110021, ShaddamIV, /thread/828110, /profile/ShaddamIV'] When we uninstall and reinstall an app, it should work as it did [/quote] I understand your position here, but that’s never been true on the Mac [1]. When you delete an app on macOS, the system doesn’t delete the app’s container [2]. That’s because the app container might contain vital user data, and there’s no way for macOS to know if the user has another copy of the app elsewhere on their system, or perhaps on an external hard drive that’s not connected right now. Given that reality, there are a couple of things you can do here. The first is to ask one of your affected users to remove the app and then delete the app’s container. You’ll find that in ~/Library/Containers. My advice is that you work through the process yourself, so that you can figured out the exact instructions, and then send those instructions to one of your affected users, just to see if this helps. IMPORTANT The user-visible name of your app’s container is likely different
Topic: App & System Services SubTopic: General Tags:
May ’26
DeclaredAgeRange API not triggering in regulated regions (Brazil, Utah) — Is it functioning in production?
Hi, We've implemented age assurance logic in our app using the DeclaredAgeRange framework to comply with regulations in Brazil (Digital ECA, effective March 17, 2026) and Utah (App Store Accountability Act, effective May 6, 2026). Our implementation calls AgeRangeService.shared.isEligibleForAgeFeatures on app launch to determine whether the current user is subject to age assurance requirements, and proceeds to call requestAgeRange(ageGates:) accordingly. However, after monitoring in production since the Brazil enforcement date, we've consistently observed isEligibleForAgeFeatures returning false for users in regulated regions, with no age range data being returned. What we'd like to clarify: Is isEligibleForAgeFeatures currently returning true for users in Brazil in production (not sandbox)? For Utah — given that HB 498 pushed the developer compliance deadline to May 6, 2027, will isEligibleForAgeFeatures reflect the original May 6, 2026 activation date or the revised 2027 date? Is there a known roll
2
0
1.5k
May ’26
Reply to OpenZFS on FSKit — Proof of Concept
Technical Findings — Things That Weren't Obvious These cost significant debugging time and aren't documented anywhere: startCheckWithTask: must complete asynchronously Calling [task didCompleteWithError:nil] synchronously inside startCheckWithTask: causes fskitd to receive task completed before task started over XPC. fskitd rejects this with FSKitErrorDomain Code=27503 Task didn't start yet and never spawns the activate instance. The fix is to dispatch the completion with even a 1ms delay so FSKit can send the started notification first. app-sandbox=true is required in entitlements ExtensionKit rejects the extension entirely without com.apple.security.app-sandbox=true, even though sandboxing a filesystem extension feels counterintuitive. This needs to be paired with com.apple.developer.fskit.fsmodule=true. Container identifier must equal volume identifier for FSUnaryFileSystem FSContainer.h documents this but it's easy to miss: for unary file systems, the container identifier passed
Topic: App & System Services SubTopic: Core OS Tags:
May ’26
OpenZFS on FSKit — Proof of Concept
Installing ZFSFSKit.appex ? /Library/ExtensionKit/Extensions/ Substituting real Mach-O (libtool wrapper ? .libs/ZFSFSKit) Installing zfs.fs ? /Library/Filesystems/ mount_zfs: Mach-O 64-bit executable arm64 Done. Signing (before pluginkit, so it sees a valid signature)... Re-signing /Library/ExtensionKit/Extensions/ZFSFSKit.appex ad-hoc (no identity). Note: requires amfi_get_out_of_my_way=1 in boot-args. Team ID: ADHOC /Library/ExtensionKit/Extensions/ZFSFSKit.appex: replacing existing signature Done. Signature: Identifier=org.openzfsonosx.filesystems.zfs.fsext Signature=adhoc TeamIdentifier=not set Entitlements: com.apple.application-identifierADHOC.org.openzfsonosx.filesystems.zfs.fsextcom.apple.developer.fskit.fsmodulecom.apple.developer.team-identifierADHOCcom.apple.security.app-sandbox Registering with pluginkit... pluginkit -a done. Restarting fskitd... # sudo pluginkit -v -m -p com.apple.fskit.fsmodule + org.openzfsonosx.filesystems.zfs.fsext((null)) 6A12A41280FB-4190-B957-FA94DC89BB1E 2026-05-
6
0
626
May ’26
Cannot attach In-App Purchase to first macOS app version — "In-App Purchases and Subscriptions" section missing on version page
I'm trying to submit a first-time In-App Purchase together with a new version of my macOS app, but App Store Connect doesn't seem to provide a way to do this. Setup: macOS app (Bundle ID: de.andreasmaser.Screenshots) Marketing version: 1.2, Build 1 (uploaded, processed, attached to version) IAP Screenshots Pro (Product ID: de.andreasmaser.Screenshots.pro) is fully configured: status Waiting for Review, App Review screenshot present, both English + German localizations, pricing set Previous 1.1 submission was rejected under Guideline 2.1(b) because the associated In-App Purchase products have not been submitted for review Per Apple's documentation (https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase), step 3 says: On the right, scroll down to the In-App Purchases and Subscriptions section. The problem: This section does not exist on the macOS app version page. I scrolled through the entire page; the sections are: App Previews & Screenshots → Promoti
0
0
221
May ’26
Reply to Can't verify my identity for sandbox can not receive verification code
Hello - I'm not fully understanding how you are reaching each of the steps described. In App Store Connect, you should be able to create up to 10,000 Sandbox users as documented here. When creating new Sandbox users, you are not required to provide a telephone number. Sandbox user accounts created in App Store Connect can then be used to sign in to devices that are running a development-signed version of your app, and test in-app purchases without incurring any charges. Note the requirement to Enable Developer Mode on your device(s) before testing with Sandbox users. More information about testing in-app purchases in Sandbox is available here, and troubleshooting tips specific to Sandbox testing can be found here. If you continue to have problems with Sandbox user accounts and testing, please file a Feedback Assistant ticket that provides as much detail as possible - including screenshots, steps to reproduce, etc. - and reply back to this thread w
May ’26
Tap To Pay TestFlight
I'm trying to distribute our app through TestFlight's internal testing for our QA Analysts to run some tests in the non-production environment. In this page: https://developer.apple.com/documentation/storekit/testing-in-app-purchases-with-sandbox Is stated that: Apps that you download from TestFlight always run in the sandbox environment. But we ran into the issue from the ProximityReaderAPI requesting a Sandbox account anyway (This token requires a sandbox test account from your Apple Developer account). Is that not the case for Tap To Pay on iPhone?
1
0
1.5k
May ’26
Nested virtualization support for macOS guests using VZMacPlatformConfiguration?
Hello, I filed Feedback FB22859649 about nested virtualization for macOS guests and would like to confirm the supported API surface / limitation through Developer Forums as well. We are using Virtualization.framework to run macOS guests on Apple silicon hosts. The use case is isolated macOS VM workspaces for development and AI-agent automation. In those workspaces, developers often need to run container or VM-backed tooling inside the guest, for example Apple Container workflows, Docker/Colima/Lima-style Linux VM workflows, local Kubernetes, CI sandboxes, testcontainers, or local MCP server stacks that expect hardware-assisted virtualization from inside macOS. Environment I used for the Feedback: Apple silicon host: MacBook Air with Apple M4 Host OS: macOS 26.5 build 25F71 Xcode: 26.5, macOS SDK 26.5 Guest type: macOS VM configured through Virtualization.framework with VZMacOSBootLoader and VZMacPlatformConfiguration From the current SDK headers, I see nested virtualization support exposed on VZGener
1
0
296
May ’26
Reply to I need the proper format for adding an application ID to an entitlements file (developing outside of Xcode)
[quote='888831022, Paul from Vancouver, /thread/826941?answerId=888831022#888831022, /profile/Paul+from+Vancouver'] I can now verity the .pkg file with Transporter and upload to App Store Connect [/quote] Cool. [quote='888831022, Paul from Vancouver, /thread/826941?answerId=888831022#888831022, /profile/Paul+from+Vancouver'] but installing to the Applications folder does not work. [/quote] Installing how? By opening the .pkg with the Installer? That’s not expected to work. In general, you can’t test distribution signed code like this. Rather, upload your app to the App Store and then test it with TestFlight. For more backstory, see Don’t Run App Store Distribution-Signed Code. [quote='888831022, Paul from Vancouver, /thread/826941?answerId=888831022#888831022, /profile/Paul+from+Vancouver'] I am making an Adobe AIR app so I may need to treat the UNIX executable included in the .app file as an embedded file. [/quote] I’m not sure I understand what you’re getting at here. If you’re publishing on the Mac App Sto
Topic: Code Signing SubTopic: General Tags:
May ’26
Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified)
Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified) On Intel Macs, Xcode 26.5 (build 17F42) downloads the darwin-arm64 build of the Claude Agent rather than the darwin-x64 build that the vendor publishes at the same version. The arm64 binary fails to exec on Intel with NSPOSIXErrorDomain Code=86 (Bad CPU type in executable) and Xcode's Intelligence subsystem then surfaces this in the UI as a code-signing / sandboxing failure. Replacing the downloaded binary with the parallel darwin-x64 build, and updating the agent's Info.plist checksum and URL to match, results in a fully functional Claude Agent in Xcode 26.5 on the same Intel Mac. This was verified end to end on the affected hardware. The agent downloader in Xcode should select the URL matching the host CPU architecture (e.g. by inspecting the result of uname -m or the equivalent in Foundation). This appears to be an isolated fix to whichever component con
1
0
465
May ’26
StoreKit 2 Product.displayPrice returns USD while purchase dialog shows EUR
Hi, I'm testing my first auto-renewable subscription using StoreKit 2 and TestFlight. When loading products via: let products = try await Product.products(for: ids) the product is returned successfully, but product.displayPrice shows: $4.99 even though: My App Store account is located in Germany. The app is only intended for the German market. The native Apple purchase sheet displays the correct price in EUR. The subscription pricing is configured correctly in App Store Connect. The subscription is still in Ready to Submit / Prepare for Submission state and has not yet been approved. Example: print(product.displayPrice) returns: $4.99 while the StoreKit purchase dialog shows: 5,99 € Has anyone seen this behavior before? Is this expected for new subscriptions in TestFlight/Sandbox before the first App Review approval, or could there be another reason why displayPrice differs from the actual purchase dialog? Thanks!
Replies
1
Boosts
0
Views
756
Activity
May ’26
APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
I’m trying to diagnose an APNs provider authentication issue that began after APNs had previously been working. Summary: My iOS app can register for remote notifications and successfully sends its device token to my server. The app has the Push Notifications capability enabled in Xcode, the Bundle ID has Push Notifications enabled in Certificates, Identifiers & Profiles, and the APNs key is active in the Apple Developer portal. However, every server-side APNs send attempt now fails with: HTTP 403 {reason:InvalidProviderToken} This happens against both sandbox and production APNs endpoints. App / account details: Bundle ID / apns-topic: app.terrasignal Team ID: 837F2XGDX Current APNs Key ID: HNW7XPK2H3 APNs key type: Apple Push Notifications service (APNs) Key configuration: Team scoped, Sandbox & Production Xcode signing team: David Buck / Team ID 837F2XGDX Push Notifications capability is enabled in Xcode Device token environment tested: sandbox Server clock verified agains
Replies
7
Boosts
0
Views
892
Activity
May ’26
Reply to Documentation on APNS Live Activity Broadcast API throttle limit
does sandbox and production environment have the same rate limits per channel or do they vary? This will help me determine if sandbox load testing is sufficient.
Replies
Boosts
Views
Activity
May ’26
StoreKit 2 currentEntitlements persists after Sandbox Purchase History reset in TestFlight
I am testing a StoreKit 2 non-consumable IAP through TestFlight. Product ID: com.metabolla.plus.lifetime Type: Non-Consumable Environment: TestFlight / Sandbox Transaction.currentEntitlements keeps returning an active entitlement for this product even after: configuring a Sandbox Apple Account clearing Sandbox Purchase History reinstalling the app rebooting the device Important detail: the first TestFlight purchase was completed before configuring the Sandbox Apple Account on the device. If I temporarily change the Product ID in code, the entitlement disappears, so the issue seems tied to the original Product ID/account/receipt. Question: Can a non-consumable TestFlight purchase made before Sandbox Apple Account configuration remain associated with the original TestFlight/Apple ID identity? Is there any supported way to clear this entitlement for testing?
Replies
5
Boosts
0
Views
1.4k
Activity
May ’26
Reply to Mac Catalyst App No longer start : Cause bugs in App Store and weird macOS behaviour
I deleted all the files that contains the name of my app from the terminal using the find command. Sometimes it does start and crash and I can get a crash dump. Other times it does nothing. But I will check from the terminal to see if I can get more infos. It will take a while to test again since I don't have access to the user computer. macOS should have a way to uninstall an app for real, not leave hidden things all over the place. Apple decided to force us to use their store, then it is their responsibility to install them properly and clean them properly. macCatalyst app are sandboxed, I cannot to that myself. Thanks for the help.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
May ’26
Reply to Mac Catalyst App No longer start : Cause bugs in App Store and weird macOS behaviour
[quote='828110021, ShaddamIV, /thread/828110, /profile/ShaddamIV'] When we uninstall and reinstall an app, it should work as it did [/quote] I understand your position here, but that’s never been true on the Mac [1]. When you delete an app on macOS, the system doesn’t delete the app’s container [2]. That’s because the app container might contain vital user data, and there’s no way for macOS to know if the user has another copy of the app elsewhere on their system, or perhaps on an external hard drive that’s not connected right now. Given that reality, there are a couple of things you can do here. The first is to ask one of your affected users to remove the app and then delete the app’s container. You’ll find that in ~/Library/Containers. My advice is that you work through the process yourself, so that you can figured out the exact instructions, and then send those instructions to one of your affected users, just to see if this helps. IMPORTANT The user-visible name of your app’s container is likely different
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
May ’26
DeclaredAgeRange API not triggering in regulated regions (Brazil, Utah) — Is it functioning in production?
Hi, We've implemented age assurance logic in our app using the DeclaredAgeRange framework to comply with regulations in Brazil (Digital ECA, effective March 17, 2026) and Utah (App Store Accountability Act, effective May 6, 2026). Our implementation calls AgeRangeService.shared.isEligibleForAgeFeatures on app launch to determine whether the current user is subject to age assurance requirements, and proceeds to call requestAgeRange(ageGates:) accordingly. However, after monitoring in production since the Brazil enforcement date, we've consistently observed isEligibleForAgeFeatures returning false for users in regulated regions, with no age range data being returned. What we'd like to clarify: Is isEligibleForAgeFeatures currently returning true for users in Brazil in production (not sandbox)? For Utah — given that HB 498 pushed the developer compliance deadline to May 6, 2027, will isEligibleForAgeFeatures reflect the original May 6, 2026 activation date or the revised 2027 date? Is there a known roll
Replies
2
Boosts
0
Views
1.5k
Activity
May ’26
Reply to OpenZFS on FSKit — Proof of Concept
Technical Findings — Things That Weren't Obvious These cost significant debugging time and aren't documented anywhere: startCheckWithTask: must complete asynchronously Calling [task didCompleteWithError:nil] synchronously inside startCheckWithTask: causes fskitd to receive task completed before task started over XPC. fskitd rejects this with FSKitErrorDomain Code=27503 Task didn't start yet and never spawns the activate instance. The fix is to dispatch the completion with even a 1ms delay so FSKit can send the started notification first. app-sandbox=true is required in entitlements ExtensionKit rejects the extension entirely without com.apple.security.app-sandbox=true, even though sandboxing a filesystem extension feels counterintuitive. This needs to be paired with com.apple.developer.fskit.fsmodule=true. Container identifier must equal volume identifier for FSUnaryFileSystem FSContainer.h documents this but it's easy to miss: for unary file systems, the container identifier passed
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
May ’26
OpenZFS on FSKit — Proof of Concept
Installing ZFSFSKit.appex ? /Library/ExtensionKit/Extensions/ Substituting real Mach-O (libtool wrapper ? .libs/ZFSFSKit) Installing zfs.fs ? /Library/Filesystems/ mount_zfs: Mach-O 64-bit executable arm64 Done. Signing (before pluginkit, so it sees a valid signature)... Re-signing /Library/ExtensionKit/Extensions/ZFSFSKit.appex ad-hoc (no identity). Note: requires amfi_get_out_of_my_way=1 in boot-args. Team ID: ADHOC /Library/ExtensionKit/Extensions/ZFSFSKit.appex: replacing existing signature Done. Signature: Identifier=org.openzfsonosx.filesystems.zfs.fsext Signature=adhoc TeamIdentifier=not set Entitlements: com.apple.application-identifierADHOC.org.openzfsonosx.filesystems.zfs.fsextcom.apple.developer.fskit.fsmodulecom.apple.developer.team-identifierADHOCcom.apple.security.app-sandbox Registering with pluginkit... pluginkit -a done. Restarting fskitd... # sudo pluginkit -v -m -p com.apple.fskit.fsmodule + org.openzfsonosx.filesystems.zfs.fsext((null)) 6A12A41280FB-4190-B957-FA94DC89BB1E 2026-05-
Replies
6
Boosts
0
Views
626
Activity
May ’26
Cannot attach In-App Purchase to first macOS app version — "In-App Purchases and Subscriptions" section missing on version page
I'm trying to submit a first-time In-App Purchase together with a new version of my macOS app, but App Store Connect doesn't seem to provide a way to do this. Setup: macOS app (Bundle ID: de.andreasmaser.Screenshots) Marketing version: 1.2, Build 1 (uploaded, processed, attached to version) IAP Screenshots Pro (Product ID: de.andreasmaser.Screenshots.pro) is fully configured: status Waiting for Review, App Review screenshot present, both English + German localizations, pricing set Previous 1.1 submission was rejected under Guideline 2.1(b) because the associated In-App Purchase products have not been submitted for review Per Apple's documentation (https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase), step 3 says: On the right, scroll down to the In-App Purchases and Subscriptions section. The problem: This section does not exist on the macOS app version page. I scrolled through the entire page; the sections are: App Previews & Screenshots → Promoti
Replies
0
Boosts
0
Views
221
Activity
May ’26
Reply to Can't verify my identity for sandbox can not receive verification code
Hello - I'm not fully understanding how you are reaching each of the steps described. In App Store Connect, you should be able to create up to 10,000 Sandbox users as documented here. When creating new Sandbox users, you are not required to provide a telephone number. Sandbox user accounts created in App Store Connect can then be used to sign in to devices that are running a development-signed version of your app, and test in-app purchases without incurring any charges. Note the requirement to Enable Developer Mode on your device(s) before testing with Sandbox users. More information about testing in-app purchases in Sandbox is available here, and troubleshooting tips specific to Sandbox testing can be found here. If you continue to have problems with Sandbox user accounts and testing, please file a Feedback Assistant ticket that provides as much detail as possible - including screenshots, steps to reproduce, etc. - and reply back to this thread w
Replies
Boosts
Views
Activity
May ’26
Tap To Pay TestFlight
I'm trying to distribute our app through TestFlight's internal testing for our QA Analysts to run some tests in the non-production environment. In this page: https://developer.apple.com/documentation/storekit/testing-in-app-purchases-with-sandbox Is stated that: Apps that you download from TestFlight always run in the sandbox environment. But we ran into the issue from the ProximityReaderAPI requesting a Sandbox account anyway (This token requires a sandbox test account from your Apple Developer account). Is that not the case for Tap To Pay on iPhone?
Replies
1
Boosts
0
Views
1.5k
Activity
May ’26
Nested virtualization support for macOS guests using VZMacPlatformConfiguration?
Hello, I filed Feedback FB22859649 about nested virtualization for macOS guests and would like to confirm the supported API surface / limitation through Developer Forums as well. We are using Virtualization.framework to run macOS guests on Apple silicon hosts. The use case is isolated macOS VM workspaces for development and AI-agent automation. In those workspaces, developers often need to run container or VM-backed tooling inside the guest, for example Apple Container workflows, Docker/Colima/Lima-style Linux VM workflows, local Kubernetes, CI sandboxes, testcontainers, or local MCP server stacks that expect hardware-assisted virtualization from inside macOS. Environment I used for the Feedback: Apple silicon host: MacBook Air with Apple M4 Host OS: macOS 26.5 build 25F71 Xcode: 26.5, macOS SDK 26.5 Guest type: macOS VM configured through Virtualization.framework with VZMacOSBootLoader and VZMacPlatformConfiguration From the current SDK headers, I see nested virtualization support exposed on VZGener
Replies
1
Boosts
0
Views
296
Activity
May ’26
Reply to I need the proper format for adding an application ID to an entitlements file (developing outside of Xcode)
[quote='888831022, Paul from Vancouver, /thread/826941?answerId=888831022#888831022, /profile/Paul+from+Vancouver'] I can now verity the .pkg file with Transporter and upload to App Store Connect [/quote] Cool. [quote='888831022, Paul from Vancouver, /thread/826941?answerId=888831022#888831022, /profile/Paul+from+Vancouver'] but installing to the Applications folder does not work. [/quote] Installing how? By opening the .pkg with the Installer? That’s not expected to work. In general, you can’t test distribution signed code like this. Rather, upload your app to the App Store and then test it with TestFlight. For more backstory, see Don’t Run App Store Distribution-Signed Code. [quote='888831022, Paul from Vancouver, /thread/826941?answerId=888831022#888831022, /profile/Paul+from+Vancouver'] I am making an Adobe AIR app so I may need to treat the UNIX executable included in the .app file as an embedded file. [/quote] I’m not sure I understand what you’re getting at here. If you’re publishing on the Mac App Sto
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
May ’26
Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified)
Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified) On Intel Macs, Xcode 26.5 (build 17F42) downloads the darwin-arm64 build of the Claude Agent rather than the darwin-x64 build that the vendor publishes at the same version. The arm64 binary fails to exec on Intel with NSPOSIXErrorDomain Code=86 (Bad CPU type in executable) and Xcode's Intelligence subsystem then surfaces this in the UI as a code-signing / sandboxing failure. Replacing the downloaded binary with the parallel darwin-x64 build, and updating the agent's Info.plist checksum and URL to match, results in a fully functional Claude Agent in Xcode 26.5 on the same Intel Mac. This was verified end to end on the affected hardware. The agent downloader in Xcode should select the URL matching the host CPU architecture (e.g. by inspecting the result of uname -m or the equivalent in Foundation). This appears to be an isolated fix to whichever component con
Replies
1
Boosts
0
Views
465
Activity
May ’26