註冊其他 iOS 裝置
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
如要使用 App Distribution 發布臨時 iOS 版本,請按照本指南註冊測試人員的裝置。臨時建構版本
是指未以企業設定檔簽署的建構版本。只有在裝置的專屬裝置 ID (UDID) 包含在建構版本的佈建設定檔中,裝置才能安裝臨時建構版本。
測試人員接受應用程式測試邀請後,App Distribution 會要求授權,將測試人員的裝置 ID 分享給您 (開發人員)。下載臨時版本前,App Distribution 會要求測試人員註冊裝置。如果測試人員註冊裝置,App Distribution 會從裝置收集 UDID,並透過電子郵件通知您。
收到含有 UDID 的電子郵件後,請使用該 UDID 更新佈建設定檔,然後將新版本發布給測試人員。您可以透過 Firebase 控制台或 Firebase CLI 手動匯出 UDID,也可以使用 fastlane 以程式輔助方式匯出 UDID。
手動匯出 UDID
- 將裝置新增至 Apple 開發人員入口網站。
- 方法 1: 以 CSV 檔案格式匯入裝置 UDID。
在 App Distribution 資訊主頁的「測試人員和群組」分頁中,選取「所有測試人員」,然後按一下「匯出 Apple UDID」下載 CSV 檔案。接著,使用「Register Multiple Devices」(註冊多部裝置) 選項,將檔案匯入 Apple 開發人員帳戶。詳情請參閱「將應用程式發布至已註冊的裝置」。
請注意,Apple 開發人員帳戶每年可能只允許匯入有限數量的裝置。
- 方法 2: 透過電子郵件收集並輸入 UDID。
在 Apple 開發人員入口網站的「新增裝置」頁面中,註冊您收到的電子郵件中指定的新裝置專屬 ID。
- 將已註冊的裝置新增至佈建設定檔。
- 下載佈建設定檔,並用來重建應用程式。如果重建應用程式只是為了更新已註冊的裝置,請勿更新建構編號或版本。
- 從 Firebase 控制台或 CLI 重新發布應用程式。
如果您未變更版本、建構編號或應用程式的程式碼,App Distribution 就不會建立新版本,也不會通知測試人員。如果已發布建構版本,且建構版本號碼和版本相同,只有新註冊裝置的使用者會收到通知電子郵件。
使用 fastlane 以程式輔助方式匯出 UDID
從 fastlane 將所有測試人員裝置的 UDID 匯出為 CSV 檔案。舉例來說,建立並執行新的 download_udids
管道:
lane :download_udids do
firebase_app_distribution_get_udids(
app: "<your Firebase app ID>",
output_file: "<path to output file>",
)
end
使用「Register Multiple Devices」選項,將 UDID 匯入 Apple 開發人員帳戶。詳情請參閱 Apple 的說明文件。請注意,Apple 開發人員帳戶每年可能只允許匯入有限數量的裝置。
將已註冊的裝置新增至佈建設定檔。
下載佈建設定檔,並用來重建應用程式。如果重建應用程式只是為了更新已註冊的裝置,請勿更新版本號碼或版本。
重新發布應用程式。如果未變更版本、建構編號或應用程式的程式碼,App Distribution 就不會建立新版本,也不會通知測試人員。如果您已發布具有相同建構版本號碼和版本的建構版本,只有新註冊裝置的使用者會收到通知電子郵件。
接收快訊
接收預設快訊
根據預設,Firebase 會透過電子郵件傳送新 iOS 裝置註冊的App Distribution快訊。
如要透過這個預設機制接收 App Distribution 快訊,您必須具備 firebase.projects.update
權限。下列角色預設具備這項必要權限:Firebase 管理員,或是專案擁有者或編輯者。
根據預設,專案成員只要具備接收快訊的必要權限,就會在註冊新 iOS 裝置時收到電子郵件。
為帳戶開啟/關閉快訊
你可以為自己的帳戶開啟/關閉App Distribution快訊,不會影響其他專案成員。請注意,您仍須具備必要權限才能接收快訊。
如要開啟或關閉App Distribution快訊,請按照下列步驟操作:
- 前往 Firebase 控制台右上角的「Firebase 快訊」notifications。
- 接著前往「設定」settings,選擇帳戶的快訊偏好設定 App Distribution。
設定第三方服務的進階快訊
你也可以使用 Cloud Functions for Firebase,透過團隊偏好的通知管道傳送 App Distribution 快訊。舉例來說,您可以編寫函式,擷取新 iOS 裝置註冊的快訊事件,並將快訊資訊發布至 Discord、Slack 或 Jira 等第三方服務。
如要完全自動化新 iOS 測試人員的加入程序,您可以編寫函式,將新 iOS 裝置的 UDID 新增至應用程式的 Provisioning Profile、重建應用程式,然後使用更新後的 Provisioning Profile 重新發布應用程式。
如要使用 Cloud Functions for Firebase 設定進階快訊功能,請按照下列步驟操作:
設定 Cloud Functions for Firebase,包括下列工作:
- 設定 Node.js 或 Python 的開發環境。
- 安裝並登入 Firebase CLI。
- 使用 Firebase CLI 初始化 Cloud Functions for Firebase。
編寫及部署函式,從 App Distribution 擷取快訊事件,並處理事件酬載 (例如在 Discord 訊息中發布快訊資訊)。
如要瞭解可擷取的所有快訊事件,請參閱App Distribution快訊的參考文件。
後續步驟
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-16 (世界標準時間)。
[null,null,["上次更新時間:2025-08-16 (世界標準時間)。"],[],[],null,["# Register additional iOS devices\n\n\u003cbr /\u003e\n\nIf you want to distribute ad hoc iOS builds using App Distribution, you must follow\nthis guide to register your testers' devices. An [*ad hoc\nbuild*](https://help.apple.com/xcode/mac/current/#/dev31de635e5)\nis a build not signed with an Enterprise profile. A device can only install an\nad hoc build if the device's unique device identifier (UDID) is included in the\nbuild's provisioning profile.\n\nWhen a tester accepts an invitation to test your app, App Distribution requests\npermission to share the tester's device identifier with you, the developer.\nBefore downloading an ad hoc build, App Distribution asks the tester to register\ntheir device. If the tester registers their device, App Distribution collects the\nUDID from the device and notifies you of the UDID by email.\n\nWhen you receive an email containing a UDID, update your provisioning profile\nwith the UDID and distribute a new build to your testers. You can manually\nexport UDIDs using the [Firebase console or Firebase\nCLI](#manual-export-udids), or you can programmatically export UDIDs using\n[fastlane](#programmatic-export-udids).\n\nManually export UDIDs\n---------------------\n\n1. Add the devices to your Apple developer portal.\n - *Option 1:* Import the device UDIDs as a CSV file.\n\n In the **Testers \\& Groups** tab of the App Distribution dashboard, select\n **All testers** , then click **Export Apple UDIDs**\n to download a CSV file. Next, import the file into your\n [Apple developer account](https://developer.apple.com/account/resources/devices/add)\n using the **Register Multiple Devices** option. To learn more, see\n [Distributing your app to registered devices](https://developer.apple.com/documentation/xcode/distributing_your_app_to_registered_devices).\n\n Note that your Apple developer account may only allow you to import a limited number of\n devices per year.\n - *Option 2:* Collect and enter the UDIDs by email.\n\n On the [Add Devices](https://developer.apple.com/account/resources/devices/add)\n page of the Apple developer portal, register the new UDID specified in the\n email you received.\n2. Add the registered devices to your [provisioning profile](https://developer.apple.com/account/resources/profiles/list).\n3. Download the provisioning profile and use it to rebuild your app. If you are rebuilding only to update the registered devices, don't update the build number or version.\n4. Re-distribute your app from the [Firebase console](https://firebase.google.com/docs/app-distribution/ios/distribute-console#distribute) or [CLI](https://firebase.google.com/docs/app-distribution/ios/distribute-cli#distribute). If you don't change your version, build number, or your app's code, App Distribution does not create a new release and won't notify testers. If you already distributed a build with the same build number and version, only users of newly-registered devices receive notification emails.\n\nProgrammatically export UDIDs using fastlane\n--------------------------------------------\n\n1. Export all of your tester device UDIDs as a CSV file from fastlane. For\n example, create and run a new `download_udids` lane:\n\n lane :download_udids do\n firebase_app_distribution_get_udids(\n app: \"\u003cyour Firebase app ID\u003e\",\n output_file: \"\u003cpath to output file\u003e\",\n )\n end\n\n | **Note:** To automate releasing a new build with new UDIDs, see [Distribute your\n | pre-release iOS builds faster with App Distribution and\n | fastlane](https://firebase.google.com/codelabs/appdistribution-udid-collection).\n2. Import the UDID(s) into your [Apple developer account](https://developer.apple.com/account/resources/devices/add)\n using the **Register Multiple Devices** option. To learn more, see [Apple's\n documentation](https://developer.apple.com/documentation/xcode/distributing_your_app_to_registered_devices).\n Note that your Apple developer account may only allow you to import a\n limited number of devices per year.\n\n3. Add the registered devices to your [provisioning profile](https://developer.apple.com/account/resources/profiles/list).\n\n4. Download the provisioning profile and use it to rebuild your app. If you are\n rebuilding only for the purposes of updating the registered devices, don't\n update the build number or version.\n\n5. [Re-distribute your\n app](/docs/app-distribution/ios/distribute-fastlane#distribute). If you\n don't change your version, build number, or your app's code,\n App Distribution does not create a new release and won't notify testers. If you\n already distributed a build with the same build number and version, only\n users of newly-registered devices will receive notification emails.\n\nReceive alerts\n--------------\n\n### Get default alerts\n\nBy default, Firebase can send App Distribution alerts for new iOS device\nregistrations via email.\n\nTo receive App Distribution alerts via this default mechanism, you must have the\n`firebase.projects.update` permission. The following roles include this required\npermission by default: [Firebase\nAdmin](/docs/projects/iam/roles-predefined-all-products) or project [Owner or\nEditor](/docs/projects/iam/roles-basic).\n\nBy default, every project member (who has the required permissions to receive\nalerts) will get an email when a new iOS device is registered.\n\n#### Turn on/off alerts for your own account\n\nFor your own account, you can turn on/off App Distribution alerts without\naffecting other project members. Note that you still need the required\npermissions to receive alerts.\n\nTo turn App Distribution alerts on or off, follow these steps:\n\n1. In the Firebase console, in the top right-corner, go to notifications *Firebase\n alerts*.\n2. Then, go to settings *Settings* and set your account preference for App Distribution alerts.\n\n### Set up advanced alerting to third-party services\n\nYou can also send App Distribution alerts to your team's preferred notification\nchannel using Cloud Functions for Firebase. For example, you can write a function\nthat captures an alert event for the registration of a new iOS device and post\nthe alert information to a third-party service, like Discord, Slack, or Jira.\n\nTo fully automate onboarding new iOS testers, you can write a function that adds\na new iOS device's UDID to the provisioning profile of your app, rebuilds the\napp, and redistributes the app with the updated provisioning profile.\n| **Note:** To use advanced alerting capabilities, your Firebase project needs to use the [Blaze pricing plan](/pricing).\n\nTo set up advanced alerting capabilities using Cloud Functions for Firebase, follow these steps:\n\n1. [Set up Cloud Functions for Firebase](/docs/functions/get-started),\n which includes the following tasks:\n\n 1. Set up a development environment for Node.js or Python.\n 2. Install and sign into the Firebase CLI.\n 3. Initialize Cloud Functions for Firebase using the Firebase CLI.\n2. [Write and deploy a function](/docs/functions/alert-events) that\n captures an alert event from App Distribution and handles the event\n payload (for example, posts the alert information in a message on Discord).\n\nTo learn about all of the alert events that you can capture, go to the reference\ndocumentation for [App Distribution\nalerts](/docs/reference/functions/2nd-gen/node/firebase-functions.alerts.appdistribution).\n\nNext steps\n----------\n\n- [Import testers from CSV\n files](/docs/app-distribution/import-testers-csv-files).\n\n- To learn how to increase your internal testing base, see [Create invite\n links](/docs/app-distribution/create-invite-links)."]]