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
-`Developer Team ID` (i.e. Apple Account, see [Xcode section](#xcode))
25
26
26
27
# Dev
27
28
@@ -30,6 +31,10 @@ Reviewing the template will help you understand the composition of the project.
30
31
31
32
# Build
32
33
34
+
> [!NOTE]
35
+
> Before building the app with Xcode make sure you create the `.dev.xcconfig` files [below](#xcconfig) and fill in your `Developer Team ID`.
36
+
> Otherwise `App groups` related functions will not work properly.
37
+
33
38
-`npm run build:mac`[^1][^2]
34
39
-`cd ./xcode`
35
40
-`xcodebuild -scheme Mac`[^1][^2][^3] or build with `Xcode` App
@@ -42,32 +47,27 @@ Reviewing the template will help you understand the composition of the project.
42
47
43
48
# Xcode
44
49
50
+
Please note that a developer account is required, which can be a free Apple Account that has agreed to the Apple Developer Agreement. This is required to obtain a `Team ID` and use the `App groups` capability.
51
+
45
52
### Configurations
46
53
47
-
The Xcode project contains two configurations, which have independent `xcconfig` configuration files, and can run on your local at the same time without conflicts.
54
+
The Xcode project contains several configurations, which have independent `xcconfig` configuration files, and can run on your local at the same time without conflicts.
55
+
56
+
-`Vite`: for vite real-time development.
48
57
49
-
-`Debug`: No developer account is required, that is `Sign to Run Locally` by default, which will speed up the build during development. This is convenient for developers without an account, and contributors who only need to do simple local debugging.
58
+
-`Debug`: for developmentand debugging.
50
59
51
-
-`Release`: A developer account is required, which means it can be used for distribution as well as running on real iOS/iPadOS devices. You will need to override your developer account information in `xcconfig` to complete the build.
60
+
-`Release`: for building and distributing.
52
61
53
62
### xcconfig
54
63
55
64
All `xcconfig` files are in the [`/xcode/xcconfig/`](../xcode/xcconfig) directory. Each `.xcconfig` file can be overridden by `.dev.xcconfig` in the same path, they will be ignored by `git`, so you can override any build settings locally.
56
65
57
-
For example, you can create an `Userscripts-Release.dev.xcconfig` file to override [`Userscripts-Release.xcconfig`](../xcode/xcconfig/Userscripts-Release.xcconfig) and fill in your own developer account information there:
58
-
59
-
`Userscripts-Release.dev.xcconfig`
60
-
61
-
```
62
-
DEVELOPMENT_TEAM = XXXXXXXXXX
63
-
```
64
-
65
-
Another example, if you want `Debug` builds to be also signed, so instead of enabling `Allow Unsigned Extensions` every time in Safari, you can create:
66
+
For example, you can create an `Userscripts-Debug.dev.xcconfig` file to override [`Userscripts-Debug.xcconfig`](../xcode/xcconfig/Userscripts-Debug.xcconfig) and fill in your own developer account `Team ID` there:
66
67
67
68
`Userscripts-Debug.dev.xcconfig`
68
69
69
70
```
70
-
CODE_SIGN_IDENTITY = Apple Development
71
71
DEVELOPMENT_TEAM = XXXXXXXXXX
72
72
```
73
73
@@ -79,4 +79,4 @@ Note that all existing `.xcconfig` files already include `.dev.xcconfig` files o
0 commit comments