First-time corrected CtxVault notarization submissions stuck "In Progress" for 36+ hours

Hi,

I’m requesting investigation of two CtxVault notarization submissions that have remained "In Progress" well past 24 hours.

Team ID: DCY4ZS6CS6 App / archive: CtxVault.zip Platform: macOS direct distribution

Pending submissions:

  • e2f25e8c-8bf6-44e6-8e60-24b22467b7e6 — created 2026-04-22T12:50:04.988Z — still In Progress
  • 1f41ff2d-cf61-4509-beba-3389f4496ba7 — created 2026-04-22T12:40:23.167Z — still In Progress

Context:

  • This is a new Developer ID release path for a personal team.
  • Earlier submissions were Invalid due to unsigned nested Mach-O files inside a bundled Python runtime.
  • That issue was corrected before the two pending submissions above.
  • The current app is signed with Developer ID Application, hardened runtime, and secure timestamps.
  • Local validation passes:
    • codesign --verify --deep --strict
    • spctl assessment on the signed app
  • notarytool accepts the upload and returns submission IDs, but the submissions do not complete and no log is yet available.

Earlier invalid submission for context:

  • b4e665a0-98eb-4b92-b44c-58a0a2c6122e

Could someone from Apple please confirm whether this team is stuck in queue or under extended review, and whether any team-side provisioning or backend action is needed?

I am intentionally not creating more duplicate submissions while these corrected jobs remain pending.

Thanks.

First-time corrected CtxVault notarization submissions stuck "In Progress" for 36+ hours
 
 
Q