Describe the bug
Whenever i ran the "rednote-mcp init" command, the login page kept relaunching after the timeout. And after looking through the logs, i found:
{"level":"error","message":"Login attempt 1 failed: page.waitForSelector: Timeout 10000ms exceeded.\nCall log:\n\u001b[2m - waiting for locator('.login-container') to be visible\u001b[22m\n","name":"TimeoutError","stack":"page.waitForSelector: Timeout 10000ms exceeded.\nCall log:\n\u001b[2m - waiting for locator('.login-container') to be visible\u001b[22m\n\n at AuthManager.login (C:\\Users\\<username>\\AppData\\Roaming\\npm\\node_modules\\rednote-mcp\\dist\\auth\\authManager.js:133:33)\n at async Command.<anonymous> (C:\\Users\\<username>\\AppData\\Roaming\\npm\\node_modules\\rednote-mcp\\dist\\cli.js:196:13)","timestamp":"2025-11-07T03:59:28.058Z"}
which suggests that the authManager's login function didn't manage to find the login container in time from the DOM element? So did i overlooked some steps or is this something that can be fixed?
Environment
- OS: Windows
- Node Version: 10.9.3
- Package Version: 0.2.3
Describe the bug
Whenever i ran the "rednote-mcp init" command, the login page kept relaunching after the timeout. And after looking through the logs, i found:
which suggests that the authManager's login function didn't manage to find the login container in time from the DOM element? So did i overlooked some steps or is this something that can be fixed?
Environment