Jingbo
Jingbo
It always generates a new ID when importing packages (see [importPackage](https://github.com/AutomaApp/automa/blob/d8c16d5d2f89520a0d2ec63db336b8e6b35ffca4/src/newtab/pages/Packages.vue#L281) and [insert](https://github.com/AutomaApp/automa/blob/d8c16d5d2f89520a0d2ec63db336b8e6b35ffca4/src/stores/package.js#L49)). One workaround is to change `packageStore.insert(pkgJson);` to `packageStore.insert(pkgJson, false);` in `Packages.vue`, and then re-build and load it...
Yes, Automa can interact with the MetaMask extension by using MetaMask's Ethereum Provider (`window.ethereum`). MetaMask injects an Ethereum provider object into the window object of web pages. This object allows...
Automa uses `browser.alarms` (see [here](https://github.com/AutomaApp/automa/blob/d8c16d5d2f89520a0d2ec63db336b8e6b35ffca4/src/utils/workflowTrigger.js#L211-L213)) to create alarms. However, on Chrome, unless the extension is loaded unpackaged, the alarms it creates are not allowed to fire more than once per...
If it involves Loop Breakpoint, you might need a `loopId` to [access the loop data](https://docs.automa.site/workflow/looping.html#access-loop-item)
Actually, those aren't URLs but rather [Base64 strings](https://en.wikipedia.org/wiki/Base64) representing the image file. The length of a Base64 string is based on the size of the image file, so if it's...
The reason your script always waits for the page to fully load is because you're using `window.onload`. You can check out more details here: [MDN: Window Load Event](https://developer.mozilla.org/en-US/docs/Web/API/Window/load_event). Basically, the...
If you're executing the script as background script, I'd suggest adding a global `try-catch` block to print the error to the console. Then follow the [help doc](https://docs.automa.site/reference/javascript-execution-context.html#background) to find the...
I quickly checked how the script is executed ([see here](https://github.com/AutomaApp/automa/blob/d8c16d5d2f89520a0d2ec63db336b8e6b35ffca4/src/sandbox/utils/handleJavascriptBlock.js#L39-L72)). Seems like it's designed to execute custom scripts within the context of the current web page (via `document.createElement`). This means...
Might be caused by the double-awaiting -- `automaFetch` returns a promise, and you already await the result with `const result = await automaFetch(...)`, so `const res = await result;` is...