Chrome extension problem 6.10.3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
27-12-21 11:30 AM
Hi,
We recently updated to 6.10.3 to fix issues with the Chrome extension. But after updating to 6.10.3 we now get another error when Chrome gets restarted:
ERROR: Internal : Failed to perform step 1 in Navigate Stage 'Launch Chrome 2' on page 'Launch Chrome' - The port establishing the connection to the browser extension cannot be opened.
We are using ephemeral ports. When debugging we're able to launch Chrome if we're stepping into the Chrome manager object. Stepping over results in the mentioned error. We have tried both closing chrome and kill process, wait stages between killing and launching but with no luck.
All advise are appreciated, thanks.
We recently updated to 6.10.3 to fix issues with the Chrome extension. But after updating to 6.10.3 we now get another error when Chrome gets restarted:
ERROR: Internal : Failed to perform step 1 in Navigate Stage 'Launch Chrome 2' on page 'Launch Chrome' - The port establishing the connection to the browser extension cannot be opened.
We are using ephemeral ports. When debugging we're able to launch Chrome if we're stepping into the Chrome manager object. Stepping over results in the mentioned error. We have tried both closing chrome and kill process, wait stages between killing and launching but with no luck.
All advise are appreciated, thanks.
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
29-12-21 06:20 AM
Hi,
Were you using Tracking ID and have you tried unchecking the highlighted setting and restart BP?
Were you using Tracking ID and have you tried unchecking the highlighted setting and restart BP?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
29-12-21 09:20 AM
Hi @Henry Li ,
In our case fixed browser extension port is already unchecked. We will try using tracking ID to see if this solves the problem. Thanks.
