lane:download_udidsdofirebase_app_distribution_get_udids(app:"<your Firebase app ID>",output_file:"<path to output file>",)end
นำเข้า UDID ไปยังบัญชีนักพัฒนาแอปของ Apple
โดยใช้ตัวเลือกลงทะเบียนอุปกรณ์หลายเครื่อง ดูข้อมูลเพิ่มเติมได้ในเอกสารของ Apple
โปรดทราบว่าบัญชีนักพัฒนาแอปของ Apple อาจอนุญาตให้คุณนำเข้าอุปกรณ์ได้เพียงจำนวนหนึ่งต่อปี
[null,null,["อัปเดตล่าสุด 2025-08-16 UTC"],[],[],null,["\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\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\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\nGet 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\nTurn 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\nSet 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- [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)."]]
