Macros Broken by KM 9.0.1 Update

Questions & Suggestions
1

Continuing the discussion from Is there an alternative solution to short pauses between Selecting and Copying?:

@Rob,

Could you please upload an example of each type of Macro that you believe is broken by KM 9.0.1, and provide details about exactly what is broken.

For example, what is now different about the execution of these "broken" macros:

  1. Won't trigger
  2. Get error message/notification (post screen shot)
  3. Provide wrong answer
  4. other?

Also for each "broken" macro, you may want to try the interactive Assistant.

For more help, see Troubleshooting Problems with KM Macros.

2

I have a real outlier situation that I think broke, or else I was using it wrong.

For a long time GIMP has had a problem with KM's clipboard manager. (It's a GIMP bug, not KM's fault.) So I have a macro that turns off the clipboard manager when GIMP starts, and turns it back on when GIMP quits.

Here's how I turned it off:

image

I'm sure I got this from Peter at some point in time, because, I mean, how else would I know it?

Anyway, with version 9, this actually caused KM to never see anything copied to the clipboard. The clipboard worked for everything else, just not within a KM macro. And fortunately I realized this only happened when GIMP was running.

So I did what I think is the obvious thing, and changed the 0 to 1:

image

This solved the problem. So I don't know if I was using it wrong before, or what, but, well, there it is.

I can't imagine anyone else encountering this problem, but if they do, then at least it's documented somewhere.

3

Dan, I don't know the nature of the issue with GIMP, but have you tried just adding it to the Clipboard History Ignored App list in KM Editor > Preferences > Excluded

image

4

Nope, I never saw that! I'll give it a try and see if it works. The issue has gotten less frequent with the latest version of GIMP, so I don't know how long it'll take to see if it works. But I'll set it up right now.

Thanks!!

1 Like
5

The macros to log in into Apps using data from 1Password fail.

They worked on 9.0 with several 0.2s pauses, but that no longer seems to work properly on 9.0.1. Sometimes the copy action is done too early (as a result copying the credentials from the first item in 1Password instead of the first search result) and sometimes too late (as a result a wrong value in a variable).

I'm experimenting with the clipboard change detection and image detection to make it more robust.

EDIT: Also the engine is using 100% of the CPU a lot of the time...

EDIT2: Image detection and/or clipboard detection is even more unstable than the 0.2s delay I used previously. Using a 0.5s delay instead seems to work fine so far... Rather disappointing, since I would prefer checking for a desired outcome above using a random delay

6

Can you post one of your 1PW macros, changing any sensitive information.
In order to debug and fix, we need to be able to reproduce the behavior you are seeing.

7

This is a part of my flow that does not work robust enough without the pauses:

search

Instead of the wait I was trying for the text "Search results" (as an image) to appear.

username

Instead of the last wait I was trying to wait for clipboard changes.

Unexpected behaviour with those checks (instead of "random" waits) is in my previous post.

8

Hi @rob, the problem should be the URL :thinking:
The support at Agilebites know about the problem and some of them have already commented on it in the 1P forum.
Unfortunately they haven't got it fixed for months.

I had the problem that the locked 1Password Mini hangs when using the URL.
If it was unlocked, it worked fine with the URL, too.

In this article I will show you my changes:

In my macro (video) I set the pauses to 0.8, but meanwhile I replaced them with pauses of 0.2 and it also works smoothly.

9

I'm not sure we have the same problem; I only run the macro right after I typed my master password in 1Password.

10

Sure. The Open URL will ask 1Password to do something, and it will do it in its own time, so a pause may be needed after that.

And after simulating the ⌃⌘C, then you need to pause until the clipboard changes (as described elsewhere, as done by the Copy action, but that only works with ⌘C).

So those delays would be expected to be necessary.

11

I understand that pauses -or something better- are needed.

I thought detecting an image/text in 1Password and a password change would be more robust, but I can't get those to work properly, while the pauses seem to work.