roam-research-private-api
roam-research-private-api copied to clipboard
Cannot load the login screen
After running roam-api export ~/Downloads/ -g $ROAM_API_GRAPH -e $ROAM_API_EMAIL -p $ROAM_API_PASSWORD got this
Cannot load the login screen!
(node:6165) UnhandledPromiseRejectionWarning: TimeoutError: waiting for selector `input[name=email]` failed: timeout 60000ms exceeded
at new WaitTask (/usr/local/lib/node_modules/roam-research-private-api/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:505:34)
at DOMWorld.waitForSelectorInPage (/usr/local/lib/node_modules/roam-research-private-api/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:416:26)
at Object.internalHandler.waitFor (/usr/local/lib/node_modules/roam-research-private-api/node_modules/puppeteer/lib/cjs/puppeteer/common/QueryHandler.js:31:77)
at DOMWorld.waitForSelector (/usr/local/lib/node_modules/roam-research-private-api/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:312:29)
at Frame.waitForSelector (/usr/local/lib/node_modules/roam-research-private-api/node_modules/puppeteer/lib/cjs/puppeteer/common/FrameManager.js:842:51)
at Page.waitForSelector (/usr/local/lib/node_modules/roam-research-private-api/node_modules/puppeteer/lib/cjs/puppeteer/common/Page.js:1285:33)
at RoamPrivateApi.logIn (/usr/local/lib/node_modules/roam-research-private-api/RoamPrivateApi.js:197:20)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:6165) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:6165) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.