Open hoelger opened 1 year ago
I have the same console output and the bot is stuck when trying to access an apartment. ("Wohnung ... näher anschauen")
I cloned the repo, built the app according to instructions and then ran "npm run-script start" to start the bot.
For me it worked on the second run, then the cookies were already rejected, and the bot could start searching and applying. Try this as a workaround and let me know if it works for you.
Reproducable for the non-artifact version if I remove the above mentioned files in /home/georg/.config/Electron/
When I try a second time, I don't get the same console output but
Attempt to launch a second task, ignored.
Attempt to launch a second task, ignored.
Attempt to launch a second task, ignored.
and the bot is stuck with "Wohnung XYZ genauer anschauen". If I delete the files you mentioned in the first post, the cookies and the console output appear again, but the bot gets stuck at the same place.
Hey Lukas, Deleting the files is only meant for reproduction of the problem. Please try to update to the newest version of the bot, there was the release of 1.7 where some of those "wohnung xyz genauer anschauen" issues were solved.
Hey Georg, thanks for the help and sorry for the late reply. I tried with 1.7 but I have the same problem. It gets stuck at "Wohnung xyz genauer anschauen". In terms of warning messages, I get the same "Attempt to launch a second task, ignored." as before. I'm starting to think this might be a problem related to my system as I tried on an old Windows PC and that's running fine so far minus the initial hiccups. Maybe something about the geometry of the window? I'm using i3 (tiling window manager) on Arch Linux if that's any help.
This only happens when I start the downloaded artifact (app image), started in terminal so I see the console output. This error did not pop up when I run the bot from code. In
/home/georg/.config/Wohnungsbot/
do delete folderLocalStorage
and bothCookies*
files, then the cookie popup will show. Sometimes I have the feeling this error stalls the app. The second time the error kept poping up, but the bot would continue to write applications.console output run 1
console output run 2