Fix first launch and package hook as a signed framework

This commit is contained in:
admin committed 2026-11-12 03:27:18 +08:00
1 parent c1d0293404
commit 97a4fad71f
6 files changed
+147 -20

No files matched your search

+19
View File
@@ -90,6 +90,25 @@ group.<your-team-id>.<your-app-id>.01
The exact value must match your own profile. Do not reuse someone else's certificate, profile, or App Group.
The hook is stored as a nested framework at:
```text
Payload/AppsManager.app/Frameworks/AppsManagerHook.framework
```
Standard signing tools must sign `Frameworks` recursively. If a tool signs only the main executable, the app will fail to launch after re-signing. The published build uses the framework layout specifically so tools such as AltStore, SideStore, Sideloadly, and similar signers handle the hook as nested code.
### 重签名 / Re-signing
- 必须保留 App Group 权限;如果新的描述文件没有 App Group,App 会提示 `No usable App Group`,无法访问其他 App 容器。
The new provisioning profile must include an App Group. Without it the app reports `No usable App Group` and cannot access other app containers.
- 修改 Bundle ID 时,必须同时使用与该 Bundle ID 匹配的描述文件和 entitlements。
When changing the Bundle ID, use a matching provisioning profile and entitlements.
- 签名工具必须递归签名 `Frameworks` 目录;不要只签名主程序。
The signing tool must recursively sign the `Frameworks` directory, not only the main executable.
- 免费 Apple ID 通常不支持 App Group,因此无法让 worse_query 正常工作。
Free Apple ID profiles generally do not support App Groups, so worse_query will not work with them.
## 第三方代码 / Third-party code
This source includes and links code from: