Repository navigation
Fix microphone startup and dictation permissions - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dictation could terminate the app when its Bluetooth input fallback switched to the built-in microphone. The user's crash log shows a 16 kHz tap against 48 kHz hardware. Capture now reads the current input hardware format and converts AVAudioEngine setup exceptions to recoverable errors through a small Objective-C bridge, retaining macOS 14 support.
Settings, Dictation exposes missing Input Monitoring permission. The shortcut monitor retries on app activation and stops if permission was revoked. The unpublished local 2.6.1 build 12 includes the previously merged note naming and M4A changes and is installed in Applications.
Validation:
Physical shortcuts, cross-app insertion and a live Bluetooth switch remain unverified. The local test copy and installed app lack Input Monitoring and Accessibility. The user deferred public release publication; the verified DMG and unsigned ZIP stay local. The original Sparkle key is on the user's older Mac and was not transferred. Packaging now explains a missing key instead of exiting silently. The existing public key and feed configuration are unchanged.