You guys pushed a broken version overnight - 10.0.281 is missing a comma an prevent execution of all my scripts.
I have been a fervent user of UI vision from back when you were kantu but I honestly cannot wake up with my whole fleet broken because of a typo. My process auto updates for your macro based on your official latest version and all my fleet migrated to 10.0.281 then all started failing overnight.
As a dev myself, this is a type of error I would expect an AI code review to catch (it took Claude 1 minute to find the problem) yet the impact is high on my side. This is the second time I have had to raise a breaking issue and I am considering migrating away from ui vision to avoid a costly downtime on my work.
Not bashing. I do love what you have done. I would just rather work with you and your tool rather than around you and your tool. Fix should be straightforward but beyond that I would be open to help in any way as well, giving back for how helpful your tool has been to me over the years would feel right too if that was an option?
AI explanation breakdown
In 10.0.281 content_script.js, the new RunMacro alias is missing a comma:
(0,u.bind)(window,“kantuRunMacro”,c)(r?u.bindOnce:u.subjectiveBindOnce)(window,“kantuSaveAndRunMacro”,…)
bind returns undefined, so the content script throws a TypeError at this point and kantuSaveAndRunMacro is never registered.
Any HTML launcher that fires kantuSaveAndRunMacro (the file generated by “Create autorun HTML”) gets no kantuInvokeSuccess. After 8 seconds it shows “Error #203: It seems you need to turn on Allow access to file URLs”, although that permission is on.
10.0.278 works. The fix is a comma after (0,u.bind)(window,“kantuRunMacro”,c).