Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Wechaty account logout unexpectedly #37

Closed
hailiang-wang opened this issue Oct 7, 2016 · 3 comments
Closed

Wechaty account logout unexpectedly #37

hailiang-wang opened this issue Oct 7, 2016 · 3 comments
Labels
bug

Comments

@hailiang-wang
Copy link
Member

hailiang-wang commented Oct 7, 2016 •
edited
Loading

Description

Since account login successfully, wechaty run in Ubuntu Server, but after several hours, the account logout unexpectedly.

Trace


^[[31m[2016-10-06 22:19:26.753] [ERROR] console - ^[[39mERR PuppetWebServer initEventsFromClient() client on error: TypeError: Cannot read property 'bridge' of undefined
    at new MediaMessage (/root/git/chatbot-mvp/philly-wechat/node_modules/wechaty/src/message-media.js:18:33)
    at PuppetWeb.onServerMessage (/root/git/chatbot-mvp/philly-wechat/node_modules/wechaty/src/puppet-web/event.js:365:11)
    at emitOne (events.js:96:13)
    at Server.emit (events.js:188:7)
    at Socket.client.on.data (/root/git/chatbot-mvp/philly-wechat/node_modules/wechaty/src/puppet-web/server.js:149:14)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Socket.onevent (/root/git/chatbot-mvp/philly-wechat/node_modules/socket.io/lib/socket.js:335:8)
    at Socket.onpacket (/root/git/chatbot-mvp/philly-wechat/node_modules/socket.io/lib/socket.js:295:12)
    at Client.ondecoded (/root/git/chatbot-mvp/philly-wechat/node_modules/socket.io/lib/client.js:193:14)
^[[32m[2016-10-06 22:19:26.755] [INFO] console - ^[[39mINFO Bot 小白 logouted
^[[32m[2016-10-06 22:20:12.745] [INFO] console - ^[[39mINFO Bot error: [object Object]
^[[33m[2016-10-06 22:20:12.893] [WARN] console - ^[[39mWARN PuppetWebEvent onBrowserDead() will not init browser because browser.targetState(close) !== open

image

Is it a bug? Or what is the solution to keep it steady?
One solution is auto restart when getting crash.
@hailiang-wang hailiang-wang mentioned this issue Oct 7, 2016
Open
@huan
Copy link
Member

huan commented Oct 7, 2016

this problem is fixed yesterday.

u can pull the latest code to hav a try.

and please be careful because master branch is in heavy developing this week.

I will tag a stable version later.

@huan
Copy link
Member

huan commented Oct 7, 2016

fixed by this commit:
c589150

@huan huan added the bug label Oct 8, 2016
@huan huan closed this as completed Oct 8, 2016
@hailiang-wang
Copy link
Member Author

verified. problem is fixed.

@oday0311 oday0311 mentioned this issue Apr 18, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@huan @hailiang-wang