Demystify code signing and its importance in app development. Get help troubleshooting code signing issues and ensure your app is properly signed for distribution.

All subtopics
Posts under Code Signing topic

Post

Replies

Boosts

Views

Activity

Follow-up Regarding Family Controls Distribution Entitlement Request
Hello, Between April 20 and April 25 of this year, I submitted a request for the Family Controls Distribution entitlement through the following page: https://developer.apple.com/contact/request/family-controls-distribution After submitting the request, I clearly saw the message: “Thank you for your submission. We’ll review your request and contact you soon with a status update.” However, I have not received any further update or feedback since then. Afterward, I contacted Apple multiple times. Unfortunately, the responses I received consistently indicated that the relevant teams were unable to check the status or progress of the entitlement request, and no clear timeline or follow-up commitment was provided. Eventually, I was informed via email that the issue had already been escalated to the operations team for handling. However, many more days have now passed without any progress or update. At this point, it has been nearly one month since I submitted the entitlement request, yet I still have not received any result, status update, or meaningful feedback. I genuinely do not understand why the tracking and communication process for this entitlement request is so unclear and slow. I would sincerely appreciate it if the relevant team could provide a clear update regarding the current status of my request and the expected next steps. Thank you.
1
1
912
May ’26
Notarization submissions stuck "In Progress" 24+ hours — first-time enrolment, signing verified clean
Hi, Two notarization submissions on my Team ID are stuck "In Progress" well past normal turnaround. Looking for guidance on whether this is normal first-time-enrolment latency or whether something needs escalating. Team ID: U7N63C278S Submissions: 2ac71ef0-cbfa-4bdd-9059-c2554050de48 — submitted 2026-05-14 08:09 UTC (currently ~48 hours In Progress) c2b557c5-92a2-4c36-996e-812b61b67fe6 — submitted 2026-05-14 11:33 UTC (currently ~46 hours In Progress) Status: xcrun notarytool history shows both as "In Progress" xcrun notarytool info <id> returns no log URL, no message, no error No rejection email received at the APPLE_ID address Apple System Status shows Developer ID Notary Service as green Context: This is my first notarization from a newly enrolled Developer Program account (enrolled ~5 days ago). I'm aware first-time submissions can be subject to longer in-depth analysis, which is why I haven't escalated sooner. Build verification (already done): codesign --verify --deep --strict -verbose=2 exits 0 Hardened runtime flag (0x10000) present on top-level .app and every nested Mach-O Full Developer ID Application chain (signed by Developer ID Application: poojan (U7N63C278S)) Secure timestamp present Universal binary (x86_64 + arm64) Every nested framework, helper app, and binary signed Built with electron-builder, hardened-runtime entitlements, notarized via notarytool submit --wait Question: Is this within expected first-time-enrolment latency, or is there something on the notary service side that needs a nudge? Happy to provide additional codesign output or the .app bundle structure if useful. Thanks for any guidance.
3
0
1.4k
May ’26
Follow-up Regarding Family Controls Distribution Entitlement Request
Hello, Between April 20 and April 25 of this year, I submitted a request for the Family Controls Distribution entitlement through the following page: https://developer.apple.com/contact/request/family-controls-distribution After submitting the request, I clearly saw the message: “Thank you for your submission. We’ll review your request and contact you soon with a status update.” However, I have not received any further update or feedback since then. Afterward, I contacted Apple multiple times regarding this issue through Case ID: 102881595688. Unfortunately, the responses I received consistently indicated that the relevant teams were unable to check the status or progress of the entitlement request, and no clear timeline or follow-up commitment was provided. Eventually, I was informed via email that the issue had already been escalated to the operations team for handling. However, many more days have now passed without any progress or update. At this point, it has been nearly one month since I submitted the entitlement request, yet I still have not received any result, status update, or meaningful feedback. I genuinely do not understand why the tracking and communication process for this entitlement request is so unclear and slow. I would sincerely appreciate it if the relevant team could provide a clear update regarding the current status of my request and the expected next steps. Thank you.
1
0
1k
May ’26
Follow-up Regarding Family Controls Distribution Entitlement Request
Hello, Between April 20 and April 25 of this year, I submitted a request for the Family Controls Distribution entitlement through the following page: https://developer.apple.com/contact/request/family-controls-distribution After submitting the request, I clearly saw the message: “Thank you for your submission. We’ll review your request and contact you soon with a status update.” However, I have not received any further update or feedback since then. Afterward, I contacted Apple multiple times regarding this issue through Case ID: 102881595688. Unfortunately, the responses I received consistently indicated that the relevant teams were unable to check the status or progress of the entitlement request, and no clear timeline or follow-up commitment was provided. Eventually, I was informed via email that the issue had already been escalated to the operations team for handling. However, many more days have now passed without any progress or update. At this point, it has been nearly one month since I submitted the entitlement request, yet I still have not received any result, status update, or meaningful feedback. I genuinely do not understand why the tracking and communication process for this entitlement request is so unclear and slow. I would sincerely appreciate it if the relevant team could provide a clear update regarding the current status of my request and the expected next steps. Thank you.
1
0
945
May ’26
2+ months blocked on error 7000. Apple's "correct escalation path" is broken.
I'm posting this so other devs hitting error 7000 know they're not alone, and so this gets some visibility outside the support ticket black hole. Timeline: End of February 2026: first notarization attempts. All rejected with status code 7000 March 1st: first support case opened Today, beginning of May: still blocked. Still error 7000 Four cases: 102833704616, 102836645198, 102842517951, 102865000390. Different advisors each time. I've uploaded my government ID twice. When I ask for a status, the answer is "I'll get back to you when I have news." Then silence. My setup is fine. Team ID is Y564MF82K8. App is signed with Developer ID Application, hardened runtime, secure timestamp, no get-task-allow, deep verify clean. Apple rejects the submission before inspecting the binary. The block is on Apple's side. Somebody needs to push a button but they cannot agree who needs to push it, so they just pass it from one department to another. The "correct escalation path" doesn't work. Quinn (Apple DTS engineer) keeps saying on this forum that error 7000 is administrative and the path is Developer Program Support (https://developer.apple.com/forums/thread/118465?answerId=379585022#379585022). I followed that path four times. The cases just sit there. Threads on this forum about error 7000 go back to 2019. Six years. Devs report cases stuck for weeks, months, with the same scripted responses. Apple knows. Apple does nothing. I'm a solo dev and I want to do a proper launch of my SaaS on all major desktop platforms. I paid the $99. I built the app. I signed every agreement. I cannot launch on macOS because Apple's departments cannot agree on who needs to push a button. If anyone here has actually unblocked error 7000, please share what worked. The official path obviously doesn't.
6
1
1.2k
May ’26
StatusCode 7000 "Team is not yet configured for notarization". It's been over five days, no resolution
Hi all, I'm submitting a Developer ID-signed, hardened-runtime app for notarization. Every submission returns: "statusCode: 7000 statusSummary: Team is not yet configured for notarization. Please contact Developer Programs Support..." Team ID: V67NRZ84A2. Apple Developer membership is active, Developer ID Application certificate is valid, signing/verification all clean. Already opened a support case last week via the recommended path. The "contact page" on the developer site said Apple usually responds within 2 business days.... Has anyone hit this and gotten it resolved? How long did it take, and was there a more effective channel than the standard support form? I've seen people on Reddit claim they've actually been able to call a Developer phone line, but I haven't seen a valid phone number anywhere. I appreciate your response!
4
0
1.3k
May ’26
Team ID not matching my Newly registered Developer Account
I originally signed into Xcode using my iCloud email account. A few days later, I enrolled in the Apple Developer Program using the same account. However, I noticed that Apple generated a different Team ID for the developer account, which does not match the Team ID that was originally associated with my Xcode account. Now, whenever I sign in with that same account, I continue to get the original Team ID instead of the new one created with the developer account. Because of this mismatch, I’m unable to properly link my app and developer account. I would like assistance understanding why there are two different Team IDs for the same Apple account and how I can make Xcode use the correct developer Team ID. @Developer Technical Support
1
0
711
May ’26
Team ID not matching my Newly registered Developer Account
I originally signed into Xcode using my iCloud email account. A few days later, I enrolled in the Apple Developer Program using the same account. However, I noticed that Apple generated a different Team ID for the developer account, which does not match the Team ID that was originally associated with my Xcode account. Now, whenever I sign in with that same account, I continue to get the original Team ID instead of the new one created with the developer account. Because of this mismatch, I’m unable to properly link my app and developer account. I would like assistance understanding why there are two different Team IDs for the same Apple account and how I can make Xcode use the correct developer Team ID.
1
0
849
May ’26
Export archive for app-store distribution command: 'xcodebuild -exportArchive -archivePath ...' exited with non-zero exit-code: 70
Hi, I have a project that integrates the Firebase SDK via SPM as a dependency of an internal Swift Package: My app ⟶ My Library ⟶ Firebase SDK The project builds successfully and can be archived locally ✅. The uploaded .ipa is valid and gets published 🚀. However, we are now trying to automate the release process using Xcode Cloud, but the iOS Archive action is failing ❌ on Xcode Cloud. The logs show the following error ⬇️: error: exportArchive codesign command failed (/Volumes/workspace/tmp/XcodeDistPipeline/XcodeDistPipeline.~~~oomCvM/Root/Payload/base-ios.app/Frameworks/FirebaseAnalytics.framework: replacing existing signature /Volumes/workspace/tmp/XcodeDistPipeline/XcodeDistPipeline.~~~oomCvM/Root/Payload/base-ios.app/Frameworks/FirebaseAnalytics.framework: invalid or corrupted code requirement(s) Requirement syntax error(s): line 1:178: unexpected token: <COMPANY_NAME> ) ** EXPORT FAILED ** I have been researching this issue for a while and have tried several solutions to fix it, but with no luck. Even though the error points to a specific library—the Firebase SDK—I don’t believe Firebase is the root cause. There were related issues in the past, but those were already fixed by the Firebase team, and as I mentioned, the project archives correctly when built locally. On the other hand, the error states: line 1:178: unexpected token: <COMPANY_ACRONYM> This makes me wonder if there’s an issue parsing our Team Name during the re-signing process, as it contains special characters ": "name": "Apple Distribution: Company Full Name "COMPANY_ACRONYM""
2
0
1.7k
May ’26
Family Controls (Distribution) pending ~1 month after app transfer
Hoping to get visibility on a Family Controls (Distribution) entitlement request pending without status updates after an app transfer. Context: Digital wellbeing app, 500K+ active iOS users Previous team had Family Controls (Distribution) approved and shipping to production App transferred to new team (H2HM68H8PP) ~1 month ago; entitlement re-requested immediately Capability page shows "View Requests (6)" with no approvals, rejections, or updates Developer Support cases opened (102883853173, 20000112879750, 102875975624) — confirmed they cannot check entitlement status Impact: Core app feature depends on Family Controls. Production app for 500K+ users will break once transfer fully propagates at provisioning level. This is a continuity issue, not a new-app launch — entitlement was previously approved on the prior team. Questions: Recommended escalation path for post-transfer entitlement requests? Should I stop resubmitting to avoid queue deprioritization? Could the entitlements team provide a status update? Happy to share bundle ID, previous team ID, and request dates privately with Apple staff.
0
3
1.2k
May ’26
Developer ID Application certificate creation
Hello, We are currently in the process of creating our Developer ID Application certificate which is due to expire. While creating the certificate, we were posed with the option of choosing a Developer ID Certificate Intermediary G2 Sub CA which is supported by Xcode 11.4.1 and later Previous Sub CA We currently build our application out of Xcode using Make or CMake files and perform the codesign and productsign using the codesign commands. We also use 2 different build machines, Ventura with Xcode 14.3 for our latest releases High Sierra (10.13) with Xcode 10.1 for legacy releases to support some customers. Can you please let us know which Developer ID Certificate Intermediary we should choose for generating the new Developer ID Application certificate?
1
0
1.5k
May ’26
Family Controls Distribution entitlement — requests submitted 2+ weeks ago, all still "Submitted"
I've been waiting on the Family Controls distribution entitlement for my app for over two weeks with use case to self direct app and sites blocking Setup: Development entitlement: ✅ approved and working Request ID: 27684X55GC The blocker: Xcode warns: "Bundle identifier is using development only version of Family Controls (Development) capability. Please request access to Family Controls (Distribution)." Archiving for App Store fails with provisioning profile errors on all my targets Questions: Is 2+ weeks normal for distribution entitlement approval? Any recommended path to escalate besides the request form and have also emailed apple support?
0
0
903
May ’26
Family Controls entitlement: no response for over 1 month
Hi, I submitted my Family Controls entitlement requests on April 15 for my iOS app, but I still haven’t received an approval, rejection, or any status update. This is blocking my ability to properly test and move forward with the app, since it depends on the Screen Time / Family Controls APIs. I've tried contact to apple developer support and filed a code-level support on app connect dashboard. and still nothing received. Here is the request information: code-level support case id: 19834379 apple developer support case id: 102878196850 Family Controls Distribution RequestId: BT4C47F5VB,SLP56WRZ3J,BZ7MF3R4FF,5HAY5UF5X2,P49SM5C859,KG2T2X2L76,N353H759C4 Thanks.
0
0
937
May ’26
4 notarytool submissions stuck "In Progress" 12+ hours (Team NS22D2XK8A)
Hi DTS, I have 4 notarytool submissions all stuck in "In Progress" with no movement for 12+ hours. 'xcrun notarytool log <id›' returns "Submission log is not yet available" for all of them - they don't appear to have been processed at all. Team Identifier: NS22D2XK8A 1 .dmg submission at 2026-05-12T01:35Z (12+ hours stuck) dmg submissions between 10:04Z and 12:12Z This is my first time notarizing with this Team ID - possibly the new-account first-submission "in-depth analysis" delay? The DMG passes every standard check: Signed with Developer ID Application (Team NS22D2XK8A) Hardened runtime on all 6 embedded binaries (codesign flags 0x10000) Full authority chain: Developer ID App → Developer ID CA → Apple Root CA Secure timestamp present Entitlements: allow-jit, allow-unsigned-executable-memory, disable-library-validation, network.client, network.server, files.user-selected. read-write codesign --verify -deep --strict passes cleanly spctl source = "Developer ID Application" (correct) DMG itself signed inside-out per TN2206 I have read the other recent "stuck In Progress" threads from new Developer IDs - same pattern. Could the queue be unblocked, or is there a team-side configuration that needs flipping? Happy to provide submission UUIDs + filenames privately via Feedback Assistant or DM. Thanks!
1
0
942
May ’26
FamilyControls distribution pending for 14+ days and not sure about approach
Hi, I'm building a wellness app called that helps users manage their phone usage based on their consumption, using the Screen Time API. I need the Family Controls (Distribution) entitlement to ship it. I've already submitted multiple requests across all my bundle IDs, but due to the lack of confirmation feedback after each submission, I may have submitted more than needed. Regardless, the oldest request submitted was on April 22nd (exactly 2 weeks ago), without any reply or change. Is this normal ? Also, I came across a forum post (https://developer.apple.com/forums/thread/821964?answerId=885672022#885672022) suggesting that the entitlement is now scoped at the team level rather than per bundle ID, and that I should resubmit a single request. I want to do the right thing here but I'm not sure whether to resubmit or wait and I don't want to make the situation worse than it already is. We're about a month away from our launch date and this is the last remaining blocker for both TestFlight and App Store submission. Any guidance on next steps, or help prioritizing this, would mean a lot. Thanks so much,
2
1
1.2k
May ’26
Notarization
tle: New account — all notarization submissions stuck In Progress 26+ hours Hi, I recently enrolled in the Apple Developer Program and all my notarization submissions have been stuck "In Progress" for over 26 hours with no resolution. Team ID: 799833449H Submission IDs: bb31ba38-9ff4-416d-b6ea-8ad88b84a2be (26+ hours) 8fdd039d-3db4-4e96-8111-37dba9d4afd2 (25+ hours) 685cba55-aacd-4a05-8086-707a6b88e138 (23+ hours) Binary is a universal macOS binary, codesign verifies cleanly with hardened runtime. notarytool log returns "not yet available" for all. Is this the in-depth analysis path for new accounts? Any ETA or action needed from my side?
2
1
491
May ’26
Notarization rejected with statusCode 7000 for months — “Team is not yet configured for notarization”
Hello, My macOS notarization has been blocked since March with: "status": "Rejected", "statusCode": 7000, "statusSummary": "Team is not yet configured for notarization", "issues": null Latest fresh probe: Submission ID: 3201b921-2313-45fd-b274-0e46d3fb03c2 Upload time: 2026-05-09T12:37:16Z Archive: KwantflowNotaryProbe-20260509T123714Z.zip Status: Rejected Error: -2052 / 7000 Issues: None Support cases: 102842156916 — Development and Technical → Other Development or Technical Questions 102882811151 — Development and Technical → Code Signing The archive uploads successfully and notarytool history/log work, but every submission is rejected before binary validation. The log shows no signing, entitlement, hardened runtime, timestamp, or executable issues. Apple forum answers say this is a Developer Program Support issue, not DTS/code-level. I have already contacted Developer Support, but the issue is still unresolved and blocks our macOS release. Has anyone recently resolved -2052 / 7000 / “Team is not yet configured for notarization”? Did Apple need to manually enable something on the team/account? Thank you.
2
0
974
May ’26
com.apple.developer.automatic-assessment-configuration entitlement missing from manually downloaded Distribution/InHouse Provisioning Profile
We are implementing an exam mode feature for an educational app used in schools, which restricts device usage during assessments. We requested the Automatic Assessment Configuration capability, received approval from Apple, and confirmed that the capability is listed as Assigned under our App ID in the Apple Developer portal. What works: When using a Development Provisioning Profile (downloaded from the portal), the entitlement key com.apple.developer.automatic-assessment-configuration is included in the profile, and our exam lock feature works correctly in development testing. The problem: When we manually download a Distribution (InHouse/Enterprise) Provisioning Profile from the portal — even after creating a new one — the entitlement key com.apple.developer.automatic-assessment-configuration is not present in the profile. verified this by running: security cms -D -i YourProfile.mobileprovision The key appears in the Development PP but is absent in the manually downloaded Distribution PP, despite the App ID showing the capability as Assigned. Note: When using Xcode's automatic signing, the generated profile does include the entitlement correctly. However, due to our organization's internal security policy, we are required to use manually managed provisioning profiles and cannot use Xcode automatic signing for distribution builds. Questions: Is the com.apple.developer.automatic-assessment-configuration entitlement intentionally restricted to Development profiles only, or is this a known portal issue with managed capabilities not being embedded in manually created Distribution profiles? Is it technically supported and intended to use AEAssessmentSession in an InHouse (Enterprise) distribution environment? If InHouse is not supported, is the correct path to test internally via Development profiles and then submit through App Store distribution to include this entitlement in production? Any guidance on the correct technical direction would be greatly appreciated.
3
0
1.3k
May ’26
notarytool submissions stuck "In Progress" indefinitely — account-specific issue?
Hello, I've been trying to notarize my macOS app using xcrun notarytool, but all submissions get stuck in "In Progress" status indefinitely (30+ minutes, never resolve). Environment: Tool: xcrun notarytool (Xcode 16) Bundle ID: io.pix-cull.app Team ID: C473MUK7G2 App type: PyInstaller-built .app, wrapped in a signed .dmg Stuck submission IDs: 00e953da (first attempt) f7ab027e 3e35fc3f 293541bc-ba61-4ccb-a273-a8f34cda2422 (most recent) Steps I've already taken: Disabled UPX compression in PyInstaller spec Signed all binaries inside-out (deepest first, .app last) Used --timestamp flag during codesign Verified Apple system status — all services show green Waited 24+ hours on the oldest submission — still "In Progress" What I observe: Running xcrun notarytool info <id> returns status: In Progress every time, no matter how long I wait. The submission never transitions to "Accepted" or "Invalid". Other developers report notarization completing in 2–15 minutes. I also submitted a ticket to Apple Developer Support (DTS), but I'm posting here as well in case anyone has seen this pattern. Is there something wrong with my account that could cause all submissions to stall? Any guidance would be appreciated. Thank you.
1
0
706
May ’26
Follow-up Regarding Family Controls Distribution Entitlement Request
Hello, Between April 20 and April 25 of this year, I submitted a request for the Family Controls Distribution entitlement through the following page: https://developer.apple.com/contact/request/family-controls-distribution After submitting the request, I clearly saw the message: “Thank you for your submission. We’ll review your request and contact you soon with a status update.” However, I have not received any further update or feedback since then. Afterward, I contacted Apple multiple times. Unfortunately, the responses I received consistently indicated that the relevant teams were unable to check the status or progress of the entitlement request, and no clear timeline or follow-up commitment was provided. Eventually, I was informed via email that the issue had already been escalated to the operations team for handling. However, many more days have now passed without any progress or update. At this point, it has been nearly one month since I submitted the entitlement request, yet I still have not received any result, status update, or meaningful feedback. I genuinely do not understand why the tracking and communication process for this entitlement request is so unclear and slow. I would sincerely appreciate it if the relevant team could provide a clear update regarding the current status of my request and the expected next steps. Thank you.
Replies
1
Boosts
1
Views
912
Activity
May ’26
Family Control Distribution
It has been 20 days since we applied for Family Controls (Distribution) permission, but the status still shows as Submitted. Is there any way to expedite the review process?
Replies
1
Boosts
0
Views
1.2k
Activity
May ’26
Notarization submissions stuck "In Progress" 24+ hours — first-time enrolment, signing verified clean
Hi, Two notarization submissions on my Team ID are stuck "In Progress" well past normal turnaround. Looking for guidance on whether this is normal first-time-enrolment latency or whether something needs escalating. Team ID: U7N63C278S Submissions: 2ac71ef0-cbfa-4bdd-9059-c2554050de48 — submitted 2026-05-14 08:09 UTC (currently ~48 hours In Progress) c2b557c5-92a2-4c36-996e-812b61b67fe6 — submitted 2026-05-14 11:33 UTC (currently ~46 hours In Progress) Status: xcrun notarytool history shows both as "In Progress" xcrun notarytool info <id> returns no log URL, no message, no error No rejection email received at the APPLE_ID address Apple System Status shows Developer ID Notary Service as green Context: This is my first notarization from a newly enrolled Developer Program account (enrolled ~5 days ago). I'm aware first-time submissions can be subject to longer in-depth analysis, which is why I haven't escalated sooner. Build verification (already done): codesign --verify --deep --strict -verbose=2 exits 0 Hardened runtime flag (0x10000) present on top-level .app and every nested Mach-O Full Developer ID Application chain (signed by Developer ID Application: poojan (U7N63C278S)) Secure timestamp present Universal binary (x86_64 + arm64) Every nested framework, helper app, and binary signed Built with electron-builder, hardened-runtime entitlements, notarized via notarytool submit --wait Question: Is this within expected first-time-enrolment latency, or is there something on the notary service side that needs a nudge? Happy to provide additional codesign output or the .app bundle structure if useful. Thanks for any guidance.
Replies
3
Boosts
0
Views
1.4k
Activity
May ’26
Follow-up Regarding Family Controls Distribution Entitlement Request
Hello, Between April 20 and April 25 of this year, I submitted a request for the Family Controls Distribution entitlement through the following page: https://developer.apple.com/contact/request/family-controls-distribution After submitting the request, I clearly saw the message: “Thank you for your submission. We’ll review your request and contact you soon with a status update.” However, I have not received any further update or feedback since then. Afterward, I contacted Apple multiple times regarding this issue through Case ID: 102881595688. Unfortunately, the responses I received consistently indicated that the relevant teams were unable to check the status or progress of the entitlement request, and no clear timeline or follow-up commitment was provided. Eventually, I was informed via email that the issue had already been escalated to the operations team for handling. However, many more days have now passed without any progress or update. At this point, it has been nearly one month since I submitted the entitlement request, yet I still have not received any result, status update, or meaningful feedback. I genuinely do not understand why the tracking and communication process for this entitlement request is so unclear and slow. I would sincerely appreciate it if the relevant team could provide a clear update regarding the current status of my request and the expected next steps. Thank you.
Replies
1
Boosts
0
Views
1k
Activity
May ’26
Follow-up Regarding Family Controls Distribution Entitlement Request
Hello, Between April 20 and April 25 of this year, I submitted a request for the Family Controls Distribution entitlement through the following page: https://developer.apple.com/contact/request/family-controls-distribution After submitting the request, I clearly saw the message: “Thank you for your submission. We’ll review your request and contact you soon with a status update.” However, I have not received any further update or feedback since then. Afterward, I contacted Apple multiple times regarding this issue through Case ID: 102881595688. Unfortunately, the responses I received consistently indicated that the relevant teams were unable to check the status or progress of the entitlement request, and no clear timeline or follow-up commitment was provided. Eventually, I was informed via email that the issue had already been escalated to the operations team for handling. However, many more days have now passed without any progress or update. At this point, it has been nearly one month since I submitted the entitlement request, yet I still have not received any result, status update, or meaningful feedback. I genuinely do not understand why the tracking and communication process for this entitlement request is so unclear and slow. I would sincerely appreciate it if the relevant team could provide a clear update regarding the current status of my request and the expected next steps. Thank you.
Replies
1
Boosts
0
Views
945
Activity
May ’26
2+ months blocked on error 7000. Apple's "correct escalation path" is broken.
I'm posting this so other devs hitting error 7000 know they're not alone, and so this gets some visibility outside the support ticket black hole. Timeline: End of February 2026: first notarization attempts. All rejected with status code 7000 March 1st: first support case opened Today, beginning of May: still blocked. Still error 7000 Four cases: 102833704616, 102836645198, 102842517951, 102865000390. Different advisors each time. I've uploaded my government ID twice. When I ask for a status, the answer is "I'll get back to you when I have news." Then silence. My setup is fine. Team ID is Y564MF82K8. App is signed with Developer ID Application, hardened runtime, secure timestamp, no get-task-allow, deep verify clean. Apple rejects the submission before inspecting the binary. The block is on Apple's side. Somebody needs to push a button but they cannot agree who needs to push it, so they just pass it from one department to another. The "correct escalation path" doesn't work. Quinn (Apple DTS engineer) keeps saying on this forum that error 7000 is administrative and the path is Developer Program Support (https://developer.apple.com/forums/thread/118465?answerId=379585022#379585022). I followed that path four times. The cases just sit there. Threads on this forum about error 7000 go back to 2019. Six years. Devs report cases stuck for weeks, months, with the same scripted responses. Apple knows. Apple does nothing. I'm a solo dev and I want to do a proper launch of my SaaS on all major desktop platforms. I paid the $99. I built the app. I signed every agreement. I cannot launch on macOS because Apple's departments cannot agree on who needs to push a button. If anyone here has actually unblocked error 7000, please share what worked. The official path obviously doesn't.
Replies
6
Boosts
1
Views
1.2k
Activity
May ’26
StatusCode 7000 "Team is not yet configured for notarization". It's been over five days, no resolution
Hi all, I'm submitting a Developer ID-signed, hardened-runtime app for notarization. Every submission returns: "statusCode: 7000 statusSummary: Team is not yet configured for notarization. Please contact Developer Programs Support..." Team ID: V67NRZ84A2. Apple Developer membership is active, Developer ID Application certificate is valid, signing/verification all clean. Already opened a support case last week via the recommended path. The "contact page" on the developer site said Apple usually responds within 2 business days.... Has anyone hit this and gotten it resolved? How long did it take, and was there a more effective channel than the standard support form? I've seen people on Reddit claim they've actually been able to call a Developer phone line, but I haven't seen a valid phone number anywhere. I appreciate your response!
Replies
4
Boosts
0
Views
1.3k
Activity
May ’26
Team ID not matching my Newly registered Developer Account
I originally signed into Xcode using my iCloud email account. A few days later, I enrolled in the Apple Developer Program using the same account. However, I noticed that Apple generated a different Team ID for the developer account, which does not match the Team ID that was originally associated with my Xcode account. Now, whenever I sign in with that same account, I continue to get the original Team ID instead of the new one created with the developer account. Because of this mismatch, I’m unable to properly link my app and developer account. I would like assistance understanding why there are two different Team IDs for the same Apple account and how I can make Xcode use the correct developer Team ID. @Developer Technical Support
Replies
1
Boosts
0
Views
711
Activity
May ’26
Team ID not matching my Newly registered Developer Account
I originally signed into Xcode using my iCloud email account. A few days later, I enrolled in the Apple Developer Program using the same account. However, I noticed that Apple generated a different Team ID for the developer account, which does not match the Team ID that was originally associated with my Xcode account. Now, whenever I sign in with that same account, I continue to get the original Team ID instead of the new one created with the developer account. Because of this mismatch, I’m unable to properly link my app and developer account. I would like assistance understanding why there are two different Team IDs for the same Apple account and how I can make Xcode use the correct developer Team ID.
Replies
1
Boosts
0
Views
849
Activity
May ’26
Export archive for app-store distribution command: 'xcodebuild -exportArchive -archivePath ...' exited with non-zero exit-code: 70
Hi, I have a project that integrates the Firebase SDK via SPM as a dependency of an internal Swift Package: My app ⟶ My Library ⟶ Firebase SDK The project builds successfully and can be archived locally ✅. The uploaded .ipa is valid and gets published 🚀. However, we are now trying to automate the release process using Xcode Cloud, but the iOS Archive action is failing ❌ on Xcode Cloud. The logs show the following error ⬇️: error: exportArchive codesign command failed (/Volumes/workspace/tmp/XcodeDistPipeline/XcodeDistPipeline.~~~oomCvM/Root/Payload/base-ios.app/Frameworks/FirebaseAnalytics.framework: replacing existing signature /Volumes/workspace/tmp/XcodeDistPipeline/XcodeDistPipeline.~~~oomCvM/Root/Payload/base-ios.app/Frameworks/FirebaseAnalytics.framework: invalid or corrupted code requirement(s) Requirement syntax error(s): line 1:178: unexpected token: <COMPANY_NAME> ) ** EXPORT FAILED ** I have been researching this issue for a while and have tried several solutions to fix it, but with no luck. Even though the error points to a specific library—the Firebase SDK—I don’t believe Firebase is the root cause. There were related issues in the past, but those were already fixed by the Firebase team, and as I mentioned, the project archives correctly when built locally. On the other hand, the error states: line 1:178: unexpected token: <COMPANY_ACRONYM> This makes me wonder if there’s an issue parsing our Team Name during the re-signing process, as it contains special characters ": "name": "Apple Distribution: Company Full Name "COMPANY_ACRONYM""
Replies
2
Boosts
0
Views
1.7k
Activity
May ’26
Family Controls (Distribution) pending ~1 month after app transfer
Hoping to get visibility on a Family Controls (Distribution) entitlement request pending without status updates after an app transfer. Context: Digital wellbeing app, 500K+ active iOS users Previous team had Family Controls (Distribution) approved and shipping to production App transferred to new team (H2HM68H8PP) ~1 month ago; entitlement re-requested immediately Capability page shows "View Requests (6)" with no approvals, rejections, or updates Developer Support cases opened (102883853173, 20000112879750, 102875975624) — confirmed they cannot check entitlement status Impact: Core app feature depends on Family Controls. Production app for 500K+ users will break once transfer fully propagates at provisioning level. This is a continuity issue, not a new-app launch — entitlement was previously approved on the prior team. Questions: Recommended escalation path for post-transfer entitlement requests? Should I stop resubmitting to avoid queue deprioritization? Could the entitlements team provide a status update? Happy to share bundle ID, previous team ID, and request dates privately with Apple staff.
Replies
0
Boosts
3
Views
1.2k
Activity
May ’26
Developer ID Application certificate creation
Hello, We are currently in the process of creating our Developer ID Application certificate which is due to expire. While creating the certificate, we were posed with the option of choosing a Developer ID Certificate Intermediary G2 Sub CA which is supported by Xcode 11.4.1 and later Previous Sub CA We currently build our application out of Xcode using Make or CMake files and perform the codesign and productsign using the codesign commands. We also use 2 different build machines, Ventura with Xcode 14.3 for our latest releases High Sierra (10.13) with Xcode 10.1 for legacy releases to support some customers. Can you please let us know which Developer ID Certificate Intermediary we should choose for generating the new Developer ID Application certificate?
Replies
1
Boosts
0
Views
1.5k
Activity
May ’26
Family Controls Distribution entitlement — requests submitted 2+ weeks ago, all still "Submitted"
I've been waiting on the Family Controls distribution entitlement for my app for over two weeks with use case to self direct app and sites blocking Setup: Development entitlement: ✅ approved and working Request ID: 27684X55GC The blocker: Xcode warns: "Bundle identifier is using development only version of Family Controls (Development) capability. Please request access to Family Controls (Distribution)." Archiving for App Store fails with provisioning profile errors on all my targets Questions: Is 2+ weeks normal for distribution entitlement approval? Any recommended path to escalate besides the request form and have also emailed apple support?
Replies
0
Boosts
0
Views
903
Activity
May ’26
Family Controls entitlement: no response for over 1 month
Hi, I submitted my Family Controls entitlement requests on April 15 for my iOS app, but I still haven’t received an approval, rejection, or any status update. This is blocking my ability to properly test and move forward with the app, since it depends on the Screen Time / Family Controls APIs. I've tried contact to apple developer support and filed a code-level support on app connect dashboard. and still nothing received. Here is the request information: code-level support case id: 19834379 apple developer support case id: 102878196850 Family Controls Distribution RequestId: BT4C47F5VB,SLP56WRZ3J,BZ7MF3R4FF,5HAY5UF5X2,P49SM5C859,KG2T2X2L76,N353H759C4 Thanks.
Replies
0
Boosts
0
Views
937
Activity
May ’26
4 notarytool submissions stuck "In Progress" 12+ hours (Team NS22D2XK8A)
Hi DTS, I have 4 notarytool submissions all stuck in "In Progress" with no movement for 12+ hours. 'xcrun notarytool log <id›' returns "Submission log is not yet available" for all of them - they don't appear to have been processed at all. Team Identifier: NS22D2XK8A 1 .dmg submission at 2026-05-12T01:35Z (12+ hours stuck) dmg submissions between 10:04Z and 12:12Z This is my first time notarizing with this Team ID - possibly the new-account first-submission "in-depth analysis" delay? The DMG passes every standard check: Signed with Developer ID Application (Team NS22D2XK8A) Hardened runtime on all 6 embedded binaries (codesign flags 0x10000) Full authority chain: Developer ID App → Developer ID CA → Apple Root CA Secure timestamp present Entitlements: allow-jit, allow-unsigned-executable-memory, disable-library-validation, network.client, network.server, files.user-selected. read-write codesign --verify -deep --strict passes cleanly spctl source = "Developer ID Application" (correct) DMG itself signed inside-out per TN2206 I have read the other recent "stuck In Progress" threads from new Developer IDs - same pattern. Could the queue be unblocked, or is there a team-side configuration that needs flipping? Happy to provide submission UUIDs + filenames privately via Feedback Assistant or DM. Thanks!
Replies
1
Boosts
0
Views
942
Activity
May ’26
FamilyControls distribution pending for 14+ days and not sure about approach
Hi, I'm building a wellness app called that helps users manage their phone usage based on their consumption, using the Screen Time API. I need the Family Controls (Distribution) entitlement to ship it. I've already submitted multiple requests across all my bundle IDs, but due to the lack of confirmation feedback after each submission, I may have submitted more than needed. Regardless, the oldest request submitted was on April 22nd (exactly 2 weeks ago), without any reply or change. Is this normal ? Also, I came across a forum post (https://developer.apple.com/forums/thread/821964?answerId=885672022#885672022) suggesting that the entitlement is now scoped at the team level rather than per bundle ID, and that I should resubmit a single request. I want to do the right thing here but I'm not sure whether to resubmit or wait and I don't want to make the situation worse than it already is. We're about a month away from our launch date and this is the last remaining blocker for both TestFlight and App Store submission. Any guidance on next steps, or help prioritizing this, would mean a lot. Thanks so much,
Replies
2
Boosts
1
Views
1.2k
Activity
May ’26
Notarization
tle: New account — all notarization submissions stuck In Progress 26+ hours Hi, I recently enrolled in the Apple Developer Program and all my notarization submissions have been stuck "In Progress" for over 26 hours with no resolution. Team ID: 799833449H Submission IDs: bb31ba38-9ff4-416d-b6ea-8ad88b84a2be (26+ hours) 8fdd039d-3db4-4e96-8111-37dba9d4afd2 (25+ hours) 685cba55-aacd-4a05-8086-707a6b88e138 (23+ hours) Binary is a universal macOS binary, codesign verifies cleanly with hardened runtime. notarytool log returns "not yet available" for all. Is this the in-depth analysis path for new accounts? Any ETA or action needed from my side?
Replies
2
Boosts
1
Views
491
Activity
May ’26
Notarization rejected with statusCode 7000 for months — “Team is not yet configured for notarization”
Hello, My macOS notarization has been blocked since March with: "status": "Rejected", "statusCode": 7000, "statusSummary": "Team is not yet configured for notarization", "issues": null Latest fresh probe: Submission ID: 3201b921-2313-45fd-b274-0e46d3fb03c2 Upload time: 2026-05-09T12:37:16Z Archive: KwantflowNotaryProbe-20260509T123714Z.zip Status: Rejected Error: -2052 / 7000 Issues: None Support cases: 102842156916 — Development and Technical → Other Development or Technical Questions 102882811151 — Development and Technical → Code Signing The archive uploads successfully and notarytool history/log work, but every submission is rejected before binary validation. The log shows no signing, entitlement, hardened runtime, timestamp, or executable issues. Apple forum answers say this is a Developer Program Support issue, not DTS/code-level. I have already contacted Developer Support, but the issue is still unresolved and blocks our macOS release. Has anyone recently resolved -2052 / 7000 / “Team is not yet configured for notarization”? Did Apple need to manually enable something on the team/account? Thank you.
Replies
2
Boosts
0
Views
974
Activity
May ’26
com.apple.developer.automatic-assessment-configuration entitlement missing from manually downloaded Distribution/InHouse Provisioning Profile
We are implementing an exam mode feature for an educational app used in schools, which restricts device usage during assessments. We requested the Automatic Assessment Configuration capability, received approval from Apple, and confirmed that the capability is listed as Assigned under our App ID in the Apple Developer portal. What works: When using a Development Provisioning Profile (downloaded from the portal), the entitlement key com.apple.developer.automatic-assessment-configuration is included in the profile, and our exam lock feature works correctly in development testing. The problem: When we manually download a Distribution (InHouse/Enterprise) Provisioning Profile from the portal — even after creating a new one — the entitlement key com.apple.developer.automatic-assessment-configuration is not present in the profile. verified this by running: security cms -D -i YourProfile.mobileprovision The key appears in the Development PP but is absent in the manually downloaded Distribution PP, despite the App ID showing the capability as Assigned. Note: When using Xcode's automatic signing, the generated profile does include the entitlement correctly. However, due to our organization's internal security policy, we are required to use manually managed provisioning profiles and cannot use Xcode automatic signing for distribution builds. Questions: Is the com.apple.developer.automatic-assessment-configuration entitlement intentionally restricted to Development profiles only, or is this a known portal issue with managed capabilities not being embedded in manually created Distribution profiles? Is it technically supported and intended to use AEAssessmentSession in an InHouse (Enterprise) distribution environment? If InHouse is not supported, is the correct path to test internally via Development profiles and then submit through App Store distribution to include this entitlement in production? Any guidance on the correct technical direction would be greatly appreciated.
Replies
3
Boosts
0
Views
1.3k
Activity
May ’26
notarytool submissions stuck "In Progress" indefinitely — account-specific issue?
Hello, I've been trying to notarize my macOS app using xcrun notarytool, but all submissions get stuck in "In Progress" status indefinitely (30+ minutes, never resolve). Environment: Tool: xcrun notarytool (Xcode 16) Bundle ID: io.pix-cull.app Team ID: C473MUK7G2 App type: PyInstaller-built .app, wrapped in a signed .dmg Stuck submission IDs: 00e953da (first attempt) f7ab027e 3e35fc3f 293541bc-ba61-4ccb-a273-a8f34cda2422 (most recent) Steps I've already taken: Disabled UPX compression in PyInstaller spec Signed all binaries inside-out (deepest first, .app last) Used --timestamp flag during codesign Verified Apple system status — all services show green Waited 24+ hours on the oldest submission — still "In Progress" What I observe: Running xcrun notarytool info <id> returns status: In Progress every time, no matter how long I wait. The submission never transitions to "Accepted" or "Invalid". Other developers report notarization completing in 2–15 minutes. I also submitted a ticket to Apple Developer Support (DTS), but I'm posting here as well in case anyone has seen this pattern. Is there something wrong with my account that could cause all submissions to stall? Any guidance would be appreciated. Thank you.
Replies
1
Boosts
0
Views
706
Activity
May ’26