Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

v0.1.15 官方 DMG 安装前签名校验未通过，想确认是否与本机环境有关

Open
  • Is something wrong?
#32 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
desktop, release, security

Research direction

Start by reproducing the checks against the v0.1.15 WeChatBridge-0.1.15.dmg asset using the reported SHA-256, codesign verification, Gatekeeper, and stapler checks on Apple Silicon. Done means determining whether the failure is in the release artifact or the local environment, documenting the required diagnostics, or linking a corrected official release with its checksum.

Written by the indexing model from the issue text.

Description

你好，准备试用官方 v0.1.15 时，安装前的签名检查没有通过，想请帮忙确认是发行包问题，还是本机校验环境的问题。

下载包

  • 来源：官方 v0.1.15 Release
  • 文件：WeChatBridge-0.1.15.dmg
  • 大小：21,731,727 bytes
  • SHA-256：6a625170390be2fe7490b9fb821eed4233f06bb79d12f8359f715684498d82e9
  • 大小与 SHA-256 均与 GitHub Release 资产信息一致；DMG 自身完整性检查通过
  • 检查日期：2026-10-04

检查过程与现象

以下根据本次 Mac 本机检查的结果摘要整理，目前没有可直接贴出的完整原始终端输出；macOS 的具体版本也暂未记录，因此不填写猜测值。

  1. 下载后校验大小和 SHA-256，并检查 DMG 完整性。
  2. 以只读方式挂载 DMG，检查其中的“微信流.app”，未安装或启动应用。
  3. 对该应用运行 codesign --verify --deep --strict，本次检查报告 arm64 签名无效。
  4. 签名元数据中能看到 stapled notarization ticket 信息，但 Gatekeeper、stapler 检查均未得到通过结果，其他检查中还出现了代码签名子系统错误。

由于也有代码签名子系统错误，目前不能排除本机环境原因，尚不能断定这个发行包本身有问题。检查停在这里，没有移除隔离属性、重新签名或绕过系统安全检查。

想请帮忙确认

  • 上述 SHA-256 对应的官方 DMG，在 Apple Silicon Mac 上能否通过应用的严格签名检查及 Gatekeeper 检查？
  • 如果更像本机环境问题，建议补充哪些诊断信息或进行哪些不降低系统安全设置的检查？
  • 如果已有重新打包的版本，能否提供官方 Release 链接、版本号和校验值？

谢谢！

Dominant language
Swift
Stars
1.6k
Forks
459
Avg merge
11h 44m
Merged PRs (30d)
7

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from freestylefly/WeChatBridge

All issues in freestylefly/WeChatBridge

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.