Failed taking a screenshot Message: 'chromedriver' executable needs to be in PATH.

[AviralDobhal07]

Hello everyone,

I'm encountering an error while trying to schedule reports using the Alerts and Reports feature in Apache Superset. The error message reads:

"Failed taking a screenshot Message: 'chromedriver' executable needs to be in PATH. Please see https://sites.google.com/a/chromium.org/chromedriver/home."

Despite having installed both the Chrome drivers and Headless Chrome, the error persists. I have attached the Superset logs for reference.

Any assistance in resolving this issue would be greatly appreciated!

Thank you!

[dosubot[bot]]

Hey there, @AviralDobhal07! I'm here to help you with any bugs, questions, or contributions you have regarding Apache Superset. Let's tackle this issue together!

I found some similar issues and discussions that might help you resolve the problem with the 'chromedriver' executable:

1. Closed Issue: Can't get ALERTS & REPORTS working. Error: Failed taking a screenshot Message: 'geckodriver' executable needs to be in PATH. - The solution involves ensuring the ALERT_REPORTS feature flag is enabled, updating the Celery beat schedule, ensuring a headless browser is installed, and configuring SMTP or Slack settings correctly. Additionally, check the permissions and path of the chromedriver executable ^[1].

2. Closed Issue: Cant take screenshot: 'chromedriver' executable may have wrong permissions. - The solution suggests adding --remote-debugging-pipe to the Chrome options and ensuring the chromedriver is placed in /usr/bin with 755 permissions. This might resolve the permission issue you're facing ^[2].

3. Closed Issue: Automated reports in local using docker compose - Failed taking a screenshot Message: 'geckodriver' executable needs to be in PATH. - It suggests using the -dev image of Superset, which includes necessary components like the Firefox headless browser ^[3].

Try these solutions to see if they resolve your issue. Make sure the chromedriver is correctly installed and accessible in your system's PATH.

To continue talking to Dosu, mention @dosu.