As the title says, I click the shortcut created with the fuction “Add shortcut to bookmarks bar” and then the UI.Vision dialog pops up. Then it waits for about 11 seconds before starting execution.
Everyone: The challenge for us is to recreate the issue. All works fine on our test systems, as shown in the video above. Once we find a way to recreate the issue, we can debug and fix it. So any hints on why and when this bug happens are welcome.
I’ve tested some more. In firefox everything works fine, however for my work it needs to work on Chrome.
When I test on another pc (win10 EN) with chrome it also has the delay. So that’s two devices where the same issue is happening in chrome
I’ve profiled in the developer tools and although I can’t profile from the start (it takes some time to press F12 and Ctrl+e) I do have a chrome profile log which might help: WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free In that profile the script is started around 8000ms
Furthermore you can see below in the profiler screenshot that every 1 second some task gets executed and then waits for a second again. So I’m guessing that there’s some code that checks something every second, and if it’s not ok yet it waits for a second. This 10 times it seems.
The delay always happen no matter what site is open. Except in a new tab it does nothing.
I’ve tested with other commands as well, same delay.
Another observation was made as I was testing with two bookmark shortcuts. When I alternate the shortcuts, then I see that the wait period is before loading the requested makro.
eg.
I play Makro A from bookmarks forlder
Next I play Makro B from bookmarks folder → Gui pops us and during the first 10 seconds I still see Makro A and only then Makro B is loaded.
This seems to happen when you don’t have XModules installed. The easiest way to fix this is to simply install them.
However, if you can’t install this or don’t want to then you can bypass it by editing src\services\filesystem\index.ts
prev[camel] = (() => {
const fn = (params: any) => pReady.then(() => {
pendingRequestCount += 1
return nativeHost.invokeAsync(method, params)
})
.then(
(data) => {
pendingRequestCount -= 1
return data
},
e => {
// *** Change this line here ***
pendingRequestCount = 0
// Note: Looks like for now whenever there is an error, you have to reconnect native host
// otherwise, all commands return "Disconnected" afterwards
const typeSafeAPI = <NativeFileAPI>(<any>api)
typeSafeAPI.reconnect().catch(() => {})
throw e
}
)
return fn
})()
@admin Hopefully this gives you a place to debug from. When it fails with XModules not installed, it returns this error:
Error: Specified native messaging host not found.
at index.ts:134:1
at KantuFileAccessHost.processResponse (index.ts:60:1)
at KantuFileAccessHost.disconnect (index.ts:105:1)
at KantuFileAccessHost.handleDisconnect (index.ts:75:1)
Depending on how you want to handle these errors, I would have it return straight away if it doesn’t find the native messaging host. Other errors could continue making requests as it is now.
