User Tools
Troubleshooting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
Troubleshooting [2021/11/01 21:00] peternlewis [Mojave and Later Security Preferences Issues] |
Troubleshooting [2023/10/11 00:08] (current) peternlewis |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| 1. Immediately after you have installed Keyboard Maestro on a specific Mac -- See [[#Situation_1_--_New_Install|Situation #1]]. | 1. Immediately after you have installed Keyboard Maestro on a specific Mac -- See [[#Situation_1_--_New_Install|Situation #1]]. | ||
| - | 2. Immediately after you have updated Keyboard Maestro to a new version -- See [[#Situation_2_--_After_Update_to_New_Version_of_Keyboard_Maestro|Situation #2]]. | + | 1. Immediately after you have update macOS -- See [[#Situation_2_--_System_Update|Situation #2]]. |
| - | 3. Keyboard Maestro’s behavior changes unexpectedly, and without apparent cause, some time (say a week or more) after it has been running as expected without any issues -- See [[#Situation_3_--_After_Working_Fine_for_a_While|Situation #3]]. | + | 1. Immediately after you have updated Keyboard Maestro to a new version -- See [[#Situation_3_--_After_Update_to_New_Version_of_Keyboard_Maestro|Situation #3]]. |
| - | 4. After you have created a new Macro, or added new Actions, that you have not used before -- See [[#Situation_4_--_After_New_Macros_or_Actions|Situation #4]]. | + | 1. Keyboard Maestro’s behavior changes unexpectedly, and without apparent cause, some time (say a week or more) after it has been running as expected without any issues -- See [[#Situation_4_--_After_Working_Fine_for_a_While|Situation #4]]. |
| + | 1. After you have created a new Macro, or added new Actions, that you have not used before -- See [[#Situation_5_--_After_New_Macros_or_Actions|Situation #5]]. | ||
| ===== General Troubleshooting ===== | ===== General Troubleshooting ===== | ||
| Line 42: | Line 43: | ||
| 1. To fix, see [How to Enable Google Chrome to Respond to KM Actions](https://forum.keyboardmaestro.com/t/announcement-google-chrome-68-disables-km-access-how-to-fix/10969) | 1. To fix, see [How to Enable Google Chrome to Respond to KM Actions](https://forum.keyboardmaestro.com/t/announcement-google-chrome-68-disables-km-access-how-to-fix/10969) | ||
| - | ==== Situation #2 -- After Update to New Version of Keyboard Maestro ==== | + | ==== Situation #2 -- After a System Update ==== |
| + | |||
| + | If Keyboard Maestro had been running fine, and then does not work as expected after upgrading macOS: | ||
| + | |||
| + | 1. Immediately after a system update, it is wise to Restart an additional time. Many times we have found the system to not be in a totally stable state after an update, and a Restart gives a clean fresh start. | ||
| + | 1. If lots of macros are failing, run the _Interactive Help Wizard_ from the Keyboard Maestro Editor Help menu and see if that helps. | ||
| + | 1. Check the Security preferences pane and verify that you have all the relevant security permissions. | ||
| + | 1. Keep in mind that after a system update (or any specific application update), your macro might break simply because things in the system or application have changed since the macro was created. See if the macro simply needs adjusting. | ||
| + | |||
| + | ==== Situation #3 -- After Update to New Version of Keyboard Maestro ==== | ||
| If Keyboard Maestro had been running fine, and then does not work as expected after an upgrade, then do the following: | If Keyboard Maestro had been running fine, and then does not work as expected after an upgrade, then do the following: | ||
| Line 54: | Line 64: | ||
| 1. Upload example Macro that produces the issue. | 1. Upload example Macro that produces the issue. | ||
| - | ==== Situation #3 -- After Working Fine for a While ==== | + | ==== Situation #4 -- After Working Fine for a While ==== |
| 1. If Keyboard Maestro has been working well, as expected, for a while (let's say a week or more), and then it suddenly behaves in an unexpected manner, then most likely that is due to something that has recently changed.\\ | 1. If Keyboard Maestro has been working well, as expected, for a while (let's say a week or more), and then it suddenly behaves in an unexpected manner, then most likely that is due to something that has recently changed.\\ | ||
| Line 70: | Line 80: | ||
| 1. If that does not help, then you can search (using the Browser Find menu) the below Keyboard Maestro specific issues to find one or more that relates to your situation. | 1. If that does not help, then you can search (using the Browser Find menu) the below Keyboard Maestro specific issues to find one or more that relates to your situation. | ||
| - | ==== Situation #4 -- After New Macros or Actions ==== | + | ==== Situation #5 -- After New Macros or Actions ==== |
| 1. The issue is most likely caused by improper use of the Action. | 1. The issue is most likely caused by improper use of the Action. | ||
| Line 157: | Line 167: | ||
| Often, adding pauses to your macro will solve the timing issues. A pause of 0.3 seconds is often enough, but in some cases (e.g. a [[action:Activate_a_Specific_Application|Activate a Specific Application]] action when there are many applications open and your system is running out of memory) longer pauses (several seconds) may be necessary. | Often, adding pauses to your macro will solve the timing issues. A pause of 0.3 seconds is often enough, but in some cases (e.g. a [[action:Activate_a_Specific_Application|Activate a Specific Application]] action when there are many applications open and your system is running out of memory) longer pauses (several seconds) may be necessary. | ||
| - | ===== Action Issues ===== | + | ===== Typing Issues ===== |
| ==== Sometimes Typing in Password Fields Drops Characters ==== | ==== Sometimes Typing in Password Fields Drops Characters ==== | ||
| Line 166: | Line 176: | ||
| This happens most commonly when you have a hot key trigger with the same key (eg Control-T) as a key you want to type in to a password field (eg "Hello there"). Because it is a password field, the only indication will be a missing bullet (•) (so ten instead of 11 bullets) and then an "invalid password" error, which makes this problem hard do diagnose. | This happens most commonly when you have a hot key trigger with the same key (eg Control-T) as a key you want to type in to a password field (eg "Hello there"). Because it is a password field, the only indication will be a missing bullet (•) (so ten instead of 11 bullets) and then an "invalid password" error, which makes this problem hard do diagnose. | ||
| + | |||
| + | ==== Sometimes Typing results in Characters Missing or out of Order ==== | ||
| + | |||
| + | This typically happens in web fields (especially Facebook) or cross platform apps. | ||
| + | |||
| + | The system has a queue for keyboard events, so they are sent by Keyboard Maestro in the correct order and then processed by the system in that order. The problems happen after that. | ||
| + | |||
| + | Typically you see this in fields where the app is processing the field. Essentially the app reads the field, does some processing or checking and then writes the field back, and the typing happens fast enough (as could keyboard typing if you could type fast enough) that changes happen while the field is being read/written and so characters are jumbled or lost. | ||
| + | |||
| + | You can slow the typing down by using Set Action Delay action (https://wiki.keyboardmaestro.com/action/Set_Action_Delay) to increase the delay for normal typing. Only do it for the current macro (not permanently) since this issue is relatively rare, and generally only applies to certain apps or fields. | ||
| + | |||
| + | ==== Everything is lowercase in remote desktops/virtual machines ==== | ||
| + | |||
| + | Yes, unfortunately these types of environments seem to miss the shift key and the consequential uppercasing of lettings and symbols. | ||
| ===== Clipboard Issues ===== | ===== Clipboard Issues ===== | ||
| Line 438: | Line 462: | ||
| In Parallels, make sure the ”Enabled Mac OS X system shortcuts” preference is enabled, which will ensure Parallels reads the keyboard from the keyboard queue. | In Parallels, make sure the ”Enabled Mac OS X system shortcuts” preference is enabled, which will ensure Parallels reads the keyboard from the keyboard queue. | ||
| - | |||
| - | |||
| ===== Other Issues ===== | ===== Other Issues ===== | ||
Troubleshooting.1635814804.txt.gz · Last modified: 2021/11/01 21:00 by peternlewis
Page Tools
