kiwix/kiwix-apple-custom
1
0
Fork 0
mirror of https://github.com/kiwix/kiwix-apple-custom.git synced 2025-09-17 11:09:18 -04:00
Code Issues Packages Projects Releases Wiki Activity

Update README

Browse Source
This commit is contained in:
Balazs Perlaki-Horvath 2025-02-07 12:03:34 +01:00
parent edab22ce4e
commit b7ffee0380
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -184,6 +184,18 @@ From this step you will have the values for the following GitHub secret keys:
- APPLE_STORE_AUTH_KEY_ID - APPLE_STORE_AUTH_KEY_ID
- APPLE_STORE_AUTH_KEY_ISSUER_ID - APPLE_STORE_AUTH_KEY_ISSUER_ID
## Add test devices
In order to test the app, and in order to even upload it to TestFlight, physical devices needs to be registered on the Apple Developer Account.
It can be done either via XCode, or via the AppStore Connect, as described here:
https://developer.apple.com/help/account/register-devices/register-a-single-device/
## Create a provisioning profile
Uploading builds to TestFlight requires at least one provision profile to be added.
It should contain the development certificate created
earlier (see above), and should also include the test devices (see above).
Here is the detailed Apple documentation on how to create a new development provisitioning profile:
https://developer.apple.com/help/account/manage-provisioning-profiles/create-a-development-provisioning-profile
## Create a Development Signing Identity (optional) ## Create a Development Signing Identity (optional)
If you whish to have the macOS application distributed outside of the AppStore, it needs to be signed with yet another type of certificate, called Developer Signing Identity. If you whish to have the macOS application distributed outside of the AppStore, it needs to be signed with yet another type of certificate, called Developer Signing Identity.