Open lilyd-code opened 1 month ago
please provide the last 6 characters of your token and the time you scan.
Hi hcfw, here's the last character of our tokens we tried to scan 6 minutes ago and it didn't work.
a8d891
They get logged in but WeChaty doesn't send a login event:
We tried it twice we're in Eastern Timezone.
also our two other tokens that weren't working for scan started scanning again but not the one mentioned above
Got it. I'll look into it. Sorry it's vacation season now the response might be delayed.
In Sep 25th, Tencent published Wecom 4.1.30. Usually it won't force you to upgrade the version of your windows wecom (which is the platform workpro is working), however we found that since Sep 30th, Tencent is randomly picking some of the accounts to do so.
We are working on adapting the new version now, and will upgrade our server as soon is it's ready.
Thank you, would it be possible to have a temporary token while this fix is being made? Token seems to be deactivated now
Hi hcfw, here's the last character of our tokens we tried to scan 6 minutes ago and it didn't work.
a8d891
They get logged in but WeChaty doesn't send a login event:We tried it twice we're in Eastern Timezone.
Has it been resolved? I've also encountered the same issue.
我们也遇到了
Hi hcfw, here's the last character of our tokens we tried to scan 6 minutes ago and it didn't work.
a8d891
They get logged in but WeChaty doesn't send a login event: We tried it twice we're in Eastern Timezone.Has it been resolved? I've also encountered the same issue.
Not yet. we are still waiting for the resolution.
没有过渡性方案吗?
嗨 hcfw,这是我们 6 分钟前尝试扫描的令牌的最后一个字符,但没有成功。
a8d891
他们登录了,但微信没有发送登录事件: 我们尝试了两次,因为我们在东部时区。解决了吗?我也遇到了同样的问题。
还没有。我们还在等待解决方案。
你好,目前解决了吗
还没有解决,还在等。 Hi Nick~请问更新进度大概什么时候可以完成? @hcfw007
Our token doesn't work anymore, here is the error in our logs:
at Object.onReceiveStatus (/home/ubuntu/polaris/node_modules/@grpc/grpc-js/build/src/ client-interceptors.js:323:181) at /home/ubuntu/polaris/node_modules/@grpc/grpc-js/build/src/resolving-call.js:93:78 at processTicksAndRejections (node:internal/process/task_queues:78:11) for call at at ServiceClientImpl.makeUnaryRequest (/home/ubuntu/polaris/node_modules/@grpc/grpc-j s/build/src/client.js:160:34) at ServiceClientImpl.start (/home/ubuntu/polaris/node_modules/@grpc/grpc-js/build/src /make-client.js:105:19) at node:internal/util:364:7 at new Promise (<anonymous>) at bound (node:internal/util:350:12) at GrpcManager.start (/home/ubuntu/polaris/node_modules/@juzi/wechaty/node_modules/@juzi/wechaty-puppet-service/dist/cjs/src/client/grpc-manager.js:135:32) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async PuppetService.onStart (/home/ubuntu/polaris/node_modules/@juzi/wechaty/node_modules/@juzi/wechaty-puppet-service/dist/cjs/src/client/puppet-service.js:134:9) at async PuppetService.start (/home/ubuntu/polaris/node_modules/state-switch/dist/cjs/src/service-ctl/service-ctl.js:65:17) at async PuppetService.start (/home/ubuntu/polaris/node_modules/@juzi/wechaty/node_modules/@juzi/wechaty-puppet/dist/cjs/src/mixins/service-mixin.js:21:13) { code: 14, 'Wechaty service discovery / resolution failed for target wechaty://token-service-discovery-test.juzibot.com/***********************************************: token "***********************************************" does not exist'
现在workpro已经全量更新到企微新版本了,可以尝试登录,如果不行可以联系销售帮你重启token试试。
Describe the bug
Scan is not being registered after user scans. No login event is provided
Info
To Reproduce
Steps to reproduce the behavior:
Expected behavior
There should be a login event, that logs the user has logged in
Screenshots
Additional context
It started with one account, then the two other accounts needed logging and everything stopped working. Only one account works now because it hasn't been logged out.