FixesMac6 min read
Accessibility permission not working after update Mac: fix
Accessibility permission not working after update Mac? The grant follows the code signature. Remove and add the app, or run tccutil reset Accessibility.
Published by Optimal Apps, the maker of Petal.
On this page
Accessibility permission not working after update? On a Mac, the cause is usually the app's code signature. macOS ties each Accessibility grant to the signature of the app that received it. When an update, a rebuild from source, or a wrongly signed release changes the signature, the old grant stops applying. System Settings can still show the switch as on. To fix it, remove the app from System Settings > Privacy & Security > Accessibility with the minus button and add it again, or run tccutil reset Accessibility <bundle ID> and grant access again.
This problem hits dictation apps hard, because they need Accessibility to paste. The steps use macOS Tahoe 26 names.
Accessibility permission not working after update: Mac quick-fix checklist
| What you see | Likely cause | Fix |
|---|---|---|
| Switch is on, app says it has no access | Grant belongs to an old signature | Remove with -, reopen the app, add again |
| Toggling the switch off and on does nothing | Stale entry for the old signature | tccutil reset Accessibility <bundle ID> |
| Started after you built the app from source | Local builds have a different signature | Reset with tccutil after each rebuild |
| Started after one specific update | That build was signed wrongly | Install a fresh, correctly signed copy |
| App is not in the list at all | App has not asked, or it runs from a DMG | Move it to /Applications, open it, add it with + |
| Transcript appears, but no paste | Accessibility missing, focus lost | Fix the grant, click the field first |
Why the grant breaks: code signatures
Every Mac app has a code signature. It proves who built the app and that nobody changed it. macOS stores privacy grants, such as Accessibility, Screen Recording, and Microphone, with that signature.
When the signature changes, macOS sees a different app. The common reasons:
- A rebuild from source. A developer or user builds the app with their own certificate, or without one. GitHub issue #530 on the VoiceInk repository explains that Accessibility and Screen Recording grants stop working after a rebuild for this reason.
- A wrongly signed release. Willow Voice documented that a v1.8.4 build was published with an incorrect signature for about one day. macOS then re-asked for Accessibility and Input Monitoring and treated the update as a new app.
- A change of signing identity. If a developer moves to a new team or certificate, all users must grant access again once.
Normal updates from the same developer, signed with the same Developer ID, keep the grant.
Step 1: Remove the app and add it again
This fixes most cases and does not need Terminal.
- Quit the app. For a menu bar app, use the Quit item in its menu.
- Open Apple menu > System Settings > Privacy & Security > Accessibility.
- Select the app in the list.
- Click the minus (-) button below the list. Enter your password if macOS asks.
- Open the app again. It asks for Accessibility, or it opens System Settings.
- If the app does not appear in the list, click the plus (+) button, choose the app in /Applications, and click Open.
- Turn the app's switch on.
- Quit and reopen the app, then test.
Willow Voice's help article for v1.8.4 gives the same order: remove it with "–", restart the app, turn access on again when it appears, and restart again.
Step 2: Reset Accessibility with tccutil
If Step 1 does not work, reset the entry from Terminal.
- Find the bundle ID of the app:
osascript -e 'id of app "VoiceInk"'
- Quit the app.
- Reset its Accessibility entry:
tccutil reset Accessibility com.prakashjoshipax.VoiceInk
- Open the app and grant Accessibility again.
- If the app also uses Screen Recording, reset that too:
tccutil reset ScreenCapture com.prakashjoshipax.VoiceInk
Replace the bundle ID with the one from step 1. Always add a bundle ID. Without one, tccutil reset Accessibility removes Accessibility for every app on the Mac.
Step 3: Install a fresh copy if one build was signed wrongly
If the problem started with one update and the developer reports a signing problem:
- Download the current version from the developer's website.
- Delete the app from /Applications.
- Install the fresh copy in /Applications.
- Repeat Step 1 or Step 2.
Step 4: Run the app from /Applications
An app that runs from a mounted disk image, from Downloads, or from a quarantined folder can get a temporary location. macOS can then fail to match the grant.
- Drag the app into /Applications.
- Eject the disk image.
- Delete other copies.
- Open the app from /Applications and grant access.
Step 5: Check the paste itself
When Accessibility is correct, a dictation app can still fail to paste if the text field loses focus or the app reads the clipboard late. Fix those separately:
- Click in the field before you dictate, and stay there until the text appears.
- For Electron apps and terminals, read Dictation not pasting into VS Code, Terminal, or Claude Code.
- For Wispr Flow, read Wispr Flow not pasting.
- For Willow Voice, read Willow Voice not working.
How to check that the grant applies
The switch in System Settings does not prove that the grant applies. Test the real behavior:
- Open TextEdit and create a new document.
- Click in the document.
- Dictate one short sentence with the app.
- If the text appears, the grant works. If the app shows a transcript but TextEdit stays empty, the grant does not apply.
Many dictation apps also show their own permission status in their settings. When the app says that it has no Accessibility access but System Settings shows the switch as on, you have a stale entry. Go back to Step 1 or Step 2.
Why macOS ties the grant to the signature
Accessibility access is powerful. An app with it can read other windows and send keystrokes to any app. If macOS kept the grant by app name only, a changed or harmful copy with the same name could use it. The signature check stops that, so the cost is one more permission prompt when the signature changes.
For people who build an app from source
If you build an open-source dictation app yourself, sign each build with the same certificate. A free Apple Development certificate in Xcode works for this. With the same signing identity, the grant survives rebuilds. With an ad-hoc or changed signature, you must reset the grant after every build.
Microphone permission follows the same rule
The microphone grant also follows the signature. If a dictation app stops hearing you after an update, use the same reset with Microphone in place of Accessibility. The full steps are in Mac app microphone permission not working.
How Petal handles Accessibility
Petal for macOS is a free, open-source dictation app. It needs Accessibility for the same reason as other dictation apps: it sends Command-V to paste the transcript.
What Petal does to keep the grant valid and to avoid lost text:
- Stable signature. Petal ships through GitHub Releases, with Sparkle updates and a Developer ID signature. Each update keeps the same signature, so the grant stays valid.
- Stale entry cleanup. When Petal asks for Accessibility and does not have it, it first removes its own old entry (
tccutil reset Accessibility com.optimalapps.petal). The next prompt then adds an entry for the current signature. This fixes the "switch is on but nothing works" case without Terminal. - A guide window. Petal opens the Accessibility pane and shows a small window: "Drag the app below into the list above, then turn it on."
- Copy fallback. If Petal cannot paste, it copies the transcript to the clipboard and tells you that Accessibility access is needed. The text is not lost.
To turn it on, open Petal's Settings > General. If Accessibility is missing, an Accessibility row appears with an Enable button.
Questions
Why does an app lose Accessibility permission after an update on Mac?
macOS ties the Accessibility grant to the app's code signature. If an update, a rebuild, or a wrongly signed build has a different signature, macOS treats it as a new app. The old entry can still show as on, but it does not apply.
The Accessibility switch is on, but the app still cannot paste. What do I do?
Select the app in Privacy & Security > Accessibility and click the minus (-) button to remove it. Quit and reopen the app, then add it again and turn it on. If that does not help, run tccutil reset Accessibility with the app's bundle ID.
How do I reset Accessibility for one app?
Quit the app and run tccutil reset Accessibility followed by the bundle ID in Terminal, for example tccutil reset Accessibility com.prakashjoshipax.VoiceInk. Open the app and grant access again when it asks.
Why does my dictation app need Accessibility?
Dictation apps paste text by sending a Command-V keystroke to the app you use. macOS allows an app to send keystrokes to other apps only with Accessibility access.