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

[BUG]v1.78.104，win11系统，kimi提示：TypeError: Cannot read properties of null (reading 'chat') #833

Open
lingok1 opened this issue May 7, 2024 · 1 comment
Open

[BUG]v1.78.104，win11系统，kimi提示：TypeError: Cannot read properties of null (reading 'chat') #833

lingok1 opened this issue May 7, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@lingok1
Copy link

lingok1 commented May 7, 2024

Describe the bug / 描述问题

v1.78.104，win11系统，kimi提示：TypeError: Cannot read properties of null (reading 'chat')

To Reproduce / 复现步骤

v1.78.104，win11系统，kimi提示：TypeError: Cannot read properties of null (reading 'chat')

Expected behavior / 期望行为

v1.78.104，win11系统，kimi提示：TypeError: Cannot read properties of null (reading 'chat')

Screenshots / 截图

No response

Devtools Info / 开发者工具信息

v1.78.104，win11系统，kimi提示：TypeError: Cannot read properties of null (reading 'chat')

OS and version / 操作系统版本

v1.78.104，win11系统，kimi提示：TypeError: Cannot read properties of null (reading 'chat')

ChatALL version / ChatALL 版本

v1.78.104，win11系统，kimi提示：TypeError: Cannot read properties of null (reading 'chat')

Network / 网络

v1.78.104，win11系统，kimi提示：TypeError: Cannot read properties of null (reading 'chat')

Additional context / 其它相关信息

No response
@lingok1 lingok1 added the bug Something isn't working label May 7, 2024
@maston2
Copy link

maston2 commented May 8, 2024 •
edited
Loading

image

@PeterDaveHello PeterDaveHello mentioned this issue Jun 30, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lingok1 @maston2