Grass Login failed #29
Description
Describe the bug
The container boots up correctly and proceeds to run the custom entry script grass-node_main.py, which handles the login flow at https://app.getgrass.io/.
The login is successful, but after that, the process fails due to an intercepted click when trying to accept a second cookie/banner that appears in a modal dialog. Additionally, during the next step, when trying to download the required browser extension (CRX), the script fails with 'result' and closes the browser. After that, it shows repeated connection errors (Errno 111 - Connection refused).
It’s important to note that an OTP code is received via email during the login process, which might interfere with automated login flows.
Device (please complete the following information):
• Type: Raspberry Pi 5
• OS details: Ubuntu Server 24.04 LTS
• Platform: arm64 (64bit)
• Version: Ubuntu 24.04
Docker
• Docker Compose version: 2.24.5
• Docker version: 24.0.7
To Reproduce
1. Clone the repository and run the container: docker compose up -d
2. Wait for the auto-login process to start at https://app.getgrass.io
3. The script logs in using provided credentials.
4. A second cookie banner appears in a modal, causing a click interception error.
5. The extension download process fails with 'result'
6. The browser is closed and repeated connection errors appear.
Expected behavior
After login, the script should be able to dismiss all banners and proceed to download the CRX extension successfully, continuing with the monetization flow.
Screenshots
N/A – the issue can be observed via container logs.
Additional context
• The error 'result' seems related to a failed or null response from the CRX download source.
• The intercepted click error shows a modal is blocking the banner button (element click intercepted).
• The appearance of an OTP email prompt may now require an extra step that breaks automation.
• This might be due to a recent frontend update at app.getgrass.io.