Notarization stuck "In Progress" — app uses audio, clipboard and accessibility APIs

Question

Created 4d

Replies 3

Boosts 0

Participants 3

Hi,

My first notarization submission has been stuck in "In Progress" for several hours with no status change. I'm wondering if it's being held for in-depth analysis given the nature of the app.

The app is a macOS dictation utility triggered by a global hotkey. It captures audio input, transcribes it, and pastes the result at the cursor position in whatever app the user is focused on.

Because of how it works, it relies on a combination of APIs that may be less common in typical submissions: continuous microphone access, programmatic clipboard manipulation, global keyboard event monitoring, and Accessibility APIs to inject text into the frontmost application.

This is the first submission for this app, so there's no prior notarization history for the system to learn from.

Is this the kind of profile that typically triggers in-depth analysis? Is there anything I should check or provide, or is waiting the right move here?

Thanks

Answered by DTS Engineer in 882185022

It was finally approved several hours later.

Cool.

This is not, in and of itself, unusual. I have a standard blurb that explains the most likely cause, which I’ve included below.

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.

Boost

Answer 1

mdtoledo OP

4d

It was finally approved several hours later.

0

Answer 2

eddiewangyw OP

2d

I have built a very similar macOS dictation tool — global hotkey, continuous mic capture, on-device transcription, then AX API text injection. My first notarization also took several hours, which is normal for this entitlement combination. Tips for future submissions: (1) Hardened Runtime with specific exceptions only — avoid blanket disable-library-validation. (2) Use Developer ID Application signing to prevent TCC permission resets. (3) After first successful notarization, subsequent submissions go through in minutes. The audio + clipboard + AX combo triggers deeper first-time analysis but is not a rejection risk. Glad yours went through.

0

Answer 3

DTS Engineer OP

Apple

2d

Recommended

It was finally approved several hours later.

Cool.

This is not, in and of itself, unusual. I have a standard blurb that explains the most likely cause, which I’ve included below.

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.

0