TEXTSWITCHER v1.2.0DIAGNOSTICS :: STATUS OK

[ DIAGNOSTICS ]

> Troubleshooting

Each section below follows the same shape: the symptom you see, the causes that actually produce it, and the exact steps to take in order. Work through the actions from the top — they are ordered from most to least likely.

> TextSwitcher does not correct anything

symptom: You type ghbdtn followed by a space in any app and the text stays as ghbdtn. No flicker, no layout switch.

likely cause

  • Accessibility permission was never granted, so the app cannot read or replace text.
  • The app is not actually running — the menu-bar icon is missing after a restart.
  • Only one input source is installed, so there is no layout to switch to.

what to do

  1. Look at the menu bar. No TextSwitcher icon means it is not running: open it from /Applications and, in its menu, enable “Launch at login”.
  2. Open System Settings → Privacy & Security → Accessibility and confirm TextSwitcher is listed and switched on.
  3. Quit TextSwitcher from the menu-bar icon and open it again — permission granted while it was running is only picked up on the next launch.
  4. Open System Settings → Keyboard → Input Sources → Edit and confirm both an English (QWERTY) and a Russian (ЙЦУКЕН) source are present.
  5. Test in TextEdit: type ghbdtn then press space. TextEdit is a plain native field and rules out an app-specific issue.

> Accessibility is enabled but correction still fails

symptom: The switch next to TextSwitcher is on, yet nothing is corrected even in TextEdit.

likely cause

  • macOS is holding a stale permission entry for a previous copy of the app — very common after replacing the app with a new DMG or an ad-hoc-signed build.
  • Two copies of TextSwitcher exist (for example one in ~/Downloads and one in /Applications) and permission belongs to the other one.
  • The permission database is confused after an in-place upgrade.

what to do

  1. Quit TextSwitcher completely from its menu-bar icon.
  2. In System Settings → Privacy & Security → Accessibility, select TextSwitcher and press the minus (−) button to remove the entry entirely — switching it off is not enough.
  3. Delete every copy of the app except the one in /Applications, then empty the Trash.
  4. Launch the app from /Applications and press Add or Allow when macOS asks again; confirm the new entry appears and is on.
  5. If a permission prompt never appears, drag the app out of /Applications and back in, then launch it once more.
  6. Restart the Mac if the entry still refuses to take effect — this clears the cached permission state.

> Correction works elsewhere but not in Chrome

symptom: Slack and TextEdit are corrected, while Chrome fields — including ChatGPT, Lovable, or Asana comments — keep the gibberish.

likely cause

  • Chrome support is a separate toggle and is off.
  • Chrome was not restarted after the toggle was enabled, so its existing windows never picked it up.
  • The field is a secure field, or the site moved focus into a canvas-based editor that exposes no editable text.
  • You are using a different browser (Arc, Brave, Edge, Firefox), which is untested.

what to do

  1. Open TextSwitcher Settings and enable Chrome support, then quit Chrome entirely (⌘Q, not just closing the window) and reopen it.
  2. Confirm you are on TextSwitcher 1.2.0 or newer — earlier builds handled Chromium rich-text editors less reliably.
  3. Test in a plain field first, such as the Google search box, before testing a rich-text editor.
  4. In a rich-text editor, finish the word with a space rather than clicking away — a click does not complete the word.
  5. If it fails only on one site, note the URL and report it; per-site editor behaviour is the usual culprit.

> Correction happens late or feels sluggish

symptom: The word is fixed a moment after you have already typed the next one, or the layout switches behind your typing.

likely cause

  • Correction is intentionally deferred to the word boundary — space, punctuation, or Return — so fast typists can be a word ahead.
  • The target app is busy rendering, which delays the Accessibility response.
  • A different automation or text-expansion utility is contending for the same events.

what to do

  1. Type a space and pause briefly at the end of a mistyped word instead of continuing straight into the next one.
  2. Check whether the delay only occurs in one heavy app (a large document, a busy web page); if so it is that app's redraw, not the correction.
  3. Temporarily quit other keyboard utilities — text expanders, clipboard managers, remappers — and retest.
  4. If corrections are consistently more than a second late in plain fields, that is a bug worth reporting with the app name.

> macOS refuses to open the downloaded app

symptom: “TextSwitcher can’t be opened because it is from an unidentified developer”, or the app bounces once and quits.

likely cause

  • Gatekeeper treats apps distributed outside the Mac App Store more strictly on first launch.
  • The DMG was still mounted, and the app was launched from the disk image instead of /Applications.

what to do

  1. Drag TextSwitcher into /Applications, eject the DMG, and launch it from there.
  2. If the warning appears, right-click (or Control-click) the app and choose Open, then confirm — this only needs doing once.
  3. Alternatively open System Settings → Privacy & Security and press “Open Anyway” in the security section right after the failed attempt.
  4. Re-download the DMG if the file was interrupted or copied through a service that may have altered it.

> How to report a bug

Almost every unfixable report is missing the same details. Email support@antari.io with:

  1. Your macOS version (Apple menu → About This Mac) and Mac model.
  2. The TextSwitcher version (currently 1.2.0).
  3. The app and the specific field — for example “Asana comment box in Chrome”.
  4. The exact characters you typed and what appeared instead.
  5. Whether the same text is corrected in TextEdit, which separates an app-specific issue from a general one.
  6. Whether Chrome support is enabled, if the problem is in a browser.

Still on an older build? Reinstall the current one first — download TextSwitcher 1.2.0 — then confirm the problem persists. Behaviour limits that are expected are listed under supported apps and known limitations.