Quark: failed get objs: failed to list objs: token [st invalid]

[alexbiaolol]

Please make sure of the following things

• I have read the documentation.
  我已经阅读了文档。

• I'm sure there are no duplicate issues or discussions.
  我确定没有重复的issue或讨论。

• I'm sure it's due to AList and not something else(such as Network ,Dependencies or Operational).
  我确定是AList的问题，而不是其他原因（例如网络，依赖或操作）。

• I'm sure this issue is not fixed in the latest version.
  我确定这个问题在最新版本中没有被修复。

AList Version / AList 版本

V3.33.0

Driver used / 使用的存储驱动

Quark

Describe the bug / 问题描述

The configuration didn't change but recently shows "failed get objs: failed to list objs: token [st invalid]"

Reproduction / 复现链接

N/A

Config / 配置

N/A

Logs / 日志

[welcome]

Thanks for opening your first issue here! Be sure to follow the issue template!

[github-actions]

See

1. 69% 提示failed get objs: failed to list objs: not found device info #3521
2. 65% Linux Arm64版本挂载阿里云盘出错，failed get objs: failed to list objs: Post "https://api.aliyundrive.com/v2/file/list": EOF #3164
3. 61% failed get objs: failed to list objs; driver not init #5588
4. 56% failed get objs: failed to list objs: PROPFIND /: 403 #6314
5. 56% failed get objs: failed to list objs: 签名错误,请检查您的本地时间是否为东八区时间-ak illegality 999 #5767
6. 56% failed get objs: failed to list objs: The resource could not be found. #1890
7. 56% webdav failed get objs: failed to list objs: ReadDir  #1739
8. 56% 挂载webdav提示 failed get objs: failed to list objs: ReadDir / #1732
9. 52% 蓝奏云cookie账号登录下载文件提示failed link: failed get link: not find file page param #5332
10. 50% 使用蓝奏云cookie挂载下载文件出现“failed link: failed get link: not find file page param” #4419

[anwen-anyi]

无任何问题吖？ 能添加 能列出列表 能下载

[DestinyYZH]

遇到了类似的问题，简单检查了一下，应该是网页版夸克请求网址变化了，现在请求网址是 drive-pc.quark.cn/* ,过去是drive.quark.cn/* ,在alist里请求的还是旧地址

[DeodarPeng]

重新获取更新下cookie

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

Hello @, this issue was closed due to inactive more than 52 days. You can reopen or recreate it if you think it should continue. Thank you for your contributions again.