INSTALLATION · MACOS PERMISSIONS

Install Lemvia and Fix macOS Permissions

Install one copy of Lemvia in Applications, launch that installed copy, and grant only the macOS permission required by the workflow you invoke. Accessibility supports selected text and replacement, Input Monitoring supports the global shortcut, and Screen Recording supports the OCR region you frame.

Current releaseLemvia 1.1.7 build 10
Supported systemmacOS 13 or later
DistributionDeveloper ID signed and Apple-notarized
Supportsupport@lemvia.app

THE SHORTEST RELIABLE PATH

Follow the state in order.

  1. Move Lemvia to Applications

    Open Lemvia-1.1.7.dmg, drag Lemvia into Applications, eject the disk image, and launch the installed copy.

  2. Invoke the feature once

    Use selection, the global shortcut, or OCR so Lemvia can explain the exact permission needed for that action.

  3. Review Privacy & Security

    Open System Settings → Privacy & Security, enable Lemvia in the relevant category, then quit and reopen Lemvia.

  4. Remove duplicate copies

    If macOS keeps asking, delete or archive copies outside Applications and authorize the single installed copy again.

Why one installed copy matters

macOS privacy decisions are associated with an application identity and its installed state. Launching one copy from a mounted disk image and another from Applications can produce two permission records that look identical to a person but are not the same entry to macOS.

Lemvia does not bypass this system. The reliable recovery path is to keep the signed copy in Applications, remove duplicates, reopen that copy, and review the current status inside Lemvia Settings. The website cannot inspect or change permissions on your Mac.

What each permission enables

Accessibility lets Lemvia read a selected text range and replace only that range after translation. Input Monitoring lets the app detect the global shortcut while another app is active. Screen Recording lets OCR capture only the region you draw on screen.

Apple places these controls in Privacy & Security so the user can allow or revoke access. If a permission is disabled, the corresponding Lemvia workflow should explain the missing access and provide a route to System Settings instead of pretending the feature succeeded.

Direct answers

Why does Screen Recording appear again?

The permission may belong to another Lemvia copy. Keep the signed copy in Applications, remove duplicates, and authorize the installed copy.

Does Screen Recording send the whole screen?

Lemvia uses the permission to capture the region you frame for OCR. The selected translation route receives extracted text, not a continuous full-screen recording.

What should I send to support?

Send the macOS version, Lemvia version, affected app, steps, and a redacted screenshot. Never send an API key, password, full card number, or private source text.

PRIMARY SOURCES

Verify the underlying behavior.

The current answer should always point back to verifiable state.

View all guides