You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
错误日志:
开始注入App: com.surteesstudios.Bartender
cp: /Applications/Bartender 5.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle: No such file or directory
/Applications/Bartender 5.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle_backup: No such file or directory
Need Deep Sign.
开始签名...
/Applications/Bartender 5.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle: No such file or directory
/Applications/Bartender 5.app: replacing existing signature
xattr: No such file: /Applications/Bartender 5.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle
我从终端进入到 /Applications/Bartender 5.app/Contents/Frameworks/Sparkle.framework/Versions/ 目录后,发现其里面没有 A 目录,变成了 B 目录
最小复现
使用InjectLib-main 进行激活,双击“秋城落叶_启动.command”启动后输入密码,扫描到 Bartender 5 后输入 y 进行注入后出现描述中的报错信息,打开 Bartender 5 也还是显示的试用
检查事项
描述问题
测试发现 Bartender 5 无法激活(版本号为 5.2.3)
错误日志:
开始注入App: com.surteesstudios.Bartender
cp: /Applications/Bartender 5.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle: No such file or directory
/Applications/Bartender 5.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle_backup: No such file or directory
Need Deep Sign.
开始签名...
/Applications/Bartender 5.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle: No such file or directory
/Applications/Bartender 5.app: replacing existing signature
xattr: No such file: /Applications/Bartender 5.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle
我从终端进入到 /Applications/Bartender 5.app/Contents/Frameworks/Sparkle.framework/Versions/ 目录后,发现其里面没有 A 目录,变成了 B 目录
最小复现
使用InjectLib-main 进行激活,双击“秋城落叶_启动.command”启动后输入密码,扫描到 Bartender 5 后输入 y 进行注入后出现描述中的报错信息,打开 Bartender 5 也还是显示的试用
系统情况
系统信息
是否修改了nvram的内核启动参数(黑苹果)
No response
是否使用了需要修改系统文件的工具(黑苹果)
No response
期望行为
希望可以支持 Bartender 5最新版本
额外信息
No response
Crash Log
No response
The text was updated successfully, but these errors were encountered: