Skip to main content

​
Windows blocked the installer

Because Windows doesn’t recognize evoX yet, it may treat the installer as an unknown app. Depending on which warning you see:
  • Your browser stopped the download (a warning like “isn’t commonly downloaded”): open the menu next to the file in your downloads list and choose Keep / Keep anyway.
  • “Windows protected your PC”: click More info, then Run anyway.
  • “Smart App Control blocked an app”: this Windows 11 feature does not let you allow a single app. evoX cannot be installed while it is on. If you want to install it, you can turn it off in Settings → Privacy & security → Windows Security → App & browser control → Smart App Control settings.
Turning off Smart App Control lowers your PC’s overall protection, and on some Windows versions it cannot be turned back on without resetting Windows. Make that choice knowingly. Before turning it off, compare the SHA-256 digest of the file you downloaded with the value on the Download page, and only run a file that matches.

​
The device does not appear connected

  1. Check the USB cable.
  2. Check whether the official evoX app is holding the device.
  3. If shown, use the explicit takeover action.
  4. If you use Linux, you must have accepted the device permission prompt on first launch and then logged out and back in. If you skipped the prompt, you are not asked again in the same release; in that case write to us through Support.
  5. Verify physical key input again.

​
An action does not work

  • Verify that the action’s native runtime is ready and the action is assignable.
  • Complete the required pack settings via Plugins → Pack → Settings.
  • Check that the profile is active and on the correct page.
  • If the provider is missing, do not delete the binding; it can be resolved again when the pack comes back.

​
A key that came from a pack does not open anything

The Open File / App and Open Folder keys of a pack you installed arrive with no target: the program and folder paths inside the pack are cleared while it is being installed, and you decide what they open. Open the key’s settings and pick your own file, app or folder. Targets you pick yourself work as they always did.

​
The “evoX does not open … links” warning

The Website action only opens safe kinds of addresses: https, http, email (mailto:), Steam, Discord, and system settings / app pages (ms-settings:, x-apple.systempreferences:, microsoft.windows.camera:, ms-photos:). Addresses that could run a file on your computer, such as file: or shell:, are refused, and pressing the key tells you why. Leaving out the scheme is fine: example.com opens in the browser as https://example.com, and local addresses like localhost:3000 work too. If you want to open a local program or folder, use the Open File / App or Open Folder action instead of Website.

​
Shortcut and text actions do not work on macOS

If the device is connected and icons are drawn but the keys do nothing, the cause is almost always Accessibility permission.
  1. Verify that evoX is turned on in System Settings → Privacy & Security → Accessibility.
  2. If it appears on but still does not work, remove evoX from the list with −, add it again and restart the app. This step is especially needed after moving to a new release.
  3. Accept the automation approval that appears on the first use of keyboard and text actions.
  4. If the action says “This action is not supported on macOS” or “Coordinate clicks are only supported on Windows.”, it is not a permission problem: that action or that mode has no equivalent on macOS. You can find which actions are translated, which are not supported and which Mouse Event modes work on the Assign actions page. The same limit applies on Linux.

​
Updates are not arriving

  • Windows: Automatic updates work only for a version installed with the installer. Choose Check on the Settings → Update card.
  • macOS: Choose Check on the Settings → Update card. Unsigned releases 0.3.14 and earlier cannot update themselves: install the new release manually from the download page once and grant Accessibility permission again. Later updates arrive automatically.
  • Linux: Updates work when you run the app as an AppImage file and the folder containing the file is writable. If the AppImage is in a system directory such as /opt, move it to your own folder (for example ~/Applications). After an update the file name changes along with the version; refresh shortcuts tied to a fixed name.
If the Update card shows an error, the message tells you why. In every case the update is not downloaded and your installed version keeps running unchanged:
  • “Couldn’t download update info”: A connection problem. Check your internet connection, VPN/proxy settings or HTTPS-scanning antivirus, then choose Check.
  • “Update info is out of sync”: This can show briefly while a new release is being published. Choose Check again in a few minutes.
  • “Update signature could not be verified”: The downloaded update info could not be verified, so it is not installed for security. If it persists, install the new release from the download page and write to us through Support.

​
The deck is blank and the keys show nothing

If the Keys page shows Background is paused — the deck is off. above the device preview, evoX’s background runtime is paused and nothing is sent to the device. Press Resume on that strip; the deck redraws within a few seconds. You can also pause and resume the background from the tray menu (the menu bar on macOS).

​
An icon does not appear on the device

Verify the device connection, that the official app has not taken the device, and that the file is a supported PNG/JPG/GIF source. Save the assignment again and check physical synchronization.

​
The Market is offline

The app can show the last catalog cache-first. New installations or account operations may require a connection. The “Couldn’t connect to the Market server” message shows an error code in parentheses (for example ERR_CERT_AUTHORITY_INVALID). Check your internet connection, VPN/proxy settings or HTTPS-scanning antivirus and try again. If it persists, include that code when you write to Support.

​
An integration connection asks for reauthorization

Integration credentials are stored encrypted on your device, tied to your system user account: to your account on Windows, to Keychain on macOS, and to your system keyring (GNOME Keyring or KWallet) on Linux. If you reinstalled your system, moved to another computer or opened it with a different user account, these secret values cannot be decrypted for security. In that case Authorize the related integration again via Plugins → Pack → Settings; this is expected and safe behavior.
On Linux, if no keyring is running in your session, the Market session and integration credentials are not saved at all; you cannot sign in with Google. Install GNOME Keyring or KWallet and log in to your session again.
Do not paste tokens, secrets, raw paths or credentials into a support message. Raw identifiers and debug IPC details are not needed in normal user lists.