PerditionC
VBAChromeDevProtocol - cdpaddin.xlam worked with Edge but not with Chrome
The Chrome version 137.0.7151.104 (64-bit) is running into issues with CDP (Chrome DevTools Protocol) — including timeouts and/or no target detection — it's very likely that this version is no longer compatible with the CDP communication pattern used in VBA tooling.
Anyone has the same issue?
I will try to test and see if I see same issue and if so if its possible to fix.
I will try to get an update out in next day or so. Chrome does no longer work as is. It seems Chrome no longer allows using the remote debug interface using the default profile, so --user-data-dir argument must be passed with a corresponding directory when starting Chrome. However, the first time (when this profile does not yet exist, so it generates it), it fails to recognize it has attached as it fails to find the initially loaded site url. Edge does still work fine without the argument, at least for now. I will try to find some time to see about using the websocket interface [I though I had an implementation of it here, though it had issues as it was blocking -- but it should be more reliable with a non-blocking (reads return immediately if no data so VBA/Excel doesn't get hung) websocket usage.]
To Avoid Interference with the Regular Chrome Profile (default). Should use a custom user data directory like --user-data-dir="C:\Temp\CDPProfile" when launching Chrome with --remote-debugging-pipe to isolate the automated browser session from your default Chrome profile. Example: browser.Launch _ Url:="https://google.com", _ whichBrowser:= chrome, _ userDataDir:="C:\Temp_User_Data"
On Wed, Jul 9, 2025 at 9:40 PM Kenneth J Davis @.***> wrote:
PerditionC left a comment (PerditionC/VBAChromeDevProtocol#17) https://github.com/PerditionC/VBAChromeDevProtocol/issues/17#issuecomment-3054908249
I will try to get an update out in next day or so. Chrome does no longer work as is. It seems Chrome no longer allows using the remote debug interface using the default profile, so --user-data-dir argument must be passed with a corresponding directory when starting Chrome. However, the first time (when this profile does not yet exist, so it generates it), it fails to recognize it has attached as it fails to find the initially loaded site url. Edge does still work fine without the argument, at least for now. I will try to find some time to see about using the websocket interface [I though I had an implementation of it here, though it had issues as it was blocking -- but it should be more reliable with a non-blocking (reads return immediately if no data so VBA/Excel doesn't get hung) websocket usage.]
— Reply to this email directly, view it on GitHub https://github.com/PerditionC/VBAChromeDevProtocol/issues/17#issuecomment-3054908249, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCQJPEDBN4VTZ4GDFZOVCTD3HXABHAVCNFSM6AAAAAB7WYVCRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANJUHEYDQMRUHE . You are receiving this because you authored the thread.Message ID: @.***>