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.

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

你的应用版本过低,请升级至最新版本后再登录。点击“确定”后将跳转至 最新版下载页面,依赖都是最新版的这个怎么解决呢? #2703

Closed
hedibin opened this issue May 16, 2024 · 2 comments

Comments

@hedibin
Copy link

hedibin commented May 16, 2024

Important:Please file the issue follow the template, or we won't be able to help you to solve the problem.

0. Report Issue Guide

  1. Please run the following command and check whether the problem has been fixed:

    rm -rf package-lock.json
    rm -rf node_modules
    npm install
  2. Please search in FAQ List first, and make sure your problem has not been solved before.

  3. Please search in the issue first, and make sure your problem had not been reported before

1. Versions

What is your wechaty version?

Answer:
1.20.2

Which puppet are you using for wechaty? (puppeteer/padlocal/service...)

Answer:
padlocal

What is your wechaty-puppet-XXX(padchat/puppeteer/) version?

Answer:

What is your node version? (run node --version)
1.20.2
Answer:

What os are you using

Answer:

2. Describe the bug

Give a clear and concise description of what the bug is.

3. To Reproduce

This part is very important: if you can not provide any reproduce steps, then the problem will be very hard to be recognized.

How to create a Minimal, Reproducible Example

Steps to reproduce the behavior:

  1. run '...'
  2. ...
  3. ...

4. Expected behavior

Give a clear and concise description of what you expected to happen.

5. Actual behavior

If applicable, add screenshots to help explain your problem. But the log message must be in plain text instead of screenshot.

6. Full Output Logs

Set env WECHATY_LOG=silly in order to set log level to silly, then we can get the full log (If you dosen't set log env, log level is info as default, we cannot get the full log)

We need full log instead of log screenshot or log fragments!

Show Logs
$ WECHATY_LOG=silly node yourbot.js

-> Make sure to copy/paste the full (instead of only fragments) log message in text format (instead of image/screenshot) at here

7. Additional context

Add any other context about the problem here.

Copy link

dosubot bot commented May 16, 2024

To address the issue where you're prompted to update to the latest version upon login, it's likely due to a version compatibility issue with Wechaty or the padlocal puppet. Here's a structured approach to resolve this:

  1. Update Wechaty and Puppet PadLocal: Ensure both wechaty and wechaty-puppet-padlocal are updated to their latest versions. You can update Wechaty by running npm install wechaty@latest in your project directory. For wechaty-puppet-padlocal, check its repository or npm page for the latest version and update accordingly.

  2. Review Documentation: Check the Wechaty GitHub repository or npm for release notes or documentation that might mention compatibility issues with WeChat. This can provide specific instructions for updates or configurations needed to avoid such errors.

  3. Compatibility Checks: Make sure all other dependencies related to WeChat in your project are up to date. WeChat's API updates can affect how Wechaty and its puppets function, so keeping everything current is crucial.

  4. Provide Detailed Information: If the issue persists after updating, please provide more detailed information such as full output logs, steps to reproduce the behavior, and the expected versus actual behavior. This can help in diagnosing the issue more accurately.

Updating Wechaty and the puppet padlocal to the latest versions is a critical step. After updating, you can check your Wechaty version with:

const { WechatyBuilder } = require('wechaty')
const bot = WechatyBuilder.build()
console.log(bot.version())

This ensures you're running the latest version, which is designed to be compatible with the current WeChat requirements. If the problem continues, reviewing the CHANGELOG.md and gerror-mixin.ts might offer insights into handling such errors or compatibility issues.

Details

Sources


About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

@huan huan added the duplicate label May 20, 2024
@huan
Copy link
Member

huan commented May 20, 2024

Merge to wechaty/puppet-padlocal#302

@huan huan closed this as completed May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants