-
-
Notifications
You must be signed in to change notification settings - Fork 589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Evaluation failed: TypeError: Cannot read property 'default' of undefined #1117
Comments
related: #1116 |
@contatodct when did this issue start and please add a screenshot of the browser here please |
@smashah started about 5 days ago, I disabled the Browser with Use_chrome false I am registering only through the terminal because I use Debian in text mode |
I remember that this issue happened only after I tried registering from another number. Haven't tested this scenario on MAC though. |
@rahulserver that's right, whatever, it happens on any operating system! and it only happens when I try to register another number |
@rahulserver @contatodct if this happens on every operating system can you kindly take a screen recording of the process or a screenshot of the browser window when this happens please. I'm unable to recreate the issue with the current information. |
@smashah as I said, I don't use a browser, I use it directly on my DEBIAN 8.7 64Bits terminal |
this happens with me too |
@contatodct I have a sneaking suspicion that you're getting tos-blocked and then the system forces it to untosblock itself (which wow cool). I just need confirmation of this with a screenshot of the web page. OR! A screenshot of the folder structure from your process working directory. When this happens next, please run So:
If that directory is there then simply deleting it before every run should fix this issue. Another thing that may help is installing real chrome on your machines and running with Lastly, you really should NOT be running any puppeteer based program as root. Please make a new user and make that user run the program. |
@edneijunior This doesn't appear to have anything to do with |
I also think this has nothing to do with |
@rahulserver @contatodct I was not able to replicate the issue. in https://github.com/open-wa/wa-automate-nodejs/releases/tag/3.1.4 it will take a screenshot if the error occurs again and add it into a This new version also tries to predict the error and attempts to "wait" for a valid session which may stop this problem from happening altogether. I've spent the last few days trying to replicate this issue and will be spending some time on other issues. Please let me know if there are any updates. Closing for now. Thanks |
@rahulserver @contatodct this new version may have fixed the issue. It may have been a case of Debian being too fast for the code. Adding a 2 second cool off before continuing to get the QR code looks like it fixed it. |
I am using Debian, 8.7 64Bits and the Open-wa Example, the first time it registers normally ..... it seems more that it loads a cache somewhere that when removing the Session and trying again to register another number it it happens...
TEMPLATE:
The text was updated successfully, but these errors were encountered: