이전 버전입니다. 현재 최신 버전은 1.2.12입니다. QoderWake 1.2.12 · 출시일:
설치 파일 1.2.10
| 아키텍처 | 형식 | 설치 범위 | 파일 크기 | 다운로드 | SHA256 |
|---|---|---|---|---|---|
| 64비트 | EXE (Inno Setup) | 모든 사용자 | 250.3 MB | download.qoder.com | VirusTotal |
링크와 SHA256은 Windows 패키지 관리자 커뮤니티 매니페스트에서 가져왔습니다. 실행하기 전에 다운로드한 파일의 해시를 비교해 보십시오.
릴리스 노트
@Waker Experience and Group Stability Improvements
Improvements
- @Waker and Automation Setup: Improved account details, authorization confirmations, and delivery destination displays, with clearer guidance when no IM connection is configured.
- Feishu Authorization: Reduced repeated QR-code scans when complete, valid authorization is already available, and unified permission requests for bot search.
- Personal Avatar Memory: Improved reading and recall for large memory collections, reducing memory usage and failures when loading extensive memories.
- Update Guidance: Clarified that restarting and reconnecting after an update may take 3–5 minutes, with clearer retry and repair instructions when something goes wrong.
Bug Fixes
- Fixed shared group files disappearing after list refreshes and errors when uploading group attachments.
- Fixed background processing of historical group tasks with many files causing other tasks to stall or time out.
- Fixed stale task progress being sent after a task became invalid, and DingTalk Personal Avatars continuing to reply after the user had already responded.
- Fixed consecutive WeCom messages being incorrectly treated as busy, and subsequent messages failing to proceed after a conversation failed to start.
- Fixed recovery issues with remote Feishu pairing approvals and configurations with multiple responding Wakers.
- Fixed repeated requests and incorrect “result not found” errors in @Waker responsibility conflict detection.
- Fixed some DingTalk @Waker tasks failing to prepare their working directory on Windows, and document queries being incorrectly blocked with some older DingTalk sign-in configurations.
- Fixed recovery or reinstallation failures after some unsuccessful updates, and conversation startup failures caused by automatic Connector token renewal.
