Apple certified technical coordinator 10.11 là gì năm 2024
|
Removed support for app upload using notarization on macOS. Instead, use Show
For details on previous Transporter releases, see . WelcomeWhat is Transporter?Transporter is Apple’s Java-based command-line tool for large catalog deliveries. You can use Transporter to deliver your pre-generated content in a Store Package to the Apple TV app, iTunes Store, Apple Books, and App Store. Whether you use your iTunes Connect account (book publisher, music provider), App Store Connect account (app developer), or encoding house account for your book, video, music, or app content, you can use Transporter to ensure your metadata and assets (for example, audio, video, books, and app files) are properly delivered to the iTunes Store, Apple Books, or App Store, validating the Store Packages against Apple’s specifications. Because some Transporter options are restricted based on user type and content type, before you deliver your Store Packages, make sure you know whether you want Transporter to authenticate you using your iTunes Connect or App Store Connect account, or your encoding house account. For more information, see . Transporter includes the following features:
Guide outlineThis guide describes Transporter, Apple’s Java-based command-line tool used for sending content to the iTunes Store, Apple Books, and App Store, and the steps necessary to install, set up, and use Transporter. This guide is organized as follows:
In addition, a revision history is provided for your reference. Note: Because Apple periodically releases new versions and updates to its software, images and output shown in this guide might be somewhat different from what you see on your screen. Get startedSystem and network requirementsApple supports Transporter on the following operating systems:
To install and run Transporter, you should have:
Notes:
Transporter uses a Service Oriented Architecture (SOA) to send and receive data and messages. It communicates with Apple’s Object Store (HTTP) servers using the HTTPS protocol. If this is a problem, contact your Apple technical representative. If you use Signiant, Transporter communicates with Signiant’s servers using Transmission Control Protocol/Internet Protocol (TCP/IP) and User Datagram Protocol (UDP). If you use Aspera, in addition to using TCP/IP and UDP, Transporter communicates with Aspera’s servers using the SSH protocol. The following table lists more details about the servers with which Transporter can communicate. By default, to use Transporter you need only port 443 to communicate with Apple’s contentdelivery.itunes.apple.com servers. You can use the “Aspera only” servers only when you are using the Aspera delivery method. You must open additional “Aspera only” servers when you are using Aspera delivery method. Communication with the Aspera servers requires port 33001. You can use the “Signiant only” servers only when you are using the Signiant delivery method. You must open additional “Signiant only” servers when you are using Signiant delivery method. Communication with the Signiant servers requires port 44001. If you have outbound and inbound firewall rules, you must open a direct outbound and inbound connection to the appropriate ports listed below. To use the Aspera or Signiant delivery methods, you need to perform additional setup and configuration steps. For more information, see the Aspera and Signiant examples in . Server IP Address TCP Port UDP Port Notes contentdelivery.itunes.apple.com 17.110.232.68 17.56.138.14 17.56.10.18 443 n/a HTTPS* idmsa.apple.com 17.151.2.14 443 n/a HTTPS* northamerica-1.object-storage.apple.com 17.156.96.0/20 443 n/a HTTPS* store-037.blobstore.apple.com 17.188.213.128/26 17.188.223.0/26 443 n/a HTTPS* store-036.blobstore.apple.com 17.188.228.0/26 17.132.8.64/26 17.132.18.64/26 17.188.229.0/26 443 n/a HTTPS* store-035.blobstore.apple.com 17.188.213.64/26 17.188.221.0/26 443 n/a HTTPS* store-033.blobstore.apple.com 17.188.199.192/26 17.132.18.0/26 17.188.195.192/26 17.132.29.128/26 443 n/a HTTPS* store-032.blobstore.apple.com 17.188.195.128/26 17.132.28.128/26 17.188.199.128/26 17.132.19.128/26 443 n/a HTTPS* store-030.blobstore.apple.com 17.188.216.0/26 17.188.224.0/26 443 n/a HTTPS* store-028.blobstore.apple.com 17.188.203.0/24 17.188.212.0/24 443 n/a HTTPS* store-026.blobstore.apple.com 17.188.210.0/24 17.188.202.0/24 443 n/a HTTPS* store-025.blobstore.apple.com 17.188.201.0/24 17.188.209.0/24 443 n/a HTTPS* store-004.blobstore.apple.com 17.132.20.0/23 17.132.22.0/23 443 n/a HTTPS* Upcoming Expansion for Uploads 17.188.193.0/26 17.188.194.0/26 17.188.197.0/26 17.188.198.0/26 17.188.199.192/26 443 n/a HTTPS* transporter.amp.apple.com 17.253.0.0/16 443 n/a HTTPS* vgr501.apple.com 17.110.248.141 33001 33001-33500 Aspera only vgr502.apple.com 17.110.248.142 33001 33001-33500 Aspera only vgr503.apple.com 17.110.248.143 33001 33001-33500 Aspera only vgr504.apple.com 17.110.248.144 33001 33001-33500 Aspera only vgr505.apple.com 17.110.248.145 33001 33001-33500 Aspera only vgr506.apple.com 17.110.248.146 33001 33001-33500 Aspera only vgr507.apple.com 17.110.248.147 33001 33001-33500 Aspera only vgr508.apple.com 17.110.248.148 33001 33001-33500 Aspera only vgr701.apple.com 17.133.233.141 33001 33001-33500 Aspera only vgr702.apple.com 17.133.233.142 33001 33001-33500 Aspera only vgr703.apple.com 17.133.233.143 33001 33001-33500 Aspera only vgr704.apple.com 17.133.233.144 33001 33001-33500 Aspera only vgr705.apple.com 17.133.233.145 33001 33001-33500 Aspera only vgr706.apple.com 17.133.233.146 33001 33001-33500 Aspera only vgr707.apple.com 17.133.233.147 33001 33001-33500 Aspera only vgr708.apple.com 17.133.233.148 33001 33001-33500 Aspera only vgr0901.apple.com 17.57.20.141 33001 33001-33500 Aspera only vgr0902.apple.com 17.57.20.142 33001 33001-33500 Aspera only vgr0903.apple.com 17.57.20.143 33001 33001-33500 Aspera only vgr0904.apple.com 17.57.20.144 33001 33001-33500 Aspera only vgr0905.apple.com 17.57.20.145 33001 33001-33500 Aspera only vgr0906.apple.com 17.57.20.146 33001 33001-33500 Aspera only vgr0907.apple.com 17.57.20.147 33001 33001-33500 Aspera only vgr0908.apple.com 17.57.20.148 33001 33001-33500 Aspera only sgr601.apple.com 17.110.248.101 44001 44001-44500 Signiant only sgr602.apple.com 17.110.248.102 44001 44001-44500 Signiant only sgr603.apple.com 17.110.248.103 44001 44001-44500 Signiant only sgr604.apple.com 17.110.248.104 44001 44001-44500 Signiant only sgr605.apple.com 17.110.248.105 44001 44001-44500 Signiant only sgr606.apple.com 17.110.248.106 44001 44001-44500 Signiant only sgr607.apple.com 17.110.248.107 44001 44001-44500 Signiant only sgr608.apple.com 17.110.248.108 44001 44001-44500 Signiant only sgr801.apple.com 17.133.233.101 44001 44001-44500 Signiant only sgr802.apple.com 17.133.233.102 44001 44001-44500 Signiant only sgr803.apple.com 17.133.233.103 44001 44001-44500 Signiant only sgr804.apple.com 17.133.233.104 44001 44001-44500 Signiant only sgr805.apple.com 17.133.233.105 44001 44001-44500 Signiant only sgr806.apple.com 17.133.233.106 44001 44001-44500 Signiant only sgr807.apple.com 17.133.233.107 44001 44001-44500 Signiant only sgr808.apple.com 17.133.233.108 44001 44001-44500 Signiant only sgr1001.apple.com 17.57.20.101 44001 44001-44500 Signiant only sgr1002.apple.com 17.57.20.102 44001 44001-44500 Signiant only sgr1003.apple.com 17.57.20.103 44001 44001-44500 Signiant only sgr1004.apple.com 17.57.20.104 44001 44001-44500 Signiant only sgr1005.apple.com 17.57.20.105 44001 44001-44500 Signiant only sgr1006.apple.com 17.57.20.106 44001 44001-44500 Signiant only sgr1007.apple.com 17.57.20.107 44001 44001-44500 Signiant only sgr1008.apple.com 17.57.20.108 44001 44001-44500 Signiant only Note:
Install TransporterYou can install and run Transporter on macOS, Windows, and Linux operating systems. Important: As an app developer, you can use Transporter if you already have Xcode, or you can manually download Transporter. For information on how to install Transporter as an app developer, see . Install Transporter on macOSYou can install and run Transporter on the macOS operating system. To install Transporter on macOS:
You are now ready to begin using Transporter. For more information, see . Install Transporter on WindowsYou can install and run Transporter on the Windows operating system. To install Transporter on Windows:
You are now ready to begin using Transporter. For more information, see . Install Transporter on LinuxYou can install and run Transporter on the Linux operating system. Before installing Transporter on Linux, make sure you have sudo privileges. If you don’t have sudo privileges, contact your system administrator.
You are now ready to begin using Transporter. For more information, see . Quick startAfter you install Transporter, use the following steps to get up and running quickly using your iTunes Connect account (book publisher, music provider), App Store Connect account (app developer), or encoding house account for your book, audiobook, video, music, or app content. Important: If you are an encoding house, be sure to use your encoding house account and not your iTunes Connect account. To get up and running quickly:
Content-type detailsOverviewTransporter options are restricted based on user type and content type. Before you deliver your Store Packages, make sure you know whether you want Transporter to authenticate you using your iTunes Connect account (book publisher, music provider), App Store Connect account (app developer), or as an encoding house for your book, audiobook, video, music, or app content. User types:
Note:
Book/audiobook detailsPublishers using Transporter must:
You can run Transporter using a variety of modes, options, and values. However, not all modes are applicable to publishers. Use the following table to understand the modes most relevant for book content. Use this mode To Get a JSON-formatted array of assets to be downloaded from Apple. Then use the vendor identifiers listed in the array of assets with retrieve assets mode to download the assets. Retrieve author information by name, including the artist’s Apple ID. In the XML output, you can also find name localizations, recent book titles and content item Apple IDs, as well as the artist page on the Store (if available). After you find the Apple ID, you can use it in your .itmsp package metadata to differentiate between authors with similar names. Using the Apple ID is the best way to avoid artist issues. Retrieve the current metadata for a book you previously uploaded. If you previously uploaded an .itmsp package and Apple modified the metadata after your initial upload, you need to retrieve the modified metadata before you can resend the package with metadata updates. Identify account(s) for which you have permission to deliver. Retrieve any open ticket information from your iTunes Connect account. Currently, you must have an iTunes Connect account to use query tickets mode. Repair any validation errors found in asset file(s) before sending them to Apple for upload. Note: Apple currently only supports EPUB file (.epub) repair. Download the assets listed in the JSON-formatted array returned by get asset list mode. Monitor the state of an .itmsp package (for example, “on store” or “not on store”) and whether or not the package encountered errors after upload. Note: You can fetch the status of several ISBNs at the same time. Post content and metadata to Apple Books; after you check your assets and .itmsp packages to verify they are ready to be delivered. Validate EPUB, iBooks, and audiobook format files, and ensure books assets are in technical compliance before creating your .itmsp packages for delivery. Verify your .itmsp packages and ensure that metadata and assets meet technical requirements before delivery to ensure any potential issues can be addressed before uploading. Video detailsVideo encoding houses using Transporter must:
Important: If you are an encoding house, be sure to use your encoding house account and not your iTunes Connect account. You can run Transporter using a variety of modes, options, and values. However, not all modes are applicable to video encoding houses. Use the following table to understand the modes most relevant for video content. Use this mode To For video types Check the status and availability of servers before you upload .itmsp packages. movies, subscription video, TV Retrieve a list of all your existing catalog reports for the past 30 days. movies, TV Retrieve the list of report content types (for example, Video) available to you. movies, TV Retrieve movie cast and crew information by name, including the artist’s Apple ID. This mode is useful for locating a specific cast or crew member even if another artist shares their name. In the XML output, you can see if the genre matches the genre of the artist you are looking for, as well as find name localizations, recent movie titles and content item Apple IDs, the roles played by the artist in those titles, and the artist page on the iTunes Store (if available). After you find the artist’s Apple ID, you can use it in your .itmsp package metadata to differentiate between artists with similar names. Using artist ID is the best way to avoid artist issues. movies Retrieve the current metadata for a video you previously uploaded. If you previously uploaded an .itmsp package and Apple modified the metadata after your initial upload, you need to retrieve the modified metadata before you can resend the package with metadata updates. movies, subscription video, TV Identify account(s) for which you have permission to deliver. movies, subscription video, TV Download your catalog reports for one or more content types for the past 30 days. movies, TV Retrieve either a transitional or strict schema file to use to validate your XML files before packaging and sending them to Apple for upload to the iTunes Store. movies, subscription video, TV Monitor the state of an .itmsp package (for example, “on store” or “not on store”) and whether or not the package encountered errors after upload. movies, subscription video, TV Test your file transfer performance by uploading a Transporter memory-generated package to the iTunes Store. movies, subscription video, TV Post content and metadata to the iTunes Store; after you check your assets and .itmsp packages to verify they are ready to be delivered. movies, subscription video, TV Verify your .itmsp packages and ensure that metadata and assets meet technical requirements before delivery to ensure any potential issues can be addressed before uploading. movies, subscription video, TV Music detailsEncoding houses and music providers using Transporter must:
Important: If you are an encoding house, be sure to use your encoding house account and not your iTunes Connect account. You can run Transporter using a variety of modes, options, and values. However, not all modes are applicable to music partners. Use the following table to understand the modes most relevant for music content. Use this mode To Create a new music artist. Create new metadata tickets for a track, ringtone, playlist, or music video you previously uploaded. Note: You don’t need to use iTunes Connect to create tickets. Check the status and availability of servers before you upload .itmsp packages. Retrieve a list of all your existing catalog reports for the past 30 days. Retrieve the list of report content types (for example, Music) available to you. Retrieve artist information by name, including the artist’s Apple ID. This mode is also useful when searching for the genre of a specific artist in a territory; even if another artist shares their name. In the XML output, you can also find name localizations, recent album and song titles and content item Apple IDs, the roles played by the artist on those titles, as well as the artist page on the iTunes Store (if available). After you find the artist’s Apple ID, you can use it in your .itmsp package metadata to differentiate between artists with similar names. Using artist ID is the best way to avoid artist issues. Retrieve the current metadata for music you previously uploaded. If you previously uploaded an .itmsp package and Apple modified the metadata after your initial upload, you need to retrieve the modified metadata before you can resend the package with metadata updates. This mode is also useful for content migration. Using a comma-separated list of vendor identifiers (`Package Summary:`2) or Apple identifiers (`Package Summary:`3), you can look up metadata for multiple packages at the same time. Identify account(s) for which you have permission to deliver. Retrieve any open ticket information from your iTunes Connect account. Currently, you must have an iTunes Connect account to use query tickets mode. Download your catalog reports for one or more content types for the past 30 days. Retrieve either a transitional or strict schema file to use to validate your XML files before packaging and sending them to Apple for upload to the iTunes Store. Monitor the state of an .itmsp package (for example, “on store” or “not on store”) and whether or not the package encountered errors after upload. Test your file transfer performance by uploading a Transporter memory-generated package to the iTunes Store. Post content and metadata to the iTunes Store; after you check your assets and .itmsp packages to verify they are ready to be delivered. Verify your .itmsp packages and ensure that metadata and assets meet technical requirements before delivery to ensure any potential issues can be addressed before uploading. Apps detailsApp developers using Transporter must:
If the Apple ID you use to sign in to Transporter is attached to more than one App Store Connect provider, you must use `Package Summary:`4 to specify the provider account you want to use for the current session. You can use provider mode to get the list of provider accounts for which you have permission to deliver content. Note: To deliver visionOS apps, use the standard commands that are used to deliver other apps, with either the You can run Transporter using a variety of modes, options, and values. However, not all modes are applicable to app developers. Use the following table to understand the modes most relevant for app content. Use this mode To Check the status and availability of servers before you upload .itmsp packages. Retrieve a list of all your existing catalog reports for the past 30 days. Retrieve the list of report content types (for example, Apps) available to you. Retrieve the current metadata for an app you previously uploaded. If you previously uploaded an .itmsp package and Apple modified the metadata after your initial upload, you need to retrieve the modified metadata before you can resend the package with metadata updates. Identify account(s) for which you have permission to deliver. Download your catalog reports for one or more content types for the past 30 days. Retrieve either a transitional or strict schema file to use to validate your XML files before packaging and sending them to Apple for upload to the App Store. Monitor the state of an .itmsp package (for example, “on store” or “not on store”) and whether or not the package encountered errors after upload. Test your file transfer performance by uploading a Transporter memory-generated package to the App Store. Post content and metadata to the App Store; after you check your assets and .itmsp packages to verify they are ready to be delivered. Verify your .itmsp packages and ensure that metadata and assets meet technical requirements before delivery to ensure any potential issues can be addressed before uploading App developer installationChoose one of the following:
Run TransporterSpecify options and valuesWhen you run Transporter using the ``2 command at the command line, you can specify the command-line options and values described in the table that follows. To obtain usage information only, run Transporter without any command-line options. For example, type: ``3 For more information, see . Note:
Two-factor authenticationIf you have enabled two-factor authentication on your account, you must create an app-specific password, as described in Using app-specific passwords. Using an app-specific password increases the level of security and ensures your Apple ID password won’t be collected or stored by third-party apps. Important: You shouldn’t run more than one occurrence of Transporter on the same Store Package at the same time. Command-line options and values Description Mandatory options `2 package(s) were not uploaded because they had problems:`6 Specifies either the source directory containing package(s) (.itmsp) you want to upload or specifies a filename for a single package, including the .itmsp extension, you want to upload. Package filenames can’t contain any spaces. If a filename contains a space, Transporter rejects the package. This option is not required when using provider, diagnostic, lookup metadata, query, or status mode. `2 package(s) were not uploaded because they had problems:`7 App uploads for macOS, Linux, and Windows: Specifies the directory and filename for the app source file (.pkg or .ipa). For Linux and Windows, `2 package(s) were not uploaded because they had problems:`8 is required. `2 package(s) were not uploaded because they had problems:`9 Specifies the Transporter mode. You can specify: ` /Users/bsmith/Applications/Packages/Many/00000000001041.itmsp - Error Messages:`0 Specifies your user password. To avoid typing your password at the command line, you can use the @env or @file directives to pass in your password. For example:
You can also exclude this option entirely. If you exclude `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`0 completely, Transporter prompts you for a secure password. Passwords containing special characters (for example, $, !, &, %, ', ",) can lead to authentication problems. If your password contains special characters, you should use the @env or @file directives, exclude the password entirely (Transporter prompts you for a secure password), or escape the special characters in your password. To escape a character, precede it with a backslash (\). For example, to use a question mark (?), type \?. For more information, see http://tldp.org/LDP/abs/html/escapingsection.html. To send special characters in passwords using Windows, you can:
This option is not required when using diagnostic or repair assets modes. The ` Unable to find registered encoding house user for username "bsmith" (1001)`1 Specifies your username. This option is not required when using diagnostic or repair assets modes. The Optional options ` Unable to find registered encoding house user for username "bsmith" (1001)`6 Specifies the account (encoding house or iTunes Connect) you want Transporter to use when retrieving the list of providers for which you have permission to deliver content. You can specify one of the following values: This option is only valid when using provider mode. ` Unable to find registered encoding house user for username "bsmith" (1001)`9 Used in combination with the `Package Summary:`5, the `Package Summary:`6 is a unique identifier associated with a software content provider. You can find your Issuer ID on the API Keys tab on App Store Connect. The options ` /Users/bsmith/Applications/Packages/Many/00000000001042.itmsp - Error Messages:`7 Specifies the name of the API key that was generated on the App Store Connect web site (API Keys tab). The generated API key consists of a public key and a private key. The private key is in a file called AuthKey_
Note: for Windows users, below are examples of where the file could be stored:
This `Package Summary:`5 option is used in combination with `Package Summary:`6. The options `notarytool`07 Specifies the platform you want Transporter to use when retrieving the current metadata for an app you previously uploaded to the App Store. You can specify one of the following values: `notarytool`08, `notarytool`09, or `notarytool`10. Use `notarytool`11 to distinguish between apps for different platforms with the same Apple identifier. For example, an iOS app with the same Apple identifier as an Apple TV app that is intended for iOS devices and not Apple TV devices. This option is only valid when using lookup metadata mode. `notarytool`12 `notarytool`13 Specifies the Apple identifier for the metadata you want to retrieve. For lookup metadata, status, and statusAll modes, specifies one or more identifiers whose metadata or package upload status you want to retrieve. For createMetadataTicket mode, specifies the identifier for the new metadata ticket. Note: For status, statusAll, and lookupMetadata modes, you can specify a comma-separated list of identifiers (`notarytool`14). To be sure Transporter recognizes the entire list, enclose the list in quotation marks. For example: `notarytool`15. You can’t use this option with `notarytool`16 or `Package Summary:`2. This option is only valid when using lookup metadata, status, statusAll, query tickets, or create tickets modes. `notarytool`18 Used in lookup artist mode, the `notarytool`19 specifies the type of artist you are searching for. To look up a movie artist, specify `notarytool`20. To look up a book author, specify `notarytool`21. Note: If you do not supply the `notarytool`19, it will default to Music. `notarytool`23 Used in download installer mode, `notarytool`24 specifies the machine architecture for the installer. Note: If you do not supply `notarytool`24, the command defaults to the current machine’s architecture. `notarytool`26 Specifies the App Store Connect provider’s short name. If your user account is attached to more than one App Store Connect provider, (for example, if you are a software consultant, where multiple clients have given you App Store Connect access), you must use `Package Summary:`4 to specify the provider you want to use for the current session. If you don’t specify a value and your user account is attached to more than one App Store Connect provider, Transporter uses the content type of the package and any provider names specified in the package’s metadata.xml file to determine your provider short name. If Transporter can’t determine the short name, Transporter:
You can’t use this option with `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`5. This option is only valid when using upload, verify, lookup metadata, lookup artist, create artist, status, statusAll, query tickets, and create tickets modes. `notarytool`29 Specifies the plist file that is exported from Xcode. See for more information on the AppStoreInfo.plist file. `notarytool`30 Books: Specifies the directory and filename for the EPUB source file (.epub file) or iBooks format source file (.ibooks file). You can’t use this option with `notarytool`31. `notarytool`32 Specifies the directory where the source assets are located. You can’t use this option with `Package Summary:`0. `notarytool`34 Specifies whether or not you want Transporter to stop a package during upload and display an error message in the error summary output if any of the package assets would replace existing assets. You can specify one of the following values: `notarytool`35, `notarytool`36. By default, Transporter sets this option to `notarytool`36, doesn’t stop a package upload, and replaces duplicate assets with the assets in the upload package. This option is only valid when using upload mode. `notarytool`38 Specifies the type of assets you want listed when you use get asset list mode. The only valid type is `notarytool`39. This option is only valid when using get asset list mode. `notarytool`40 Specifies that you want to remove successfully uploaded packages from the source directory after Transporter completes the upload process. For example, if you run Transporter with an `Package Summary:`1 value set to /Users/jdoe/packages and specify `notarytool`42, Transporter removes all the packages that successfully upload from the /Users/jdoe/packages directory. Failed packages remain in the /Users/jdoe/packages directory. You can’t use this option with `notarytool`43. `notarytool`44 Specifies whether or not you want Transporter to delete the Aspera log file after a successful upload. You can specify one of the following values: `notarytool`35, `notarytool`36. By default, Transporter sets this option to `notarytool`35 and deletes the Aspera log file after a successful upload. This option is only valid when using the Aspera delivery method to upload packages. `notarytool`48 Specifies the directory where you want Transporter to move the processed packages or files to after Transporter finishes executing, but before uploading the packages or files.
This option is only valid when using lookup metadata, repairEpubAssets, retrieve asset, schema, or request report modes. `notarytool`49 Specifies that you want to verify only metadata, not assets, when running Transporter in verify mode. This option is only valid when using verify mode. `notarytool`50 Specifies the distribution method to use for the app. If you specify `notarytool`51 or if you omit the `notarytool`52 option, the app is processed as an App Store submission. `notarytool`53 Specifies the end date or timestamp for assets you want listed when you use get asset list mode. If you don’t specify the `notarytool`54 option, the array includes all asset files that have been modified since the specified start date. If you specify a simple local date in the ISO-8601 format `notarytool`55, your timezone is used to convert the date into an offset date timestamp with the time set to `notarytool`56. For example, if you are in the Pacific Time Zone and you specify the date `notarytool`57, then the timestamp `notarytool`58 is used. The value `notarytool`59 represents your timezone’s offset from UTC. If you specify a timestamp, the time must be formatted with an offset date time formatter in the ISO-8601 format `notarytool`60. These timestamps look like `notarytool`61. For Java integrators, use the `notarytool`62 formatter. This option is only valid when using get asset list mode. `notarytool`63 Specifies the directory where you want to save error logs. By default, Transporter displays error information in the console. If you specify a path, Transporter saves error logs for each package, using the package name as the filename, in the specified directory, as well as displaying error information in the console. If you specify a relative path, Transporter saves error logs in a path relative to the current working directory. If the package verification and upload is successful, Transporter deletes the error log. For bulk deliveries, Transporter saves the error log for each package inside a single file. To investigate issues for a specific failed upload, you can send the individual error log file instead of sending the output for the entire bulk upload. `notarytool`64 Specifies whether Transporter should escape non-ASCII characters with XML numeric entity references in the XML output. By default, Transporter sets this option to `notarytool`35. If you specify the `notarytool`66 option, you must also specify the `notarytool`67 option. This option is valid only when using create artist or lookup artist modes. Example with `notarytool`68 (the default behavior) `notarytool`69`notarytool`70`notarytool`71`notarytool`72 Example with `notarytool`73 `notarytool`69`notarytool`70`notarytool`76`notarytool`72 Note: Specifying `notarytool`73 may not work correctly on the Microsoft Windows platform. `notarytool`79 Specifies the directory and filename where you want to save output that is formatted for easier parsing by other clients, such as Xcode. If you specify `notarytool`80, Transporter saves the formatted output in the specified location with the specified filename This option is only valid when using upload and verify modes. `notarytool`81 Specifies the directory where you want Transporter to move unsuccessfully validated assets to or failed packages to after Transporter completes the validate or upload process. `notarytool`82 Specifies a token to force Transporter to create a music artist. When you run in create artist mode, before creating a new artist, Transporter performs an artist lookup to determine if there are any existing artists with the name specified in `notarytool`83 Note: When you use a force-creation token, Transporter verifies the token, then expires the token 20 minutes after you run create artist mode. You can only use a force-creation token with the exact same artist name, locale, and artist sort name specified in your initial create artist command. This option is only valid when using create artist mode. `notarytool`84 Specifies if you want to retrieve cover art with retrieve asset mode. This option is only valid when using retrieve asset mode. `notarytool`85 Specifies whether or not you want Transporter to display upload progress details. You can specify one of the following values: `notarytool`35, `notarytool`36. When a file is fully uploaded, Transporter logs the following statement: File Uploaded Successfully. By default, Transporter sets this option to `notarytool`35 and displays upload progress information and percentages during file upload. `notarytool`89 Specifies the iTunes Connect provider’s short name. If your user account is attached to more than one App Store Connect provider, see `Package Summary:`4 above. You can’t use this option with `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`5. This option is only valid when using upload, verify, lookup metadata, lookup artist, create artist, status, statusAll, query tickets, and create tickets modes. `notarytool`92 Specifies the filename used for get asset list mode. If specified, the JSON-formatted array is written to the output file. If the file already exists, it is overwritten. If not specified, the JSON-formatted array is written to standard output. This option is only valid when using get asset list mode. `notarytool`93 Specifies the JSON Web token (JWT). You can generate the JWT with the private key downloaded from the API Keys tab on App Store Connect and use an external tool or library that can be found at https://jwt.io. You can use this option in place of the `Package Summary:`5/`Package Summary:`6 pair. The options `notarytool`00 Specifies the unit of transfer speed, or throttle speed, you want to use with HTTP, Aspera’s FASP protocol, or Signiant’s Media Exchange servers. This option limits the upload speed to the number, in kilobits per second (Kbit/s), you specify. For Signiant, when you specify `notarytool`01, Transporter converts the kilobits per second value to bytes per second. For more precise delivery control, and to help diagnosis network congestion issues, Apple recommends specifying an initial setting of 100000, incrementing by 10000 as needed. For Aspera, you can specify a throttle speed up to 912,000 Kbit/s. This option is required when using the Aspera or Signiant delivery methods. `notarytool`02 Specifies the directory and filename where you want Transporter to log successfully uploaded package and file information, using the following file format: `notarytool`03 `notarytool`04 Specifies the search terms you want Transporter to use when downloading information about music artists available in the iTunes Store. To specify search terms with spaces, enclose the search terms in quotation marks. For example: `notarytool`05. You can’t use this option with `notarytool`06 or `Package Summary:`3. This option is only valid when using lookup artist or create artist modes. `notarytool`08 Specifies the name of the new music artist, in inverted order, with a comma between the last and first names for alphabetical sorting in the iTunes Store. `notarytool`09 Specifies the locale you want to associate with a new music artist. To specify locales, enclose the locales in quotation marks. For example: `notarytool`10. This option is only valid when using create artist mode. `notarytool`11 Specifies any note text you want to include with the newly opened metadata ticket. This option is only valid when using create tickets mode. `notarytool`12 Specifies the directory and filename you want to use to log output information, including timestamps. By default, Transporter logs output information to the console. If you specify a filename, Transporter logs the output to the specified file, as well as to the console. If you specify a relative path, Transporter logs output information in a path relative to the current working directory. `notarytool`13 Specifies that you want Transporter to return output information in XML format. By default, Transporter returns output information in text format. This option is only valid when using verify, upload, lookup artist, status, statusAll, transfer test, list reports, or request report modes. `notarytool`14 Specifies the operating system for the installer. This option is only valid when using download installer mode. Note: If you do not supply `notarytool`15, the command defaults to the current machine’s operating system. `notarytool`16 Specifies the type of output (metadata only, assets only, or both metadata and assets) you want Transporter to return when looking up metadata for a playlist or app you previously uploaded. You can specify one of the following values: `notarytool`17, `notarytool`18, or `notarytool`19. This option is only valid when using lookup metadata mode. `notarytool`20 Specifies the new genre you want to use for your playlist. Where To specify a new genre:
For a complete list of genres, download iTunes Package Music Specification Addendum: Music, Music Video, and Ringtone Genre Codes in the iTunes Connect Resources and Help page for music. `notarytool`25 Specifies the new playlist or music video title for the newly opened metadata ticket. `notarytool`26 Specifies the translation you want to use for your playlist title. Where
To specify a new translation, create a new metadata ticket specifying a playlist vendor ID and the new text you want to use for the playlist title. For example: `notarytool`39 `notarytool`40`notarytool`41 Specifies the public identifier for the assets you want to retrieve with the retrieve asset mode. This option is only valid when using retrieve asset mode. `notarytool`42 Specifies that you want to remove unmanifested files from your EPUB files (.epub) before you send your asset files to Apple for upload to Apple Books. This option is only valid when using repair assets mode. `notarytool`43 Specifies the date for the report you are requesting in the form: `notarytool`44. For example, `notarytool`45 downloads, or displays the status message, for all the reports requested in the 24 hour period on the specified date. If you specify `notarytool`46, Transporter downloads all of the reports requested for the past 30 days. Use this option to download reports that are older than the past 24 hours. When this argument isn’t given, Transporter downloads reports for the past 24 hours. If there is no report requested for the specified date, and the date isn’t today, Transporter displays a message indicating there is no report. `notarytool`47 Specifies the encoding house provider’s short name. This is, for example, the short name of the provider whose assets you are checking, verifying, or uploading or whose package status you are requesting or transfer performance you are testing or metadata guides or quality control files you are downloading. `notarytool`48 Specifies the schema type (for example, music or tv) and version (for example, 3.1 or 3.2) you want to retrieve. For example, `notarytool`49 To generate and download the Japanese iTT V2 static schema file, specify `notarytool`50, without the `notarytool`51 option. This option is required, and only valid, when using schema mode. `notarytool`52 Specifies that you want to retrieve either the transitional schema or the strict schema. You can specify one of the following values: `notarytool`53, `notarytool`54. By default, Transporter returns the schema file to the console. If you specify a directory using `notarytool`55, Transporter saves the schema file to If you specify a static schema (for example, `notarytool`56), the `notarytool`57 command-line option is optional. This option is required, and only valid, when using schema mode. `notarytool`58 Specifies locales, in addition to the artist’s native locale, where you want to search for an artist’s localized name. To specify locales, enclose the locales in quotation marks. For example, to search for a Chinese artist with an English translation of John Doe: `notarytool`59 Note: For lookup artist mode, you can specify a comma-separated list of locales. To be sure Transporter recognizes the entire list, enclose the list in quotation marks. For example: `notarytool`60. This option is only valid when using lookup artist mode. `notarytool`61 Specifies the size of the memory-generated package you want to test, using the following format: `notarytool`62 where:
For example, 10k, 10K, 10kb, 10Kb, 10kB, 10Kb, and 10KB all specify 10 kilobytes. By default, Transporter tests a 10 megabyte (MB) package. This option is only valid when using transfer test mode. `notarytool`63 Specifies the start date or timestamp for assets you want listed when you use get asset list mode. If you specify a simple local date in the ISO-8601 format `notarytool`55, your timezone is used to convert the date into an offset date timestamp with the time set to `notarytool`65. For example, if you are in the Pacific Time Zone and you specify the date `notarytool`57, then the timestamp `notarytool`67 is used. The value `notarytool`59 represents your timezone’s offset from UTC. If you specify a timestamp, the time must be formatted with an offset date time formatter in the ISO-8601 format `notarytool`60. These timestamps look like `notarytool`70. For Java integrators, use the `notarytool`62 formatter. This option is only valid when using get asset list mode. `notarytool`72 Specifies up to 1000 subitem IDs, in a comma-separated string. `notarytool`73 Specifies the type of the subitem to look up. Note: Specifying `notarytool`74 returns metadata only, it doesn’t return subitems of any type. However, not specifying `notarytool`75 at all returns all existing subitems. If you specify `notarytool`76, you must specify `notarytool`75. `notarytool`78 Specifies the directory where you want Transporter to move successfully validated assets to or successfully uploaded packages to after Transporter completes the validate or upload process. You can’t use this option with `notarytool`42. `notarytool`80 Specifies the directory and filename where you want to save summary information. If you specify `notarytool`81, Transporter saves summary information in the specified location with the specified filename, in addition to logging output information to the console and, if you specified a filename with `notarytool`82, the specified output file. For bulk deliveries, Transporter saves several package details inside a single summary file. `notarytool`83 Specifies the delivery method you want to use. You can specify one of the following values: `notarytool`84, `notarytool`85, and `notarytool`86 . Apple recommends you don’t specify this option and instead allow Transporter to use automatic transport discovery to determine the best transport mode for your packages. Currently, Transporter defaults to HTTP as the best transport mode. If you do need to specify `notarytool`3, you should revert back to automatic transport discovery soon as possible. If the specified transport can’t be used due to errors or server unavailability, Transporter chooses another transport based on the transport preference order. Transporter chooses additional transports until all available transport options are exhausted, at which point the delivery fails. For upload mode only, you can specify the delivery methods in the order you want, separated by commas (,). For example, `notarytool`88. If you specify only one transport option (`notarytool`89), Transporter uses that option and if it fails the delivery fails with no fall back options. For details on these methods, see the HTTP, Aspera, and Signiant examples in . `notarytool`90 Specifies that you want Transporter to display the total transmission time for successful packages, along with the package size and bytes per second. You can specify this option with any upload delivery method to receive the time (seconds, minutes, hours) it took Transporter to upload a specific package, along with the package size and throughput details. `notarytool`91 Specifies the new version title for the newly opened metadata ticket. `notarytool`92 Specifies the new track title for the newly opened metadata ticket in the form: `notarytool`93. For example, `notarytool`94. You can also specify a disc number in the form: `notarytool`95. To specify that you want to name track 1 on disc 1 LoremIpsum, type: `notarytool`96. You can specify `notarytool`97 for each track number. If the disc number isn’t specified, Transporter defaults to 1. `notarytool`98 Specifies the translation you want to use for your track title. Where
To specify a new translation, create a new metadata ticket specifying a playlist vendor ID and the new text you want to use for the track title. For example:
`“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`12 Specifies the new version title for the newly opened metadata ticket in the form: `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`13. For example, `notarytool`94. You can also specify a disc number in the form: `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`15. To specify that you want to name track 1 on disc 1 LoremIpsum, type: `notarytool`96. `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`17 Specifies a specific report type to request or the special value `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`18, which requests reports for all of your supported report types. The following is a list of report types, however report types are limited by the type of content your iTunes Connect or App Store Connect account can manage:
This option is case-insensitive, can’t be empty or null, and must be either This option is only valid when using request report mode.
These options are for subscription videos only, not for TV or movies. Used in combination, these three options specify:
These options are valid for status mode and lookup metadata mode. For details about details about Universal Media Catalog, see . `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`25 Specifies that you want to receive a new version of Transporter (via automatic software updates) as soon as that version becomes available. Receiving the early access update allows you to test out the new version of Transporter in your testing environment to ensure it works properly with your content processing system. If you do not supply the `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`26 option, you will receive new versions of Transporter later via automatic software updates. `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`27 Specifies the log level you want to use. You can specify one of the following values:
By default, Transporter uses the eXtreme log level. If all transport diagnostics fail, Transporter logs the reason for the failure in the summary information. `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`35
Specifies the vendor identifier for the metadata you want to retrieve. For lookup metadata, status, and statusAll modes, specifies one or more vendor identifiers whose metadata or package upload status you want to retrieve. For createMetadataTicket mode, specifies the vendor identifier for the new metadata ticket. Note:
You can’t use this option with `notarytool`06 or `Package Summary:`3. This option is valid when using lookup metadata, retrieve asset, status, statusAll, query tickets, or create tickets modes. `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`44 Specifies you want Transporter to display progress information when verifying or uploading a package file. You can specify one of the following values:
This option is only valid when using verify or upload modes. `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`53 Specifies whether or not you want Transporter to pause and wait for a keystroke after an error occurs. You can specify one of the following values: `notarytool`35, `notarytool`36. By default, Transporter sets this option to This option is only valid when running a Microsoft Windows operating system. `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`59 Specifies that you want to change the Java Virtual Machine’s (JVM) allocated memory by increasing the JVM heap size. By default, Transporter uses a 2048MB heap size. If you are uploading very large files, or many files at once, you can use For example, to increase the heap size to 4096MB, type: `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`62 Note: A 4096MB heap size specifies that the application will use up to 4096MB of memory, if needed. Standalone options `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`63 Returns the current Transporter version number, copyright information, and acknowledgements. You can enter this parameter by itself as a standalone parameter. For example, type: `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`64 `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`65 Returns the current Transporter version number. You can enter this parameter by itself as a standalone parameter. For example, type: `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`66 Use create artist modeUse create artist mode to create a new music artist. When you run in create artist mode, before creating a new artist, Transporter performs an artist lookup to determine if there are any existing artists with the name specified in `notarytool`83 Note: When you use a force-creation token, Transporter verifies the token, then expires the token 20 minutes after you run create artist mode. You can only use a force-creation token with the exact same artist name, locale, and artist sort name specified in your initial create artist command. In create artist mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, because there was no artist conflict, it returns information indicating that the artist "Jonny Doe" was created. `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`88 For more detailed examples, including Transporter output and logging information, see . Use create tickets modeUse create tickets mode to create new metadata tickets for a track, ringtone, album, or music video you previously uploaded. You can create a metadata ticket for the following fields: album genre, track genre, album title, album title translation, track title, track title translations, album version title, track version title. You must have an iTunes Connect account to use create tickets mode. You can’t use your encoding house username and password with create tickets mode. In create tickets mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
Notes:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to standard error, as well as information about whether or not the metadata ticket was successfully created to change the playlist title. `Package Summary:`24 For more detailed examples, including Transporter output and logging information, see . Use diagnostic modeUse diagnostic mode before you upload packages to check the status and availability of the Apple servers or, if you set the transport mode to HTTP, Aspera, or Signiant, to check the status and availability of the HTTP, Aspera, or Signiant servers. You can also use this mode after an unsuccessful upload attempt to help debug any network connectivity problems between your computer and the Apple servers, or your computer and the HTTP, Aspera, or Signiant servers if you set the transport mode to HTTP, Aspera, or Signiant. When you run in diagnostic mode, Transporter tests the web service and the different hosts and ports based on the `notarytool`3 If you don’t specify a transport option and value, Transporter uses automatic transport discovery to determine the best transport mode for your packages. Currently, Transporter defaults to HTTP as the best transport mode. If the specified transport can’t be used due to errors or server unavailability, Transporter chooses another transport based on the transport preference order. Transporter chooses additional transports until all available transport options are exhausted, at which point the delivery fails. You can specify the delivery methods in the order you want, separated by commas (,). For example, `notarytool`88. If you specify only one transport option (`notarytool`89), Transporter uses that option and if it fails the diagnostic check fails with no fall back options. If you don’t specify a username or password, Transporter performs basic diagnostic tests (for example, testing TCP connectivity). If you specify a username and password, Transporter performs enhanced diagnostic tests (for example, Transporter can more accurately test TCP and UDP connectivity to Signiant and Aspera servers). If all transport diagnostics fail, Transporter logs the reason for the failure in the summary information. In diagnostic mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to the console, as well as diagnostic information regarding the web service and any network connectivity problems between your computer and the Aspera servers. `Package Summary:`40 For more detailed examples, including Transporter output and logging information, see the following sections: Use download installer modeUse download installer mode to download an installer of the latest available version of iTMSTransporter, the Transporter application. For example, you can download the latest version when:
By default, download installer mode downloads the Transporter installer for the current operating system and machine architecture into the current directory. Use command-line options to change the operating system, machine architecture, or destination directory. This mode also displays installation instructions that are specific to the downloaded installer version. In download installer mode, specify these command-line options:
Optionally, you can specify the following additional command-line options:
Use get asset list modeUse get asset list mode to get a JSON-formatted array of assets to be downloaded from Apple. Then use the vendor or public identifiers listed in the array of assets with to download the assets. The public identifier is the `Package Summary:`52 field shown in the sample JSON output below. Dates in the array of assets use the ISO-8601 offset date time format `notarytool`60, for example, `Package Summary:`54. In get asset list mode, you must specify these command-line options:
Optionally, you can specify the following command-line options:
Notes
Sample JSON Output
Use list reports modeUse list reports mode to specify that you want to display a list of all your existing catalog reports for the past 30 days. The report list contains the request date, the name of the user who requested the report (Requested By), content type (for example, Apps or Music), and the status of the report request. In list reports mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to standard error, as well as the list of all the provider’s catalog reports for the past 30 days. ``49 For more detailed examples, including Transporter output and logging information, see . Use list report types modeUse list report types mode to specify that you want to display the list of report content types (for example, Apps or Music) available to you. The report list contains the content type (for example, Apps or Music) and the request date. In list report types mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to standard error, as well as the list of report types available to the provider. ``57 For more detailed examples, including Transporter output and logging information, see and . Use lookup artist modeUse lookup artist mode to specify that you want to download information about music artists, movie cast and crew, or book authors available in the Store. This mode is useful to find details for specific artists; and particularly useful for artists whose names are shared with other artists in other genres or territories. After you retrieve an Apple identifier for a music or movie artist, or book author, you can use the identifier in your Store Package metadata to differentiate between artists with similar names. Use lookup artist mode to find the following details about a specific artist:
In lookup artist mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, it returns information to the console indicating the names, genres, Apple identifiers, and languages associated with the artists who match the search criteria you specified. Transporter returns output information in XML format. ``79 For more detailed examples, including Transporter output and logging information, see , , , and . Use lookup metadata modeUse lookup metadata mode to retrieve the current metadata for a playlist or app you previously uploaded in a Store Package to the iTunes Store, Apple Books, or App Store. This mode is useful when you want to resend the Store Package with updated metadata. If you previously uploaded a package and Apple modified the metadata after your initial upload, you need to retrieve the modified metadata before you can resend the package with metadata updates to the iTunes Store, Apple Books, or App Store. Transporter supports lookup metadata mode for apps that contain up to 1000 In-App Purchases. Using lookup metadata mode, you specify whether you want to search for the metadata by vendor identifier (`notarytool`16) or Apple identifier (`notarytool`06) and Transporter, sending messages to a web service, generates a stub package for the metadata in the directory you specify. You can optionally search for multiple packages at once by specifying multiple vendor identifiers (`Package Summary:`2) or Apple identifiers (`notarytool`06) in a comma-separated list. After Transporter retrieves the current metadata, it creates a stub package, If available, Transporter also returns the following information in the metadata:
Note: If you change the file name, size, or checksum for an asset (for example, artwork files, audio files, video files, EPUB files, and so on), you must supply the new asset file matching the updated file name, size, and checksum. In lookup metadata mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to standard error, as well as creating a stub package containing the current metadata for the 4463953 playlist and saving it to the /tmp/packages directory. `2 package(s) were not uploaded because they had problems:`18 Use `notarytool`75 and `notarytool`76 to look up a subitem. For example, you can look up metadata for:
To lookup metadata for subscription videos, specify the UMC catalog (`2 package(s) were not uploaded because they had problems:`23), content (`2 package(s) were not uploaded because they had problems:`24), and variant (`2 package(s) were not uploaded because they had problems:`25) identifiers.
The following example specifies a single subscription video. `2 package(s) were not uploaded because they had problems:`29`2 package(s) were not uploaded because they had problems:`30 The following example specifies multiple subscription videos. `2 package(s) were not uploaded because they had problems:`31`2 package(s) were not uploaded because they had problems:`32 For more detailed examples, including Transporter output and logging information, see and . Use provider modeUse provider mode to obtain a list of providers for which you have permission to deliver content. This mode is useful not only to verify if you have permission to deliver content for a specific provider, but also to obtain the short name you will use with `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`5 (encoding house user) or `Package Summary:`4 (App Store Connect user) when later uploading content for that provider. For TV and film deliveries, you must use an encoding house account. iTunes Connect users are prohibited. In provider mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to the console, as well as the list of providers for which you have permission to deliver content: `2 package(s) were not uploaded because they had problems:`44 For a more detailed example, including Transporter output and logging information, see . Use query tickets modeUse query tickets mode to retrieve information about all open iTunes tickets that still need your attention. You must have an iTunes Connect account to use query tickets mode. You can’t use your encoding house username and password with query tickets mode. In query tickets mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
To limit the number of tickets returned, specify `notarytool`16 or `notarytool`06. Transporter returns only the tickets associated with the specified id. Note: If you are an encoding house, you shouldn’t use this mode without prior authorization from Apple. For more information, contact your Apple technical representative. In the following example, when Transporter finishes executing the command, it returns eXtreme log information to standard error, as well as information about all open iTunes tickets that still need your attention. Transporter returns output information in XML format. `2 package(s) were not uploaded because they had problems:`62 For more detailed examples, including Transporter output and logging information, see . Use repair assets modeUse repair assets mode to repair some common errors in your asset files before sending them to Apple for upload to Apple Books. Repair assets mode doesn’t modify an existing Store Package. After you repair your asset files using repair assets mode, you must replace the current, un-repaired asset files in the Store Package with the new, repaired asset files and update the xml metadata file (metadata.xml) appropriately. Apple currently only supports EPUB file (.epub) repair. When using repair assets mode, keep the following in mind:
In repair assets mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command it displays information indicating which files in the /tmp/epub directory were repaired and stored in the destination directory (/tmp/epub/repair/), the repaired files checksum information, and eXtreme log information. `2 package(s) were not uploaded because they had problems:`77 For more detailed examples, including Transporter output and logging information, see . Use request report modeUse request report mode to specify that you want to download your catalog reports for one or more content types for the past 30 days. Reports contains the request date, the name of the user who requested the report (Requested By), content type (for example, Apps or Music), the status of the report request, and the path to the downloaded report if a report was downloaded. Requests are restricted to only one request per content type in a 24-hour period. If you requested a report within the last 24 hours, and it is available for download, Transporter immediately downloads the report to the specified directory. If you requested a report within the last 24 hours, and it isn’t available for download, Transporter displays a status message indicating that it isn’t available for download. Otherwise, if you haven’t requested a report within the last 24 hours, Transporter creates a request for a new report. In request report mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to standard error, as well as all of the provider’s catalog reports for the past 30 days. If available, Transporter saves the reports in the /tmp/RequestReport/ directory. `2 package(s) were not uploaded because they had problems:`90 For more detailed examples, including Transporter output and logging information, see . Use retrieve asset modeUse retrieve asset mode to download the assets listed in the JSON-formatted array returned by . The retrieve asset mode downloads each asset file and associated metadata to the output directory. See comments for the `notarytool`55 option. Note: Transporter checks that the file system for the target directory has enough disk space available to write all of the requested files including some overhead. The overhead is equal to the size of the largest file to be downloaded. The assets are first written as encrypted files, then decrypted one at a time. After the decrypted file is written, the encrypted file is removed. In retrieve asset mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
Use schema modeUse schema mode to specify that you want to retrieve either a transitional or strict schema file to use to validate your XML files before packaging and sending them to Apple for upload to the iTunes Store, Apple Books, or App Store. In addition to specifying whether you want to retrieve transitional or strict, you must specify the schema type (for example, music or tv) and version (for example, 3.1 or 3.2) you want to retrieve. You can also specify `notarytool`55 to indicate where you want Transporter to save the schema file. Before submitting the XML metadata, iTunes recommends that you check the file for any structural and formatting errors. iTunes rejects files that contain errors, which can cause delays in the delivery of your content. iTunes has selected Relax NG (RNG) as the schema language for content delivery. To check for errors, you need a tool that validates RNG schema. Note: The schema files are dynamic, and often contain a mixture of schema types (for example, music or tv) in one file. In schema mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
Note: If you specify a static schema (for example, `notarytool`56), the `notarytool`57 command-line option is optional. In the following example, when Transporter finishes executing the command, it returns eXtreme log information to the console. Transporter also returns the transitional schema file for the 4.7 version of the Store Package film specification to the console. ` /Users/bsmith/Applications/Packages/Many/00000000001041.itmsp - Error Messages:`50 For more detailed examples, including Transporter output and logging information, see . Use status modesUse status mode to retrieve status information for one or more of the specified vendor ( Using status mode, you can see the state of your package and whether or not your package has any errors (for example, an internal transfer error or import error). You can also see the vendor or Apple identifier, the content status information (for example, Live, Other, Not Live, In Review), and the content review state (for example, NotLive-WaitingForReview) for your package. In addition, for all content types (music, TV, books, audiobooks, apps, etc.), Transporter displays:
A package might be successfully uploaded to Apple, but still not pass through Apple’s server side process successfully. The status mode options can help you see how your package is doing in Apple’s process. If you are requesting status information for a package containing movie or TV components, status mode also returns component status information in addition to the package status. Component status information is only applicable to movies or TV. For example, for each component (video, audio, full subtitle, etc.), Transporter returns the following information labeled by component type:
If a component is rejected, Transporter returns information to explain the rejection. For example:
If you are requesting status information for a package containing an application or ringtone, status mode returns only upload and content information. Status mode doesn’t support status (On Store, Ready For Store, Not On Store) for applications and ringtones. In status mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to the console, as well as status information for the most recent package the vendor (00028947576600) uploaded. ` /Users/bsmith/Applications/Packages/Many/00000000001041.itmsp - Error Messages:`88 To retrieve status information for subscription videos, specify the UMC catalog (`2 package(s) were not uploaded because they had problems:`23), content (`2 package(s) were not uploaded because they had problems:`24), and variant (`2 package(s) were not uploaded because they had problems:`25) identifiers.
The following example specifies a single subscription video.
The following example specifies multiple subscription videos.
For more detailed examples, including Transporter output and logging information, see , , and . Use transfer test modeUse transfer test mode to test your file transfer performance by uploading a Transporter memory-generated package to the iTunes Store, Apple Books, or App Store. Because the package you send is generated in memory there is no disk I/O during the file transfer and you can therefore remove your disk IO subsystem as a performance factor, helping you better diagnose performance problems. When you test a package for transfer performance, Transporter creates a test package to leverage existing behaviors and statistics. After you successfully upload the package, Transporter displays the total transmission time and details (` /Users/bsmith/Applications/Packages/Many/00000000001041.itmsp - Error Messages:`99) for the package. If upload fails, Transporter returns informational, warning, or error messages indicating the problem. By default, whether you specify In transfer test mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
Note:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to the console, as well as the total transmission time and details (` /Users/bsmith/Applications/Packages/Many/00000000001041.itmsp - Error Messages:`99) for the 10 megabyte package. Transporter uses 10000 Kbit/s throttle speed to transport the specified provider’s file to the Signiant server during upload. ` Unable to find registered encoding house user for username "bsmith" (1001)`25 For more detailed examples, including Transporter output and logging information, see . Use upload modeUse upload mode to deliver your content, in a pre-generated Store Package, to the iTunes Store, Apple Books, or App Store. App upload supports Linux and Windows in addition to macOS. You can use either `Package Summary:`0 or `Package Summary:`1. The `2 package(s) were not uploaded because they had problems:`8 argument is required for Linux and Windows and specifies the file generated by exporting from Xcode (an AppStoreInfo.plist file). See for information on generating that file. If you receive the following message while trying to upload content: ` Unable to find registered encoding house user for username "bsmith" (1001)`29, Apple hasn’t turned on upload access for you. Check with your Apple technical representative and make sure you have been given permission to upload content. Apple recommends you don’t specify the `notarytool`2 and instead allow Transporter to use automatic transport discovery to determine the best transport mode for your packages. Currently, Transporter defaults to HTTP as the best transport mode. If you need to specify `notarytool`2, you should revert back to automatic transport discovery soon as possible. If the specified transport can’t be used due to errors or server unavailability, Transporter chooses another transport based on the transport preference order. Transporter chooses additional transports until all available transport options are exhausted, at which point the delivery fails. You can specify the delivery methods in the order you want, separated by commas (,). For example, `notarytool`88. If you specify only one transport option (`notarytool`89), Transporter uses that option and if it fails the delivery fails with no fall back options. Apple recommends delivering no more than 1000 Store Packages at one time to the iTunes Store, Apple Books, or App Store. In upload mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
Note:
Example: HTTPUsing the HTTP delivery method, you can deliver your content in a pre-generated Store Package to the iTunes Store, Apple Books, or App Store using Apple’s Object Store (HTTP) servers. Transporter includes an integration with HTTPS servers to allow fast delivery of your Store Packages to the iTunes Store, Apple Books, or App Store. HTTP transport is faster doesn't require firewall re-configuration. Note: When delivering Store Packages, Apple recommends you don’t specify the `notarytool`3 command and instead allow Transporter to use automatic transport discovery to determine the best transport mode for your packages. Currently, Transporter defaults to HTTP as the best transport mode. If you do need to specify `notarytool`3, you should revert back to automatic transport discovery soon as possible. To upload all packages in /tmp/files, type: ` Unable to find registered encoding house user for username "bsmith" (1001)`77 In this example, when Transporter finishes executing the command, it returns eXtreme log information to the console and uploads successful packages for the specified provider from the /tmp/files directory. Using Transporter you can specify success and failure directories to help you determine which packages succeeded and which packages failed. To upload all packages in /tmp/files using ` Unable to find registered encoding house user for username "bsmith" (1001)`80 In this example, when Transporter finishes executing the command, it returns eXtreme log information to the console, and the /tmp/files directory is empty. Transporter uploads successful packages for the specified provider from the /tmp/files directory. Successful packages are moved from the source directory into the /tmp/successful_packages directory and those that failed are moved into the /tmp/failed_packages directory. To upload all packages in /tmp/files using ` Unable to find registered encoding house user for username "bsmith" (1001)`83 In this example, when Transporter finishes executing the command, it returns eXtreme log information to the console. Transporter uploads successful packages for the specified provider from the /tmp/files directory. Transporter also displays the throughput details for the successfully uploaded packages and logs the information to the /tmp/loghistory directory. For more detailed examples, including Transporter output and logging, see . Example: AsperaUsing the Aspera delivery method, you can deliver your content in a pre-generated Store Package to the iTunes Store, Apple Books, or App Store using the Aspera server. Transporter includes an embedded integration with the Aspera delivery software to allow fast delivery of your Store Packages to the iTunes Store, Apple Books, or App Store. Aspera’s bulk data transfer technology and file transfer products are built on the FASP file transport. The FASP file transport protocol provides high-speed file transfers over any IP network (LAN, WAN, satellite, wireless, and intercontinental links). When setting up an Aspera integration, if you have outbound and inbound firewall rules, you must open a direct outbound and inbound connection to Transmission Control Protocol (TCP) port 33001 and User Datagram Protocol (UDP) port 33001. UDP “flood protection” in your firewall configuration can cause a UDP time out issue. To avoid the issue, you can create separate firewall rules to allow UDP activities for a longer period of time for Aspera users. For more information, see the Aspera Security Model firewall information at the Aspera website. To upload a package, type: ` Unable to find registered encoding house user for username "bsmith" (1001)`84 In this example, when Transporter finishes executing the command, it returns eXtreme log information to the console. Transporter uses 1000 Kbit/s throttle speed to transport the specified provider’s 10000061918882.itmsp package to the Aspera server during upload. For more detailed examples, including Transporter output and logging, see and . Example: SigniantUsing the Signiant delivery method, you can deliver your content in a pre-generated Store Package to the iTunes Store, Apple Books, or App Store using the Signiant Media Exchange servers. Transporter includes an integration with the Signiant Media Exchange servers to allow fast delivery of your Store Packages to the iTunes Store, Apple Books, or App Store. When setting up a Signiant integration, if you have outbound and inbound firewall rules, you must open a direct outbound and inbound connection to Transmission Control Protocol (TCP) port 44001 and User Datagram Protocol (UDP) ports 44001 through 44101. UDP “flood protection” in your firewall configuration can cause a UDP time out issue. To avoid the issue, you can create separate firewall rules to allow UDP activities for a longer period of time for Signiant users. For more information, see . To upload a package, type: ` Unable to find registered encoding house user for username "bsmith" (1001)`85 In this example, when Transporter finishes executing the command, it returns eXtreme log information to the console. Transporter uses 10000 Kbit/s throttle speed to transport the specified provider’s 10000061918882.itmsp package to the Signiant server during upload. For more detailed examples, including Transporter output and logging, see , , and . Use validate assets modeUse validate assets mode to validate your assets against Apple’s specifications before sending them to Apple for upload to Apple Books. Apple currently only supports EPUB file (.epub) and iBooks format file (.ibooks) validation. In validate assets mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to the console; including information about whether or not each of the specified provider’s asset files in the /tmp/assets directory are valid. ` /Users/bsmith/Applications/Packages/Many/00000000001042.itmsp - Error Messages:`02 For more detailed examples, including Transporter output and logging information, see . Use verify modeUse verify mode to validate your Store Packages, including metadata and assets, against Apple’s specifications before sending them to Apple for upload to the iTunes Store, Apple Books, or App Store. When you send a package to Apple for verification, Transporter parses the metadata file and verifies that the file is well formed and the data is correct, including dates, products, and more. Transporter also validates all assets (for example, audio files, video files, book files, and apps) you send to Apple. In verify mode, you must specify these command-line options:
Optionally, you can specify the following additional command-line options:
In the following example, when Transporter finishes executing the command, it returns eXtreme log information to the console; including information about whether or not each of the specified provider’s packages, files, metadata, and assets in the /tmp/packages directory are valid. ` /Users/bsmith/Applications/Packages/Many/00000000001042.itmsp - Error Messages:`25 For a more detailed example, including Transporter output and logging information, see . Transporter examplesCreate artist modeWhen you run in create artist mode, before creating a new artist, Transporter performs an artist lookup to determine if there are any existing artists with the name specified in `notarytool`83 In the following example, the user, bob, runs Transporter in create artist mode and specifies that Transporter create a new music artist named "Juan Pérez".
Transporter returns information indicating that the artist "Juan Pérez" wasn’t created because the artist already exists. Transporter also returns a force-creation token ("1d82c6f6-26ef-3e28-8a97-558c7c5717da") you can use to force Transporter to create the new music artist. To force Transporter to create the new music artist, add ` /Users/bsmith/Applications/Packages/Many/00000000001042.itmsp - Error Messages:`30 to the command:
Transporter returns information indicating that the artist "Juan Pérez" was created. Create tickets modeIn the following example, the user, bob, runs Transporter in create tickets mode and specifies that Transporter create a metadata ticket for vendor 10000000000255 to change the playlist title to Prince - Greatest Hits, and display eXtreme logging information.
Transporter returns information indicating the metadata ticket was successfully created, and displays eXtreme logging information. Diagnostic modeHTTP, Aspera, and SigniantIn the following example, the user runs Transporter in diagnostic mode without specifying a specific delivery method.
Transporter runs a diagnostic test to check the web service and, because the user didn’t specify a delivery method, Transporter checks the status and availability of all the servers (HTTP, Aspera, and Signiant). In this example, when Transporter finishes executing the command, it displays diagnostic information indicating a successful connection between your computer and the Apple web service and successful connections between your computer and the Apple HTTP, Aspera, and Signiant servers. For example, “TEST RESULT: The transport test succeeded. Able to connect to the host(s)." HTTPIn the following example, the user runs Transporter in diagnostic mode using the HTTP delivery method.
Transporter runs a diagnostic test to check the web service and the status and availability of the Apple HTTP servers. In this example, when Transporter finishes executing the command, it displays diagnostic information indicating a successful connection between your computer and the Apple web service and a successful connection between your computer and the Apple HTTP server. For example, “TEST RESULT: The transport test succeeded for transport: HTTP. Able to connect to the host(s)." AsperaIn the following example, the user runs Transporter in diagnostic mode using the Aspera delivery method, and specifies that Transporter display eXtreme logging information.
Transporter runs a diagnostic test to check the web service and the status and availability of the Aspera servers and displays eXtreme logging information. In this example, when Transporter finishes executing the command, it displays eXtreme logging information, as well as diagnostic information indicating a successful connection between your computer and the Apple web service and a successful connection between your computer and the Aspera servers. For example, “TEST RESULT: The transport test succeeded. Able to connect to the host(s)." SigniantIn the following example, the user runs Transporter in diagnostic mode using the Signiant delivery method, and specifies that Transporter display eXtreme logging information.
Transporter runs a diagnostic test to check the web service and the status and availability of the Signiant servers and displays eXtreme logging information. In this example, when Transporter finishes executing the command, it displays eXtreme logging information, as well as diagnostic information indicating a successful connection between your computer and the Apple web service and a successful connection between your computer and the Signiant servers. For example, “TEST RESULT: The transport test succeeded. Able to connect to the host(s)." UnauthenticatedIn the following example, the user runs Transporter in diagnostic mode using without specifying a specific delivery method, username, or password.
Transporter runs a diagnostic test to check the web service and, because the user didn’t specify a delivery method, username, or password, Transporter performs basic diagnostic testing of TCP connectivity. In this example, when Transporter finishes executing the command, it displays diagnostic information indicating successful TCP connectivity. For example, “TEST RESULT: The transport test succeeded. Able to connect to the host(s)." List reports modeIn the following example, the user, bob, runs Transporter in list reports mode and specifies that Transporter list all the provider’s catalog reports for the past 30 days.
Transporter returns the list of all the provider’s catalog reports for the past 30 days, and displays eXtreme logging information. In this example, Transporter displays the request date (03/21/2013 12:11 PDT), the name of the user who requested the report (bob), content type (TV Show), and the status (Succeeded) indicating the report request was a success. List report types modeReport types for a TV providerIn the following example, the user, bob, runs Transporter in list report types mode and specifies that Transporter display the list of his available report content types (for example, Apps or Music).
Transporter returns the list of report types available for bob, a TV provider. In this example, Transporter displays one report type available to bob (TV Show) and the request date (2014-07-10 17:38:23 PDT). Report types for an app developerIn the following example, the user, bob, runs Transporter in list report types mode and specifies that Transporter display the list of his available report content types (for example, Apps or Music), and display the returned output information as XML.
Transporter returns the list of report types available for bob, an app provider, and returns the output information as XML. In this example, Transporter displays three report types available to bob (Apps, Game Center Leaderboard Metadata, Game Center Achievement Metadata) and the request date (2014-07-10 17:43:06 PDT). Lookup artist modeLookup artist modeIn the following example, the user, bob, runs Transporter in lookup artist mode to search for artists with the name John Appleseed, and specifies that Transporter not display any logging information. `notarytool`719`notarytool`720 When Transporter finishes executing the command it displays information about the artists who matched the specified search term, without any additional logging information. In this example, two artists match the John Appleseed search term:
You can use the Apple identifiers in the album artists and track artists block of a music Store Package to precisely specify the intended artist. For more information, see the section in the iTunes Package Music Specification. Lookup artist mode for music artists (displaying XML output)In the following example, the user, bob, runs Transporter in lookup artist mode to search for artists with the name John Appleseed and display the returned output information as XML, and specifies that Transporter not display any logging information. `notarytool`721`notarytool`693`notarytool`694`notarytool`724`notarytool`725`notarytool`726`notarytool`727`notarytool`728`notarytool`729`notarytool`730`notarytool`731`notarytool`732`notarytool`733`notarytool`734`notarytool`735`notarytool`736`notarytool`737`notarytool`738`notarytool`739`notarytool`740`notarytool`741`notarytool`742`notarytool`743`notarytool`744`notarytool`745`notarytool`746`notarytool`747`notarytool`748`notarytool`749`notarytool`742`notarytool`751`notarytool`752`notarytool`745`notarytool`746`notarytool`747`notarytool`748`notarytool`749`notarytool`742`notarytool`759`notarytool`760`notarytool`745`notarytool`746`notarytool`747`notarytool`748`notarytool`749`notarytool`742`notarytool`767`notarytool`768`notarytool`745`notarytool`746`notarytool`747`notarytool`748`notarytool`749`notarytool`742`notarytool`775`notarytool`776`notarytool`745`notarytool`746`notarytool`747`notarytool`748`notarytool`749`notarytool`742`notarytool`783`notarytool`784`notarytool`745`notarytool`746`notarytool`747`notarytool`748`notarytool`749`notarytool`742`notarytool`791`notarytool`792`notarytool`745`notarytool`746`notarytool`747`notarytool`748`notarytool`749`notarytool`742`notarytool`799`notarytool`800`notarytool`745`notarytool`746`notarytool`747`notarytool`748`notarytool`749`notarytool`742`notarytool`807`notarytool`808`notarytool`745`notarytool`746`notarytool`811`notarytool`748`notarytool`749`notarytool`742`notarytool`815`notarytool`816`notarytool`745`notarytool`746`notarytool`747`notarytool`748`notarytool`749`notarytool`742`notarytool`823`notarytool`824`notarytool`745`notarytool`746`notarytool`747`notarytool`748`notarytool`749`notarytool`830`notarytool`831`notarytool`832`notarytool`833`notarytool`834`notarytool`835`notarytool`836`notarytool`837`notarytool`835`notarytool`839`notarytool`840`notarytool`835`notarytool`842`notarytool`843`notarytool`835`notarytool`845`notarytool`846`notarytool`847`notarytool`848`notarytool`849`notarytool`850`notarytool`746`notarytool`852`notarytool`748`notarytool`854`notarytool`855`notarytool`856`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`863`notarytool`746`notarytool`865`notarytool`748`notarytool`854`notarytool`855`notarytool`856`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`876`notarytool`746`notarytool`878`notarytool`748`notarytool`854`notarytool`855`notarytool`882`notarytool`857`notarytool`861`notarytool`862`notarytool`886`notarytool`746`notarytool`888`notarytool`748`notarytool`854`notarytool`855`notarytool`892`notarytool`857`notarytool`861`notarytool`862`notarytool`896`notarytool`746`notarytool`898`notarytool`748`notarytool`854`notarytool`855`notarytool`892`notarytool`857`notarytool`861`notarytool`862`notarytool`906`notarytool`907`notarytool`908`notarytool`726`notarytool`727`notarytool`728`notarytool`732`notarytool`913`notarytool`734`notarytool`735`notarytool`916`notarytool`737`notarytool`738`notarytool`919`notarytool`740`notarytool`831`notarytool`922`notarytool`833`notarytool`834`notarytool`925`notarytool`836`notarytool`837`notarytool`835`notarytool`839`notarytool`840`notarytool`835`notarytool`842`notarytool`843`notarytool`835`notarytool`845`notarytool`849`notarytool`937`notarytool`746`notarytool`939`notarytool`748`notarytool`854`notarytool`855`notarytool`856`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`950`notarytool`746`notarytool`952`notarytool`748`notarytool`854`notarytool`855`notarytool`856`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`906`notarytool`907`notarytool`965`notarytool`717 When Transporter finishes executing the command it displays information about the artists who matched the specified search term, without any additional logging information. In this example, two artists match the John Appleseed search term:
You can use the Apple identifiers in the album artists and track artists block of a music Store Package to precisely specify the intended artist. For more information, see the section in the iTunes Package Music Specification. Lookup artist mode for movie artistsThis example shows a lookup artist mode for movie artists. Lookup artist with -outputFormat of XML now includes:
To lookup a movie artist, specify the `notarytool`967 Note that if you do not supply `notarytool`19, it will default to Music. The following is a sample for looking up "Steven Spielberg" using columnar output. (The role and localization information will only appear in the xml output format.) `notarytool`969 This is the sample output for Steven Spielberg in xml format: `notarytool`970`notarytool`693`notarytool`694`notarytool`973`notarytool`974`notarytool`975`notarytool`976`notarytool`977`notarytool`978`notarytool`979`notarytool`980`notarytool`981`notarytool`982`notarytool`983`notarytool`984`notarytool`985`notarytool`986`notarytool`987`notarytool`988`notarytool`989`notarytool`990`notarytool`991`notarytool`992`notarytool`993`notarytool`994`notarytool`995`notarytool`996`notarytool`997`notarytool`998`notarytool`991`notarytool`000`notarytool`001`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`008`notarytool`009`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`016`notarytool`017`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`024`notarytool`025`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`032`notarytool`033`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`040`notarytool`041`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`048`notarytool`049`notarytool`994`notarytool`995`notarytool`052`notarytool`997`notarytool`998`notarytool`991`notarytool`056`notarytool`057`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`064`notarytool`065`notarytool`994`notarytool`995`notarytool`068`notarytool`997`notarytool`998`notarytool`991`notarytool`072`notarytool`073`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`080`notarytool`081`notarytool`994`notarytool`995`notarytool`084`notarytool`997`notarytool`998`notarytool`991`notarytool`088`notarytool`089`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`096`notarytool`097`notarytool`994`notarytool`995`notarytool`100`notarytool`997`notarytool`998`notarytool`991`notarytool`104`notarytool`105`notarytool`994`notarytool`995`notarytool`108`notarytool`997`notarytool`998`notarytool`991`notarytool`112`notarytool`113`notarytool`994`notarytool`995`notarytool`116`notarytool`997`notarytool`998`notarytool`991`notarytool`120`notarytool`121`notarytool`994`notarytool`995`notarytool`124`notarytool`997`notarytool`998`notarytool`991`notarytool`128`notarytool`129`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`136`notarytool`137`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`991`notarytool`144`notarytool`145`notarytool`994`notarytool`995`notarytool`004`notarytool`997`notarytool`998`notarytool`151`notarytool`152`notarytool`153`notarytool`154`notarytool`155`notarytool`156`notarytool`157`notarytool`158`notarytool`159`notarytool`995`notarytool`161`notarytool`997`notarytool`163`notarytool`164`notarytool`165`notarytool`166`notarytool`167`notarytool`168`notarytool`169`notarytool`995`notarytool`171`notarytool`997`notarytool`163`notarytool`164`notarytool`175`notarytool`166`notarytool`167`notarytool`168`notarytool`179`notarytool`995`notarytool`181`notarytool`997`notarytool`163`notarytool`164`notarytool`165`notarytool`166`notarytool`167`notarytool`168`notarytool`189`notarytool`995`notarytool`191`notarytool`997`notarytool`163`notarytool`164`notarytool`165`notarytool`166`notarytool`167`notarytool`168`notarytool`199`notarytool`995`notarytool`201`notarytool`997`notarytool`163`notarytool`164`notarytool`165`notarytool`166`notarytool`167`notarytool`168`notarytool`209`notarytool`210`notarytool`211`notarytool`717 When Transporter finishes executing the command it displays information about the artist(s) who matched the specified search term, without any additional logging information. In this example, only one artist matched the Steven Spielberg search term. You can use the Apple identifiers in the `notarytool`213 or `notarytool`214 block of a film Store Package to precisely specify the intended artist. For more information, see the section in the iTunes Package Film Specification. Lookup artist mode for movie artists (displaying XML output with non-ASCII characters)This example shows a lookup artist mode for movie artists with the command-line option `notarytool`66 set to `notarytool`36. This option includes non-ASCII characters in the XML output. Note: Specifying `notarytool`73 may not work correctly on the Microsoft Windows platform. `notarytool`218`notarytool`693`notarytool`694`notarytool`221`notarytool`222`notarytool`223`notarytool`224`notarytool`225`notarytool`226`notarytool`227`notarytool`228`notarytool`229`notarytool`230`notarytool`231`notarytool`232`notarytool`233`notarytool`234`notarytool`235`notarytool`236`notarytool`237`notarytool`238`notarytool`239`notarytool`240`notarytool`241`notarytool`242`notarytool`243`notarytool`244`notarytool`245`notarytool`246`notarytool`239`notarytool`248`notarytool`249`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`256`notarytool`257`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`264`notarytool`265`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`272`notarytool`273`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`280`notarytool`281`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`288`notarytool`289`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`296`notarytool`297`notarytool`242`notarytool`243`notarytool`300`notarytool`245`notarytool`246`notarytool`239`notarytool`304`notarytool`305`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`312`notarytool`313`notarytool`242`notarytool`243`notarytool`316`notarytool`245`notarytool`246`notarytool`239`notarytool`320`notarytool`321`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`328`notarytool`329`notarytool`242`notarytool`243`notarytool`332`notarytool`245`notarytool`246`notarytool`239`notarytool`336`notarytool`337`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`344`notarytool`345`notarytool`242`notarytool`243`notarytool`348`notarytool`245`notarytool`246`notarytool`239`notarytool`352`notarytool`353`notarytool`242`notarytool`243`notarytool`356`notarytool`245`notarytool`246`notarytool`239`notarytool`360`notarytool`361`notarytool`242`notarytool`243`notarytool`364`notarytool`245`notarytool`246`notarytool`239`notarytool`368`notarytool`369`notarytool`242`notarytool`243`notarytool`372`notarytool`245`notarytool`246`notarytool`239`notarytool`376`notarytool`377`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`384`notarytool`385`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`392`notarytool`393`notarytool`242`notarytool`243`notarytool`252`notarytool`245`notarytool`246`notarytool`239`notarytool`400`notarytool`353`notarytool`242`notarytool`243`notarytool`404`notarytool`245`notarytool`246`notarytool`407`notarytool`408`notarytool`409`notarytool`410`notarytool`411`notarytool`412`notarytool`413`notarytool`414`notarytool`415`notarytool`243`notarytool`417`notarytool`245`notarytool`419`notarytool`420`notarytool`421`notarytool`422`notarytool`423`notarytool`424`notarytool`425`notarytool`243`notarytool`427`notarytool`245`notarytool`419`notarytool`420`notarytool`431`notarytool`422`notarytool`423`notarytool`424`notarytool`435`notarytool`243`notarytool`437`notarytool`245`notarytool`419`notarytool`420`notarytool`421`notarytool`422`notarytool`420`notarytool`444`notarytool`422`notarytool`423`notarytool`424`notarytool`448`notarytool`243`notarytool`450`notarytool`245`notarytool`419`notarytool`420`notarytool`421`notarytool`422`notarytool`420`notarytool`444`notarytool`422`notarytool`423`notarytool`424`notarytool`461`notarytool`243`notarytool`463`notarytool`245`notarytool`419`notarytool`420`notarytool`421`notarytool`422`notarytool`423`notarytool`424`notarytool`471`notarytool`472`notarytool`473`notarytool`717 Lookup artist mode for book authorsThis example shows a lookup artist mode for books. Lookup artist with -outputFormat of XML now includes:
To lookup a book artist, specify the `notarytool`475 Note that if you do not supply `notarytool`19, it will default to Music. The following is a sample for looking up "William Shakespeare" using columnar output. (The role and localization information will only appear in the xml output format.) `notarytool`477 This is the sample output for William Shakespeare in xml format: `notarytool`478`notarytool`693`notarytool`694`notarytool`724`notarytool`725`notarytool`726`notarytool`484`notarytool`728`notarytool`729`notarytool`487`notarytool`731`notarytool`732`notarytool`490`notarytool`734`notarytool`735`notarytool`493`notarytool`737`notarytool`495`notarytool`919`notarytool`740`notarytool`741`notarytool`742`notarytool`815`notarytool`816`notarytool`745`notarytool`746`notarytool`504`notarytool`748`notarytool`749`notarytool`742`notarytool`775`notarytool`776`notarytool`745`notarytool`746`notarytool`512`notarytool`748`notarytool`749`notarytool`742`notarytool`807`notarytool`808`notarytool`745`notarytool`746`notarytool`520`notarytool`748`notarytool`749`notarytool`830`notarytool`831`notarytool`525`notarytool`833`notarytool`834`notarytool`925`notarytool`836`notarytool`837`notarytool`835`notarytool`839`notarytool`846`notarytool`534`notarytool`848`notarytool`849`notarytool`537`notarytool`746`notarytool`539`notarytool`748`notarytool`854`notarytool`855`notarytool`543`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`550`notarytool`746`notarytool`552`notarytool`748`notarytool`854`notarytool`855`notarytool`543`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`563`notarytool`746`notarytool`565`notarytool`748`notarytool`854`notarytool`855`notarytool`543`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`576`notarytool`746`notarytool`578`notarytool`748`notarytool`854`notarytool`854`notarytool`855`notarytool`543`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`590`notarytool`746`notarytool`592`notarytool`748`notarytool`854`notarytool`855`notarytool`543`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`603`notarytool`746`notarytool`605`notarytool`748`notarytool`854`notarytool`855`notarytool`543`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`616`notarytool`746`notarytool`618`notarytool`748`notarytool`854`notarytool`855`notarytool`543`notarytool`857`notarytool`855`notarytool`859`notarytool`857`notarytool`861`notarytool`862`notarytool`906`notarytool`907`notarytool`965`notarytool`717 When Transporter finishes executing the command it displays information about the artist(s) who matched the specified search term, without any additional logging information. In this example, only one artist matched the William Shakespeare search term. You can use the Apple identifiers in the `notarytool`633 block of a Apple Books Package to precisely specify the intended author. For more information, see the section in the Apple Books Book Package Specification . Lookup artist mode for book authors (displaying XML output with non-ASCII characters)This example shows a lookup artist mode for book authors with the command-line option `notarytool`66 set to `notarytool`36. This option includes non-ASCII characters in the XML output. Note: Specifying `notarytool`73 may not work correctly on the Microsoft Windows platform. `notarytool`637`notarytool`693`notarytool`694`notarytool`221`notarytool`222`notarytool`223`notarytool`643`notarytool`225`notarytool`226`notarytool`646`notarytool`228`notarytool`229`notarytool`649`notarytool`231`notarytool`232`notarytool`652`notarytool`234`notarytool`235`notarytool`236`notarytool`237`notarytool`238`notarytool`239`notarytool`344`notarytool`345`notarytool`242`notarytool`243`notarytool`663`notarytool`245`notarytool`246`notarytool`239`notarytool`352`notarytool`353`notarytool`242`notarytool`243`notarytool`671`notarytool`245`notarytool`246`notarytool`239`notarytool`360`notarytool`361`notarytool`242`notarytool`243`notarytool`679`notarytool`245`notarytool`246`notarytool`239`notarytool`240`notarytool`241`notarytool`242`notarytool`243`notarytool`687`notarytool`245`notarytool`246`notarytool`239`notarytool`312`notarytool`313`notarytool`242`notarytool`243`notarytool`695`notarytool`245`notarytool`246`notarytool`239`notarytool`280`notarytool`281`notarytool`242`notarytool`243`notarytool`679`notarytool`245`notarytool`246`notarytool`239`notarytool`707`notarytool`708`notarytool`242`notarytool`243`notarytool`679`notarytool`245`notarytool`246`notarytool`239`notarytool`715`notarytool`321`notarytool`242`notarytool`243`notarytool`679`notarytool`245`notarytool`246`notarytool`239`notarytool`723`notarytool`724`notarytool`242`notarytool`243`notarytool`679`notarytool`245`notarytool`246`notarytool`239`notarytool`731`notarytool`732`notarytool`242`notarytool`243`notarytool`679`notarytool`245`notarytool`246`notarytool`239`notarytool`296`notarytool`297`notarytool`242`notarytool`243`notarytool`679`notarytool`245`notarytool`246`notarytool`239`notarytool`352`notarytool`353`notarytool`242`notarytool`243`notarytool`671`notarytool`245`notarytool`246`notarytool`239`notarytool`755`notarytool`756`notarytool`242`notarytool`243`notarytool`679`notarytool`245`notarytool`246`notarytool`407`notarytool`408`notarytool`764`notarytool`410`notarytool`411`notarytool`767`notarytool`413`notarytool`414`notarytool`770`notarytool`243`notarytool`772`notarytool`245`notarytool`419`notarytool`420`notarytool`776`notarytool`422`notarytool`420`notarytool`779`notarytool`422`notarytool`423`notarytool`424`notarytool`471`notarytool`472`notarytool`473`notarytool`717 Lookup metadata modeLookup metadata mode (single Store Package)In the following example, the user, bob, runs Transporter in lookup metadata mode and specifies that Transporter create a stub package containing the current metadata for the Apple 4463953 playlist and save the package to the /tmp/packages directory, and display informational logging information. The example also shows the contents of the /tmp/packages directory before and after bob executes the iTMSTransporter command so you can see that Transporter created the metadata.xml file and stored it in the new 4463953.itmsp stub package in the directory. `notarytool`787`notarytool`788`notarytool`789`notarytool`790`notarytool`791`notarytool`792`notarytool`793`notarytool`794`notarytool`795`notarytool`796`notarytool`797`notarytool`798`notarytool`799`notarytool`800`notarytool`801`notarytool`802`notarytool`803`notarytool`804`notarytool`805`notarytool`787`notarytool`788`notarytool`808`notarytool`809`notarytool`810`notarytool`811`notarytool`812`notarytool`813`notarytool`814`notarytool`815 Transporter retrieves the current metadata for the playlist, creates a new 4463953.itmsp stub package consisting of a single metadata.xml file, stores the stub package in the tmp/packages directory, and displays informational logging information. In this example, Transporter displays information indicating it retrieved the metadata and created the stub package successfully: “Looking up the metadata and creating a stub package for it is done." The example also shows the contents of the /tmp/packages directory before and after bob executes the iTMSTransporter command so you can see that Transporter created the metadata.xml file and stored it in the new 4463953.itmsp stub package in the directory. Lookup metadata mode (multiple Store Packages)In the following example, the user, bob, runs Transporter in lookup metadata mode and specifies that Transporter create a stub package containing the current metadata for the Apple playlists with Apple identifiers 4463953 and 4463954. Transporter saves the package to the /tmp/packages directory, and display informational logging information. The example also shows the contents of the /tmp/packages directory before and after bob executes the iTMSTransporter command so you can see that Transporter created the metadata.xml files and stored the files in the new 4463953.itmsp and 4463954.itmsp stub packages in the directory. `notarytool`787`notarytool`788`notarytool`789`notarytool`790`notarytool`820`notarytool`821`notarytool`822`notarytool`823`notarytool`824`notarytool`825`notarytool`826`notarytool`827`notarytool`828`notarytool`829`notarytool`830`notarytool`831`notarytool`832`notarytool`833`notarytool`834`notarytool`835`notarytool`836`notarytool`837`notarytool`804`notarytool`839`notarytool`787`notarytool`788`notarytool`808`notarytool`809`notarytool`810`notarytool`845`notarytool`811`notarytool`812`notarytool`813`notarytool`814`notarytool`815 Transporter retrieves the current metadata for the playlist, creates new 4463953.itmsp and 4463954.itmsp stub packages consisting of a single metadata.xml file, stores the stub packages in the tmp/packages directory, and displays informational logging information. In this example, Transporter displays information indicating it retrieved the metadata and created the stub packages successfully: “Looking up the metadata and creating a stub package for it is done." The example also shows the contents of the /tmp/packages directory before and after bob executes the iTMSTransporter command so you can see that Transporter created the metadata.xml files and stored the files in the new 4463953.itmsp and 4463954.itmsp stub packages in the directory. Lookup metadata mode (single subscription video)In the following example, the user, jappleseed, runs Transporter in lookup metadata mode and specifies the Universal Media Catalog values for the catalog ID, content ID, and variant ID for a single subscription video. `notarytool`851`notarytool`852`notarytool`853`notarytool`854`notarytool`855`notarytool`856`notarytool`857`notarytool`858`notarytool`859`notarytool`860`notarytool`861`notarytool`862`notarytool`863`notarytool`864`notarytool`865`notarytool`866`notarytool`867`notarytool`868`notarytool`869`notarytool`870`notarytool`871`notarytool`872`notarytool`873`notarytool`874`notarytool`875`notarytool`876`notarytool`877`notarytool`878`notarytool`879`notarytool`880`notarytool`881`notarytool`882`notarytool`883`notarytool`884`notarytool`885`notarytool`886`notarytool`887`notarytool`888`notarytool`889`notarytool`890`notarytool`891`notarytool`892`notarytool`893`notarytool`894`notarytool`895`notarytool`896`notarytool`897`notarytool`872`notarytool`875`notarytool`877`notarytool`901`notarytool`902`notarytool`880`notarytool`881`notarytool`882`notarytool`906`notarytool`907`notarytool`908`notarytool`886`notarytool`887`notarytool`888`notarytool`889`notarytool`890`notarytool`891`notarytool`892`notarytool`916`notarytool`894`notarytool`895`notarytool`919`notarytool`897`notarytool`921`notarytool`922`notarytool`923`notarytool`924`notarytool`925`notarytool`926`notarytool`927`notarytool`928`notarytool`929`notarytool`930`notarytool`931`notarytool`932`notarytool`933`notarytool`804`notarytool`935 Lookup metadata mode (multiple subscription videos)In the following example, the user, jappleseed, runs Transporter in lookup metadata mode and specifies the Universal Media Catalog values for the catalog ID, content ID, and variant ID for two subscription videos.
Provider modeIn the following example, the user, bob, runs Transporter in provider mode and specifies that Transporter not display any logging information.
When Transporter finishes executing the command it displays a list containing the long and short name of providers for which bob has permission to deliver content, without any additional logging information. In this example, bob has permission to deliver content for one provider: Apple Computer (Long Name), Apple (Short Name). When uploading assets for this provider, you use the short name (Apple) with the `“Delivered file set does not contain expected file [34D17614CB805E8AB853CD5ABCBF3C0A-940AE112-01-18-mp4-128000.m4a] that is referenced in the metadata file”`5 option. Query tickets modeIn the following example, the user, bob, runs Transporter in query tickets mode and specifies that Transporter return information about all open iTunes tickets that still require attention, and display eXtreme logging information.
Transporter returns information on all your open iTunes tickets that still require attention, and displays eXtreme logging information. In this example, Transporter displays information for 2 open tickets (ticketId=97202 and ticketId=135986) and provides details on what actions need to be taken (“The wrong cover art has been submitted for this album." and “Wrong cover art. Album title and artist name do not match.”). Repair assets modeIn the following example, the user runs Transporter in repair assets mode and specifies that Transporter repair the unmanifested.epub EPUB file, remove unmanifested files from your EPUB files before you send your asset files to Apple for upload to Apple Books, and store the repaired file in the /tmp/repairEpubAssetsUnmanifested/ directory.
Transporter attempts to repair the unmanifested.epub EPUB file, remove unmanifested files from your EPUB files, and store the repaired file in the /tmp/repairEpubAssetsUnmanifested/ directory. When Transporter finishes executing the command it displays information indicating whether it could repair the file or not. In this example, Transporter repaired the unmanifested.epub EPUB file. Transporter displays the repaired file path (/tmp/repairEpubAssetsUnmanifested/unmanifested.epub) and checksum (8dd1e064ae5cdde7b1b3c8d766db92ee). Request report modeIn the following example, the user, bob, runs Transporter in request report mode and specifies that Transporter download all the provider’s catalog reports for the past 30 days.
Transporter downloads all the provider’s catalog reports for the past 30 days to the /tmp/ directory, and displays eXtreme logging information. In this example, Transporter indicates that the following catalog reports were downloaded to the /tmp/ directory: Apple_TV.ljjwjfgf.zip and Apple_TV.ljjwjfgf.zip. Schema modeIn the following example, the user, bob, runs Transporter in schema mode and specifies that Transporter return the transitional schema file for the 4.7 version of the Store Package film specification, save the schema file to the /tmp/schema directory, and display eXtreme logging information.
Transporter returns the transitional schema file for the 4.7 version of the Store Package film specification, and displays eXtreme logging information. In this example, Transporter saves the transitional schema file in /tmp/schema/film4.7-transitional.rng. Status modesStatus mode (music example)In the following example, the user, bob, runs Transporter in status mode and specifies that Transporter return status information for the most recently uploaded package for the given Apple identifier.
Transporter returns status information for the most recently uploaded package for the given Apple identifier. Status mode (video example)In the following example, the user, bob, runs Transporter in status mode and specifies that Transporter return status information for the most recently uploaded package for the given Apple identifier.
Transporter returns status information for the most recently uploaded package for the given Apple identifier. In this example, since the package you are requesting status for contains a video, status mode also returns component status information (name, locale, status, delivered, rejection reason and note, if applicable) for each video component (thumbnails, subtitles, audio captions, chapters, dub credit, video, preview) in addition to the package status. Status mode (specifying a list of identifiers)In the following example, the user, bob, runs Transporter in status mode and specifies that Transporter return status information for the most recently uploaded packages for the comma-separated list of vendor identifiers, and display the returned output information as XML.
Transporter returns status information for the most recently uploaded packages for the comma-separated list of vendor identifiers (98143907070932,98143907070931), and returns the output information as XML. In this example, Transporter returns an Upload Failed status for vendor identifier 98143907070932 and a final upload status of Imported for vendor identifier 98143907070931. StatusAll modeIn the following example, the user, bob, runs Transporter in statusAll mode and specifies that Transporter return status information for all uploaded packages for the given Apple identifier, and display the returned output information as XML.
Transporter returns status information for all uploaded packages for the given Apple identifier, and returns the output information as XML. In this example, since the package you are requesting status for contains a movie, status mode also returns component status information (name, locale, status, delivered) for each movie component (captions, video, audio, chapters, thumbnails) in addition to the package status. StatusAll mode (specifying a list of identifiers)In the following example, the user, bob, runs Transporter in statusAll mode and specifies that Transporter return status information for all uploaded packages for the comma-separated list of vendor identifiers, and display the returned output information as XML.
Transporter returns status information for all uploaded packages for the comma-separated list of vendor identifiers, and returns the output information as XML. In this example, Transporter returns a final upload status of Import Error for vendor identifier 98143907070936 and Import Error for vendor identifier 98143907070937. Transfer test modeIn the following example, the user, bob, runs Transporter in transfer test mode and specifies that Transporter use 10000 Kbit/s throttle speed to upload the 10 megabyte package to the Signiant server, return the total transmission time and details (-throughput), and display eXtreme logging information.
Transporter uses 10000 Kbit/s throttle speed to upload the 10 megabyte package to the Signiant server, displays the package metadata, the total transmission time and details (-throughput), and displays eXtreme logging information. When Transporter finishes executing the command it displays information indicating whether it could successfully upload the file or not. In this example, Transporter displays information indicating one 10 megabyte package was uploaded successfully (APPLE2812F6A232B944FD91CCA2C10A1F0C8C.itmsp) with a total transmission time of 15839 ([2014-03-14 12:30:51 PDT] Upload modeApp upload using Linux or WindowsIn the following example, the user runs Transporter in upload mode to upload an app from a Linux machine. The example uses `Package Summary:`0 to specify the app file and `2 package(s) were not uploaded because they had problems:`8 to specify the AppStoreInfo.plist file generated by Xcode.
App upload using macOS with -assetFileIn the following example, the user runs Transporter in upload mode to upload an iOS app on macOS. The example uses `Package Summary:`0 to specify the app file. The `2 package(s) were not uploaded because they had problems:`8 option is optional on macOS. The `Package Summary:`0 option specifies either an iOS .ipa or a macOS .pkg file which is the result of an Xcode build. The example below is for an iOS application called MyApp. This example is being sent by a multi-provider user, so the `Package Summary:`4 option is required. It is optional if the user is not a multi-provider user who should use `Package Summary:`59 instead.
App upload using API Key on LinuxThis example shows how to upload an iOS app from a Linux machine using an API key. The example uses `Package Summary:`5 option to specify the name of the API key and `Package Summary:`6 to specify the software provider’s unique identifier (see Issuer ID on the API Keys tab on App Store Connect. Note that for windows the command should be `Package Summary:`786 instead of `Package Summary:`787.
App upload using JWT on LinuxThis example shows how to upload an app from a Linux machine using JWT. The example uses ` /Users/bsmith/Applications/Packages/Many/00000000001041.itmsp - Error Messages:`8 option to specify the JSON Web token (JWT). You can generate the JWT with the private key downloaded from the API Keys tab on App Store Connect and use an external tool or library that can be found at https://jwt.io. Note that for windows the command should be `Package Summary:`786 instead of `Package Summary:`787.
AsperaIn the following example, the user, bob, runs Transporter in upload mode and specifies that Transporter use 100000 Kbit/s throttle speed to upload all Apple packages in the /tmp/packages directory to the Aspera server, and display eXtreme logging information.
Transporter uses 100000 Kbit/s throttle speed to upload successful Apple packages in the /tmp/packages directory to the Aspera server, displays the package metadata, and displays eXtreme logging information. When Transporter finishes executing the command it displays information indicating whether it could successfully upload packages or not. In this example, Transporter displays information indicating one package was uploaded successfully (98143907081232.itmsp). Aspera on WindowsIn the following example, the user, bob, runs Transporter in upload mode and specifies that Transporter use 200000 Kbit/s throttle speed to upload all Apple packages in the C:\Transporter-Package directory to the Aspera server, display the throughput time and details for the successfully uploaded packages, and display eXtreme logging information.
Transporter uses 200000 Kbit/s throttle speed to upload successful Apple packages in the C:\Transporter-Package directory to the Aspera server, display the package metadata, display the throughput time and details for the successfully uploaded packages, and display eXtreme logging information. When Transporter finishes executing the command it displays information indicating whether it could successfully upload packages or not. In this example, Transporter displays information indicating one package was uploaded successfully (98143907091223.itmsp). Transporter displays the throughput information for the successful package (0 minutes, 49.92 seconds, 13.01MB, 266.89KB/sec). HTTPIn the following example, the user, bob, runs Transporter in upload mode and specifies that Transporter upload a package in the private/tmp/outputFiles/ directory to the HTTP server, and display eXtreme logging information. In this example, the -t command (to specify the transport delivery method) is omitted; Transporter will use HTTP by default.
Transporter uploads the successful Apple package in the /private/tmp/outputFiles directory to the HTTP server, displays the package metadata, and displays eXtreme logging information, including warnings. When Transporter finishes executing the command, it displays information indicating whether it could successfully upload packages or not. In this example, Transporter displays information indicating one package was uploaded successfully (BasicSingle-Apple-US-10215/10000000010215.itmsp) to the HTTP server. SigniantIn the following example, the user, bob, runs Transporter in upload mode and specifies that Transporter use 100000 Kbit/s throttle speed to upload all Apple packages in the /tmp/packages directory to the Signiant server, and display eXtreme logging information.
Transporter uses 100000 Kbit/s throttle speed to upload successful Apple packages in the /tmp/packages directory to the Signiant server, displays the package metadata, and displays eXtreme logging information. When Transporter finishes executing the command it displays information indicating whether it could successfully upload packages or not. In this example, Transporter displays information indicating one package was uploaded successfully (98143907081233.itmsp). Signiant on WindowsIn the following example, the user, bob, runs Transporter in upload mode and specifies that Transporter upload an Apple package in the C:\Transporter-Package directory to the Signiant server, and display eXtreme logging information.
Transporter uploads successful Apple packages in the C:\Transporter-Package directory to the Signiant server, displays the package metadata, and displays eXtreme logging information. When Transporter finishes executing the command it displays information indicating whether it could successfully upload packages or not. In this example, Transporter displays information indicating one package was uploaded successfully (98143907091223.itmsp). Signiant (failing over to Aspera)In the following example, the user, bob, runs Transporter in upload mode and specifies that Transporter use 200000 Kbit/s throttle speed to upload all Apple packages in the /tmp/packages directory to the Signiant server, with only the Aspera delivery method as the fall back, and display eXtreme logging information.
Transporter uses 200000 Kbit/s throttle speed and attempts to upload successful Apple packages in the /tmp/packages directory to the Signiant server. When the Signiant delivery method fails, Transporter fails over to the Aspera delivery method and uses 200000 Kbit/s throttle speed to upload successful Apple packages in the /tmp/packages directory to the Aspera server, displays the package metadata, and displays eXtreme logging information. When Transporter finishes executing the command it displays information indicating whether it could successfully upload packages or not. In this example, Transporter displays information indicating one package was uploaded successfully (98143907099229.itmsp). Validate assets modeIn the following example, the user, bob, runs Transporter in validate assets mode and specifies that Transporter verify the 9780446564212.epub, 9780759574731.epub, and 9781599953120.epub EPUB files and display eXtreme logging information.
Transporter attempts to verify the 9780446564212.epub, 9780759574731.epub, and 9781599953120.epub EPUB files and displays eXtreme log information. When Transporter finishes executing the command it displays information indicating whether it could verify the file or not. In this example, Transporter verified the 9780446564212.epub EPUB file but couldn’t verify the 9780759574731.epub and 9781599953120.epub EPUB files because unmanifested files were found. Transporter displays the “9000: Unmanifested file found : 9780759574731.epub:/9780759574731.pdf” and “9000: Unmanifested file found : 9781599953120.epub:/OEBPS/images/Art_P116.jpg” error messages indicating the problems. Verify modeIn the following example, the user, bob, runs Transporter in verify mode and specifies that Transporter verify the 98143907060222.itmsp Apple package and display eXtreme logging information.
Transporter attempts to verify the 98143907060222.itmsp Apple package and displays the package metadata, as well as the eXtreme log information. When Transporter finishes executing the command it displays information indicating whether it could verify the package or not. In this example, Transporter couldn’t verify the package because the sales start date element in the metadata has an incorrect value. Transporter displays the “ERROR ITMS-4017: “The value 2515-12-30 provided for sales_start_date is more than 500 years away” at Album/Tracks/Track/Offer (MZItmspOfferPackage)" error message indicating the problem. The example also shows the metadata section where the error occurred. Transporter messagesWeb service, database, and file system messagesThe following table lists the web service, database, and file system messages you might encounter while using Transporter. Code Message 1001 Unable to find registered user with username 1002 Exception occurred when creating MZItmspPackager for provider. 1003 ProviderPackager is null for provider. 1004 Exception occurred when creating MZContentProviderUpload for provider. 1005 Unable to create uploading directory for provider. 1007 Unable to find a MZContentProviderUpload for package. 1008 Unable to find package file for 1009 Unable to create incoming directory for provider. 1010 Unable to create incoming dir 1011 Unable to create uploaded directory for provider. 1012 Unable to create uploaded dir: 1013 Unable to find content provider. Unable to find content provider for 1014 Unable to access directory for path 1015 An error occurred saving your changes to the Apple database. This problem may be a transient issue on the Apple side. If the problem persists for more than an hour, please contact your iTunes representative. 1016 An error occurred saving your changes to the Apple database. This problem may be a transient issue on the Apple side. If the problem persists for more than an hour, please contact your iTunes representative. 1017 Unable to process validateAssets request at this time due to a general error. 1018 Unable to process upload done request at this time due to general error. 1019 Unable to process validateMetadata request at this time due to a general error. 1020 Unable to process authenticateWithProvider request at this time due to general error. 1021 Encoding house user 1022 Internal state error. No matching encoding house could be found for encoding house user 1023 Encoding house 1025 Unable to authenticate a null encoding house user. 1026 Unable to authenticate the encoding house user with a null/empty password. 1028 Unable to authenticate for provider: 1029 Encoding house 1030 Unable to process client checksum completed request at this time due to a general error. 1035 The found upload record is not in an ‘Uploading’ status. The current status is ' 1038 Cannot find a CPU without a package name. 1039 Unable to find content provider for username 1040 Username does not have a content provider. 1041 Unable to find a MZContentProviderUpload for package. 1042 An error occurred saving your changes to the Apple database. This problem may be a transient issue on the Apple side. If the problem persists for more than an hour, please contact your iTunes representative. 1043 Unable to process uploadFailed request at this time due to a general error. 1044 The found upload for the given package name 1045 You must be an Admin or Technical user in order to perform this action. 1046 Client version 1055 The package’s metadata must be specified. 1062 An error occurred while processing the upload’s direct import. 1063 The exact error message is specific to the situation but generally indicates that the iTunes Store, Apple Books, or App Store is not currently accepting content. 1064 The exact error message is specific to the situation but generally indicates that the iTunes Store, Apple Books, or App Store is not currently accepting content. 1065 This operation has been disabled until further notice. 1066 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1067 Invalid or poorly-formed XML. 1068 The authenticated user is not authorized to invoke the requested service method. 1089 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1092 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1095 More than one host with the name ' 1096 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1097 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1098 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1099 The transport information for the package could not be found. 1100 You must supply a vendor identifier. 1101 You must supply a vendor identifier. 1103 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1106 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1107 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1108 A host with the name ' 1109 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1110 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1111 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1113 Either the vendor_id or the apple_id must be specified. 1114 Both the vendor_id and the apple_id can NOT be specified at the same time. Please only specify one. 1115 Unable to process lookupMetadataWithArguments request at this time due to a general error. 1116 No content was found for the specified 1117 The content type for the specified 1118 An internal error occurred in the web service while looking up the metadata with the specified 1119 An error occurred while looking up the metadata with the specified 1120 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1125 Could not find the caller’s encoding house. 1126 Could not gather the status info due to a general error. 1127 Unable to process metadataGuidesForDownloadWithArguments request at this time due to a general error. 1128 Unable to process metadataGuidesForDownloadWithArguments request at this time due to a general error. 1129 The list of metadata guides to download for 1130 Unable to process generate schema request at this time due to a general error. 1131 The exact error message is specific to the situation but generally indicates that the package version is unsupported for the schema. 1132 The base URL to download metadata guides for 1133 The value of the property 1134 The number of files in the package exceeds the maximum of 1135 Unable to process the iTunes QC download request at this time due to a general error. 1136 The apple_id must be a number to be valid. 1137 The QC state of ' 1138 The QC quality of ' 1139 The exact error message is specific to the situation but generally indicates that the parameters supplied (or their combination) were invalid. 1140 The exact error message is specific to the situation but generally indicates that the content object was NOT found with the given request parameters. 1143 The exact error message is specific to the situation but generally indicates an error was encountered while trying to process the content object. 1145 An error occurred while processing the QC download request. 1146 The exact error message is specific to the situation but generally indicates that there was an error while generating the schema. 1147 schemaType parameter must be either ‘strict’ or ‘transitional’: 1148 Unable to process query tickets request at this time due to a general error. 1149 Content provider '%s’ lacks required permissions to query content tickets. 1152 The specified throttle of '%s’ is greater than the allowed max throttle of '%s’. Please use a throttle value equal to or less than the allowed max value. 1153 The specified throttle of '%s’ is invalid. Please specify an integer value for the throttle. 1154 queryTickets mode is not available to iPhone software developers. 1170 Unable to process queryAssetTypes request at this time due to a general error. 1171 Unable to process validateRawAssets request at this time due to a general error. 1200 Unable to process the createMetadataTicket request at this time due to a general error. 1201 The authenticated user is not authorized to open metadata tickets for the specified content. 1202 The specified content was not found. 1203 The specified content does not support opening a new metadata ticket. 1204 The specified content has an existing metadata ticket. 1205 A new title/translation was specified for a track number which does not exist: 1207 Video content supports only title changes. 1208 The specified content already has an open metadata ticket. 1209 The specified content was not found. Please try again, using apple_id instead of vendor_id. 1210 You must have an iTunes Connect account to use create tickets mode. You cannot use your encoding house username and password with create tickets mode. 1241 The version of the application you’re using is no longer allowed. Please log into iTunes Connect to download the latest version or obtain it via software update. 1242 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 1243 Unable to find an iTunes Connect user for username %s. If you are an encoding house user, you must specify a provider short name. 1244 Unable to find an encoding house user for username %s. If you are an iTunes Connect user, you must not specify a provider short name. 1268 An error occurred while processing the json request. 1269 No json request was provided in the payload. 1270 No service name was provided for the json request. 1271 Unable to instantiate the service class named 1272 An error occurred while trying to call the requested method 1273 Could not retrieve the list of valid methods names from the service class named 1274 The method named 1275 No method name was provided in the json request. 1276 No method named 1278 The iTunes Store is experiencing an internal server error. See https://www.apple.com/support/systemstatus/ for information about major outages. 2001 The account 2010 An unknown error occurred. 2012 Authorization failed for user Validation messagesTransporter reports validation errors for such things as bad, invalid, or missing data, as well as unsupported features and schema errors. Validation error messages can provide you with information about the XML package specifications Transporter accepts, as well as help you automate your system and track down any failed packages. All validation errors (for example, metadata validation errors) have the same 2000 error code. For example:
Within the 2000 error code range, Transporter breaks down validation errors into sub-codes to uniquely identify bad data, invalid data, missing data, unsupported features, and schema errors. Transporter sub-code validation errors use the following general format: ITMS-ErrorCode: ErrorMessage. Internally, the Transporter sub-code validation errors use a long format similar to the following: ` Unable to find registered encoding house user for username "bsmith" (1001)`392 For example: ` Unable to find registered encoding house user for username "bsmith" (1001)`393. Note: Because Apple periodically releases new versions and updates to its software, the sub-code validation error format shown in this guide might change and be somewhat different from what you see on your screen. For sub-code validation errors in the 3-Series: Bad Data, 4-Series: Invalid Data, 5-Series: Missing Data, 6-Series: Unsupported Features, 8-Series: Schema Errors, and 9-Series: Asset Errors range, see the following table. Code Message 3-Series: Bad Data Bad Data is data that might be well formed, valid XML, but is in some deeper way inconsistent with itself or with the existing state of the content management system. 3000 Generic error code for Bad Data. 3001 Has container ID, but playlist does not exist. 3002 Referenced VideoFileComponentSet does not exist. 3003 Referenced vendor ID for video could not be found. 3004 Has unknown asset type. 3005 A playlist with this UPC already exists for this provider. 3006 Computed checksum does not match provided checksum in metadata.xml. 4-Series: Invalid Data Invalid data is either poorly formatted, invalid XML, or the contents of the XML elements do not conform to the iTMS specification. 4000 Generic error code for Invalid Data. 4001 Original Release Date is before 1900 C.E. 4002 Original Release Year is not 4 digits. 4003 Release date is before 1900 C.E. 4004 Audiobook track is cleared for sale. Audiobook tracks cannot be sold individually. 4005 Chapters are not in order. 4006 Has bonus material with duplicate vendor identifiers. 4007 Has tracks with duplicate vendor identifiers. 4008 Has videos with duplicate vendor identifiers. 4009 First chapter does not begin at timecode 00:00:00. 4010 Has more than one cover art file, iTMS will only use primaryArtworkFile. 4011 Multiple products for the territories. 4012 Defines multiple track products for the territories. 4013 Defines multiple video products for the territories. 4014 Package language is not a valid ISO language. 4015 All chapters must have artwork or all chapters must have no artwork. 4016 Preorder-only track is on album without preorder date. 4017 Available date more than one year away. 4018 Available date is before 1900 C.E. 4019 Preorder date must be before available date. 4020 Preorder date is not allowed on this offer. 4021 Preorder date more than one year away. 4022 Preorder date is before 1900 C.E. 4023 Preorder wholesale tier is only allowed on album products. 4024 Offer product has negative wholesale price. 4025 Has the territories not specified on the album. 4026 Release Year is not 4 digits. 4027 Cover file payload is not an allowed type. 4028 File is not a recognized type. 4029 Invalid or poorly-formed XML. 4030 Album type is not a recognized album type. 4031 Invalid album-level track count. 4032 Unknown role. 4033 The file payload is not an allowed type. 4034 Invalid track number. 4035 Invalid volume number. 4036 Chapter art file type is not supported. 4037 Encountered invalid time code on chapter. 4038 Bad unavailable date. 4039 Invalid track preview start index. 4040 Invalid track number. 4041 Invalid volume number. 4042 Invalid track-level volume count. 4043 Invalid track-level track count. 4044 The file payload is not an allowed type. 4045 Invalid item number. 4046 Invalid volume number. 4047 Rating container does not match any known rating. 4048 Bad video release date. 4049 A field that is supposed to be formatted as a number could not be parsed as such. 4050 Episode production number cannot be greater than MAX_EPN_LENGTH characters in length. 4051 This XML tag has been deprecated. 4052 Invalid Sell Plus Quality in XML. 4053 Invalid Translations. 4057 Invalid Physical Release Date. 4058 Enable_user_generated_ringtone tag is present on a non-track level product. This is not allowed. 4060 Does not have UPC data as digits between 10 and 14 digits in width. 4061 Does not have ISRC data as alphanumeric of 12 width. 4062 Invalid Vendor Identifier. 4063 Price tier for the content provider is invalid. 5-Series: Missing Data Missing data refers to elements that are required in the package according to the iTMS specification and are not present. 5000 Generic error code for Missing Data. 5001 Does not have cover art file. 5002 Does not have any genre names. 5003 Album does not have name. 5004 Album has no artist set as primary. 5005 Album does not have vendor identifier. 5006 Artist does not have name. 5007 Does not have bonus material file name. 5008 Bonus Material does not have vendor identifier. 5009 Chapter has no title. 5010 Bonus Material does not have copyright information. 5011 Does not have checksum for file. 5012 File container is present but does not contain a file. 5013 File container is not present. 5014 Piece has no Name. 5015 Product Offer not specified in metadata, iTMS will use default. 5016 Product does not have available date, iTMS will use default. 5017 Available date must be specified along with preorder date. 5018 Product offer does not have territory. 5019 Product does not have wholesale, iTMS will use default. 5020 Track does not have name. 5021 Album has no tracks or videos. 5022 Track is missing territories specified on the album:. 5023 Track does not have vendor identifier. 5024 Video does not have name. 5025 Origin asset is not present in the metadata. 5026 Video does not have vendor identifier. 5027 Root file does not contain metadata file. 5028 Meta data uploads are not allowed for this provider. No file container for song in metadata. 5029 Meta data uploads are not allowed for this provider. No file container for video in metadata. 5030 Artist has no Name. 5037 Missing track number. 5038 6-Series: Unsupported Features 8-Series: Schema Errors Schema validation errors are errors that occur during the import system’s attempt to validate the metadata.xml file against the Apple schema. 8000 Generic error code for Schema Error. 8001 Schema validation fatal errors occur upon encountering of conditions such as a malformed XML file. These conditions prevent the XML schema validating parser to perform its normal operation. 8002 Schema validation errors occur while validating XML against the corresponding schema. 8003 Warnings are a result of schema validation when non-fatal and non-error conditions are met. 9-Series: Asset Errors Asset validation or retrieval errors are errors that can occur on the client side. 9000 The specified asset does not follow specifications. To fix the error, follow the on-screen suggestions and review requirements in iTunes Package Specification and iTunes Asset Guide. 9101 Could not download the 9102 Could not download the Style guide messagesThe following table lists the style guide messages you might encounter while using Transporter. Code Message 4112 Live: If the audio is from a live recording, Live must be listed on the track. 4221 Compound Artist: < 4221 Various Artists on Track: Various Artists must not be a track-level artist. 4181 Missing Composer: At least one Composer must be provided at both the album and the track level. This role is required for the supplied genres. 4181 Feat., With as Primary: Album or track lists the same artist with both Primary and featuring or with roles: <` Unable to find registered encoding house user for username "bsmith" (1001)`397>. More resourcesGlossaryThe glossary defines terms you will encounter as you use this guide. Term Definition app developer The content-owning entity that has a contract directly with Apple. App developers deliver content directly to the App Store and must have an App Store Connect account with the Admin or Technical role. App Store Connect A suite of web-based tools you can use to sign up to become a content provider and to manage your content. You use App Store Connect to submit and manage your content in the App Store. You also use App Store Connect to accept legal agreements, to enter your tax and banking information, and to view trends and financial reports. For more information, see the App Store Connect Help. Aspera FASP software A suite of cross-platform software applications that provides secure transmission of file and directory data independent of network conditions. The Aspera file transfer client application can securely transfer data on public and private networks much faster than standard FTP, depending on available bandwidth. For more information, see the Aspera website. checksum A redundancy check used to guarantee that the asset files Apple receives are correct and complete. All content files you deliver to Apple must include an industry-standard MD5 digest checksum. Once received, the MD5 digest checksum contained in the metadata file (one for each file you send) is compared against the actual file received by Apple. If any differences are detected, Transporter rejects the asset file as well as its entire corresponding package. encoding house Partners without a contractual relationship with iTunes. Encoding houses provide encoding, delivery, and metadata preparation services for third-party users. Encoding houses deliver all content directly to the iTunes Store or App Store through Transporter and are contracted by third party users for their services. An encoding house and a provider can be the same company. Compare provider. FASP Aspera’s Fast, Secure Protocol. Aspera’s data transfer technology and file transfer products are built on the FASP proprietary file transport protocol. The protocol is designed to meet the requirements of file transfers over any IP network. For more information, see the Aspera website. iBooks format A file format created for Multi-Touch books and Multi-Touch textbooks on the iPad. Books you create in iBooks format (.ibooks) using iBooks Author support rich typography, precise layout, and new interactive objects such as image galleries, quizzes, and slideshows. iTunes Connect A suite of web-based tools you can use to sign up to become a content provider and to manage your content. You use iTunes Connect to submit and manage your content in the iTunes Store or Apple Books. You also use iTunes Connect to accept legal agreements, to enter your tax and banking information, and to view trends and financial reports. For more information, see the App Store Connect Help. lossless data compression A class of data compression algorithms that allow the exact original data to be reconstructed from the compressed data. Common lossless audio compression formats include FLAC (Free Lossless Audio Codec) and Apple Lossless Core Audio Format (CAF). Compare lossy data compression. lossy data compression A class of data compression algorithms that allow an approximation of the original data to be reconstructed, in exchange for better compression rates. Common lossy audio compression formats include MP3, AAC (Advanced Audio Coding), and IMA ADPCM. Compare lossless data compression. MD5 Message-Digest algorithm 5. A cryptographic hash function with a 128-bit hash value used by Transporter to guarantee that the asset files you send are correct and complete. Polished A state in iTunes Connect indicating that Apple reviewed the content of your package and made any necessary corrections. provider The content-owning entity that has a contract directly with Apple. Providers can be encoding houses, publishers, or app developers and can deliver content directly to the iTunes Store, Apple Books, or App Store or contract with an encoding house for their services and use the encoding house to deliver content. A provider and an encoding house can be the same company. Compare encoding house. publisher The content-owning entity that has a contract directly with Apple. Publishers are the personal or corporate contributor to the publication content you are delivering directly to Apple Books. schema file A file defining the structure, content, formatting, and semantics of XML documents. You can request transitional or strict schema files from Transporter to use to validate your XML files before packaging and sending them to Apple for upload. Signiant Media Exchange An integrated, open software solution to help you manage, secure, automate, and accelerate digital file-based workflows and to move and distribute content. For more information, see the Signiant website at https://www.signiant.com. SSH Secure Shell. A set of standards and an associated network protocol that allows you to establish a secure channel connection between a local and a remote computer. Store Package A Transporter generated file with the .itmsp file extension. Transporter generates a package file (iTunes Store Package, App Store Package, or Book Package) from uploaded content. stub package An incomplete Store Package. A stub package only has some of the information in a total Store Package, needing the remaining information to be provided. For example, in lookup metadata mode, a stub package is created with only a single metadata.xml file. You still need to provide any missing assets, cover images, or bonus materials. Transporter uses the stub package only to help generate the metadata.xml file. subitem An In-App Purchase, a Game Center Achievement, or a Game Center Leaderboard. throughput The amount of data per time unit that is uploaded. You can specify ` /Users/bsmith/Applications/Packages/Many/00000000001041.itmsp - Error Messages:`99 with any upload delivery method to receive the time it took Transporter to upload a specific package. Unpolished A state in iTunes Connect indicating that Apple hasn’t reviewed the content of your package. web service A software system designed to support interoperable machine-to-machine interaction over a network. Notation conventionsThe following conventions are used throughout this guide. SummaryNotation Indicates ` Unable to find registered encoding house user for username "bsmith" (1001)`400 A command or other terminal text. ` Unable to find registered encoding house user for username "bsmith" (1001)`401 A shell prompt. ` Unable to find registered encoding house user for username "bsmith" (1001)`402 An optional command-line option. A user-provided value. ` Unable to find registered encoding house user for username "bsmith" (1001)`403 Alternative command-line option values (type one or the other). Commands and Other Terminal TextCommands or command-line options that you type, along with other text that normally appears in a Terminal window or at another command-line prompt, are shown in ` Unable to find registered encoding house user for username "bsmith" (1001)`404 font. For example: You can use the ` Unable to find registered encoding house user for username "bsmith" (1001)`405 command to get things done. When a command is shown on a line by itself, as you might type it in a Terminal window or at another command-line prompt, it follows a dollar sign that represents the shell prompt. For example: ` Unable to find registered encoding house user for username "bsmith" (1001)`406 To use the command in this example, type ` Unable to find registered encoding house user for username "bsmith" (1001)`405 without the dollar sign at the command prompt, then press the Return key. Command-Line Options and ValuesMost commands require you to specify one or more command-line options and values, or the item to which the command is applied. Command-Line Options You Must Type as ShownIf you need to type a command-line option and value as shown, it appears following the command in the same font. For example: ` Unable to find registered encoding house user for username "bsmith" (1001)`408 To use the command in this example, type the entire line as shown. Command-Line Option Values You ProvideIf you need to supply a value, its placeholder has a name that indicates what you need to provide. For example: ` Unable to find registered encoding house user for username "bsmith" (1001)`409 In this example, you need to replace hh with the hour and mm with the minute, as shown in the previous example. Optional Command-Line OptionsIf a command-line option is available but not required, it appears in square brackets. For example: ` Unable to find registered encoding house user for username "bsmith" (1001)`410 To use the command in this example, type either Alternative Command-Line Option ValuesIf you need to type one of a number of command-line option values, they are separated by a vertical line and grouped within angle brackets ` Unable to find registered encoding house user for username "bsmith" (1001)`413. For example: ` Unable to find registered encoding house user for username "bsmith" (1001)`414 To use the command in this example, you must type either Command-line helpFor more command-line information, see:
Solve problemsTransporter problemsUse this section to help you troubleshoot general problems you might encounter while using Transporter. What tools are available to debug problems with Transporter?You can use the following modes and options to help you debug problems with Transporter:
My Windows machine generates error messages that it cannot migrate a jar during the automatic software update process when I run Transporter. What can I do?If you are getting multiple error messages that look similar to this:
You can do one of these two options:
The machine where I installed Transporter can’t connect to the web service running on Apple’s servers. What can I do?Perform the following steps to verify you can hit the web service URL using the machine where you installed Transporter:
If the web service is down, and you are using eXtreme verbosity, Transporter displays the following output:
What can I do if Transporter stalls during upload?During upload, if you receive output similar to the example below, retry your delivery or upgrade to the latest version of Transporter.
Java Virtual Machine problemsUse this section to help you troubleshoot Java Virtual Machine problems you might encounter while using Transporter. What version of the Java Virtual Machine (JVM) does Transporter require and how do I determine which version I have installed?
How do I upgrade to JVM version 17?
What can I do if Transporter fails due to an SSL exception?
What can I do when Transporter or JVM hangs?Get a Java stack trace of the problem by pressing:
For more information, see https://java.sun.com/developer/technicalArticles/Programming/Stacktrace/. Some older versions of Transporter contain components that can’t be updated as part of Transporter’s automatic software update functionality. If Transporter hangs when using older versions of Java, download and re-install the latest Transporter available from iTunes Connect. Aspera problemsUse this section to help you troubleshoot problems you might encounter while using Transporter in the Aspera delivery method. What can I do if Transporter fails during upload using Aspera and a 64 bit Linux distribution?Transporter might have an issue with Aspera and a 64 bit Linux distribution if, during upload, a message similar to the following appears in the Transporter log output information: ` Unable to find registered encoding house user for username "bsmith" (1001)`530 To resolve the issue, install the 32 bit compatibility libraries.
What can I do if Transporter fails during upload using Aspera and Windows 7 (64 bit)?If you see an error message that looks like this in your transporter log: ` Unable to find registered encoding house user for username "bsmith" (1001)`534 Your install of Windows-7 may be missing a DLL. To correct this problem download and install the "Visual C++ Redistributable for Visual Studio 2015” from Microsoft at https://www.microsoft.com/en-us/download/details.aspx?id=48145. Where can I find Aspera error code messages and explanations?
Where can I find Aspera’s log files?Aspera’s log file, aspera-scp-transfer.log, is located in a package-specific directory under your operating system’s temp directory. Aspera’s log file is typically located in the following directories:
Where The following is an example of a Transporter message indicating where the Aspera log file is located when an upload isn’t successful: “[2007-07-31 13:38:44 PDT] Signiant problemsUse this section to help you troubleshoot problems you might encounter while using Transporter in the Signiant delivery method. Where can I find Signiant’s log files? Signiant’s log files are located in your operating system’s temp directory. The temp directory value is programmatically retrieved from the Java property named ` Unable to find registered encoding house user for username "bsmith" (1001)`535. The temp directories are typically located in the following directories:
Signiant log file names begin with “sigitc”, contain date and time information, and use a .log extension. For example: sigitc-2007-04-11-13-04-46-766.log If file upload is successful, Signiant Media Exchange deletes the log file. If there were errors during upload, Signiant Media Exchange saves the log file and displays the log file’s name and location. For example: [2007-04-11 13:05:49 PDT] Transporter error messagesUse this section to help you troubleshoot problems you might encounter while using Transporter in the Aspera and Signiant delivery methods. I received message “1028 Unable to authenticate for provider:
|
