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.
Topic:
Code Signing
SubTopic:
Notarization