No Plover Steno Output to External Text Applications on MacOS Ventura, but Outputs to Paper Tape

[roobdj]

Steno output does not appear in text applications (Notes, Terminal, etc), when running Plover 4.0.0rc2 on MacOS 13.7.1 with Nolltronics Multisteno keyboard.

The same keyboard works perfectly in QWERTY mode, bypassing Plover. When Plover is launched via command line through Terminal, translated steno output works correctly to, e.g., Notes application. The issue seems to be MacOS Accessibility.

This may be related to #1642 and #1134, but no suggested solutions applied.

Steps taken

1. Verified keyboard (Nolltronics Multisteno) works in QWERTY mode in text applications
2. Confirmed Plover receives keyboard input (visible in paper tape)
3. Output set to “Enabled.”
4. Granted Plover permissions in System Settings > Privacy & Security > Accessibility
5. Granted Plover permissions in System Settings > Privacy & Security > Input Monitoring
6. Performed complete uninstall/reinstall:
   • Removed Plover.app
   • Deleted ~/Library/Application Support/plover
   • Deleted ~/Library/Preferences/org.openstenoproject.plover.plist
   • Restarted system from cold
   • Fresh install with new permissions
7. Discovered working solution: Launching Plover through Terminal using:

/Applications/Plover.app/Contents/Frameworks/Python.framework/Versions/Current/bin/python -m plover.scripts.main --gui qt

Expected behavior

Plover should output steno translations to external text applications when launched normally through Plover.app, just as it does when launched via Terminal.

Operating system

• OS: MacOS 13.7.1
• Plover Version: 4.0.0rc2+6.g53c416f

Hardware

• iMac Retina 4K, 21.5-inch, 2017
• Keyboard: Nolltronics Multisteno
• Connection: USB
• Machine Configuration: Gemini PR protocol
• All standard dictionaries present and working (user.json, commands.json, main.json)

Additional Context

The issue appears to be related to permission inheritance and how MacOS handles input access for the bundled Python framework (Python 3.9.7) within Plover.app. When launched directly through Terminal, the Python framework appears to receive proper input permissions, but this same permission chain doesn't work when launching through Plover.app.

Attempted workarounds including creating an AppleScript launcher also failed to resolve the permission inheritance issue. Currently using the Terminal launch command as a temporary solution.