Hi @Michal Turek ,
Send an email to AA Support team "apeopleopsteam@automationanywhere.com" to get the access.
Thanks @ChanduMohammad S
I've posted an e-mail to the address You've mentioned, but there's no response,
Could You please post a screenshot of the article please?:
https://apeople.automationanywhere.com/s/article/Upgrade-Chrome-and-Edge-Manifest-v3-from-Manifest-v2?_ga=2.245711820.998733119.1667803014-368026655.1641986793amp;_gl=1*k8edss*_ga*MzY4MDI2NjU1LjE2NDE5ODY3OTM.*_ga_DG1BTLENXK*MTY2NzgyMjkwMi4xMzUuMS4xNjY3ODIzNTU3LjM0LjAuMA..
Hi @Michal Turek
PFB details
We recommend that you upgrade to Automation 360 v.26 to switch from Manifest V2 extensions to Manifest V3 extensions for both Google Chrome and Microsoft Edge browsers. However, if you are using Automation 360 v.25 or earlier, you can perform this procedure on the Bot Agent devices to switch to the Manifest V3 extension manually, please click here for detailed steps.
Manifest v3 binaries for Chrome: Download
Manifest v3 binaries for Edge: Download
Additional Links- Overview of the Manifest v3 can be accessed here.
- Post upgrade to Automation 360 v.26 if you encounter any challenges with the recorder package, please follow the steps available in the article, to switch the Manifest v3 to v2 extension manually.
Hallo @ChanduMohammad S ,
I've got one more thing:
Is the old Chrome AA manifest v2 Plugin version (f.i. 1.7.0.0) to be removed?, because after the upgrade to Mv3 there are two plugins available simultanisly - old and new,
greetings,
MT
Hi @Michal Turek ,
Please remove the old extension.
Hallo,
as an addition to previous comments, I’ve got a one UA Bot Runner (version 21.134) on a VM with Windows Server 2019 Standard. The Control Room is v. 24 build 12350 on-Premise.
I’d conducted all steps necessary for a manual switching Manifest V2 to V3 Chrome extension (according to manual above), but despite that there’s still Manifest V2 (1.5.0.0) present in Chrome.
How to force switching to new extension.
Looking for clues,
thanks Michal