Notarization stuck in “In Progress” for all submissions since April 4th

Well it looks this morning the 4 submissions were rejected but sayings the Team is not configured yet I don't understand what's going on with apple everything seems to be OK on the dev account I've accepted all agreements no error message and I'haven't changed anything during the meanwhile and I today I tried to submit another build stuck in progress again ! I have verified too and record again my TeamID with "xcrun notarytool store-credentials" which return

This process stores your credentials securely in the Keychain. You reference these credentials later using a profile name.

Validating your credentials...
Success. Credentials validated.
Credentials saved to Keychain.

I've checked everything certificated, keychain etc but still blocked in progress, here is the rejected logs :

  "rejected": [
    {
      "logFormatVersion": 1,
      "jobId": "b4872e7a-e2b5-485e-9223-09f3ed94958f",
      "status": "Rejected",
      "statusSummary": "Team is not yet configured for notarization. Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.",
      "statusCode": 7000,
      "archiveFilename": "macopt_notary_payload.mZls1y",
      "uploadDate": "2026-04-05T07:13:18.139Z",
      "sha256": "9983acb8591746d8d2ff63c213c96625627a5bbed53688b0e32e5c358f73928e",
      "ticketContents": null,
      "issues": null
    },
    {
      "logFormatVersion": 1,
      "jobId": "375408f2-3c0a-455e-88a1-9cd08ce7dc35",
      "status": "Rejected",
      "statusSummary": "Team is not yet configured for notarization. Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.",
      "statusCode": 7000,
      "archiveFilename": "macopt_notary_payload.CvrZNt",
      "uploadDate": "2026-04-04T20:07:51.080Z",
      "sha256": "e9b9f863e6e43ab86815988984e8e6fe8b89365bac9b60554277b4ee7db54222",
      "ticketContents": null,
      "issues": null
    },
    {
      "logFormatVersion": 1,
      "jobId": "dad888b3-6aff-4c54-9608-da1f86e44db7",
      "status": "Rejected",
      "statusSummary": "Team is not yet configured for notarization. Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.",
      "statusCode": 7000,
      "archiveFilename": "macopt_notary_payload.IH0RDr",
      "uploadDate": "2026-04-04T17:10:02.201Z",
      "sha256": "2097bab6015442f6904d9539441966d99557f90a5ef0a351a75e1dd7108d8e8f",
      "ticketContents": null,
      "issues": null
    },
    {
      "logFormatVersion": 1,
      "jobId": "9e129b21-e682-48ce-baa7-8d2d77051bac",
      "status": "Rejected",
      "statusSummary": "Team is not yet configured for notarization. Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.",
      "statusCode": 7000,
      "archiveFilename": "macopt_notary_payload.GsrSa6",
      "uploadDate": "2026-04-04T16:28:17.905Z",
      "sha256": "70076eccf72b835bcabe9b7a76d9b66804b5d0eec9425b5bedc56065577af7e1",
      "ticketContents": null,
      "issues": null
    }

OK, so there’s two parts to this:

• Why the delay?
• What to do about the Team is not yet configured for notarization failure?

The second part is the one that matters, but lemme quickly touch on the first. I have a standard spiel about this, which I’ve included at the end of this post, just as an FYI.

Regarding the second part, this isn’t something we can help you with here on the forums. Rather, you need to seek help via official channels. For the details, see this post.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays.

For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive.

Hi Quinn,

Thanks for the clarification, I appreciate it.

I understand that some submissions can be delayed due to deeper analysis. That said, many developers are still reporting notarization issues right now (including 403 errors reported this morning on the forums), so there may be a broader service-side issue.

I have already opened a support case through Apple Developer Support earlier this morning, as requested by the JSON response (“Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.”), and I’m now following that official path and waiting for the answer now.

Thanks again for your guidance.

I have already opened a support case

Cool.

many developers are still reporting notarization issues right now

Honestly, this is about normal, with the vast majority being the “in-depth analysis” issue.

including 403 errors reported this morning on the forums

Yeah, I’ve seen a few of those. They are definitely unrelated to your issue. Rather, they’re tied to the Apple Developer Program License Agreement. I usually see a cluster of those every time we update the agreement, which is something we did recently (2026-03-31). These usually have an obvious cause — the developer simply failed to agree to the new agreement — but every now and again I see something unexpected. However, the symptoms are very specific, and certainly not a sign of wider issues with the notary service.

While the notary service is quite reliable, it does occasionally have problems, and when that happens the signal here on the forums is very clear |-:

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi Quinn,

Thanks for your reply.

I understand the possibility of “in-depth analysis”, but based on the behavior I’m observing, this doesn’t seem to fully explain the situation.

Here is the full sequence of events:

• For over a month, notarization has been working consistently (20+ submissions), typically completing within a minute.
• On April 4th (morning), submissions were still accepted without any issue.
• Later that same day, submissions started getting stuck in “In Progress” for extended periods.

At that point, I waited for those “In Progress” submissions to complete.

• After some time, those submissions were eventually returned as Rejected with the error: "Team is not yet configured for notarization."

• I then retried new submissions, and on April 8th, they were suddenly Accepted again, without any change on my side.

• However, later that same day, new submissions were again Rejected with the same error.

• And today (April 9th), new submissions are once again stuck in "In Progress" (since around 9 AM).

So the pattern is: In Progress → Rejected → Accepted → Rejected → In Progress

No changes were made to:

• Team configuration
• certificates or signing setup
• notarization workflow
• or submission volume

Given this inconsistent behavior, it does not seem to match a typical “in-depth analysis” scenario, but rather something intermittent or unstable.

Additionally, multiple developers are currently reporting similar issues (including intermittent failures and long “In Progress” states), which suggests this may not be isolated.

Could you confirm whether there are any ongoing issues affecting notarization or team configuration on Apple’s side?

This is currently blocking releases, and the behavior is difficult to predict.

Thanks again for your help.