Skip to main content

​
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.

​
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: The app is not yet signed by Apple, so automatic updates are off. Install the new release manually from the download page and grant Accessibility permission again.
  • 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.

​
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.

​
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.