iTMS Transporter not found on this machine - Transporter is no longer bundled with xcode 14

[BjornGameDev]

Issue Description

When you try to publish a ios app on Xcode 14 it throws the following error:

iTMS Transporter not found on this machine - make sure your Xcode installation is not damaged.

The transporter app is no longer bundled with Xcode 14? One fix I found is to install the Transporter.app separately from the App store and hard code getITMSTransporterPath function in itmtransporter-service.js to '/Applications/Transporter.app/Contents/itms/bin/iTMSTransporter'.

Reproduction

With xcode 14 and MacOs Ventura

1. Run ns publish ios
2. Throws error iTMS Transporter not found on this machine - make sure your Xcode installation is not damaged.

Relevant log output (if applicable)

No response

Environment

OS: macOS 13.0
CPU: (6) x64 Intel(R) Core(TM) i5-8500B CPU @ 3.00GHz
Shell: /bin/zsh
node: 12.9.1
npm: 6.10.2
nativescript: 8.3.3

# android
java: 11.0.14.1
ndk: Not Found
apis: Not Found
build_tools: Not Found
system_images: Not Found

# ios
xcode: 14.0.1/14A400
cocoapods: 1.11.2
python: 2.7.18
python3: 3.8.6
ruby: 2.6.10
platforms:
  - DriverKit 21.4
  - iOS 16.0
  - macOS 12.3
  - tvOS 16.0
  - watchOS 9.0

Please accept these terms

• I have searched the existing issues as well as StackOverflow and this has not been posted before
• This is a bug report
• I agree to follow this project's Code of Conduct

[BjornGameDev]

If nativescript uses the iTMSTransporter in future then the Transporter app needs to be installed separately and ns doctor needs to check it is installed. Another option I've heard is to do it through altool?

[copperford]

Having the same issue. Similar workaround after looking at the itmtransporter-service.js. file was to copy the ITMSTransporter binary into the expected location under /Applications/XCode/Contents/SharedFrameworks/ContentDeliveryService.frameworks/Versions/A/itms/bin directory. Ugly, but got me past this step.

[BjornGameDev]

Yep, both solutions make it work. There might be a risk that when there is a update of Xcode, the binary gets removed again, also you won't get any updates to the Transporter. Of course my temporary solution also gets removed if I update nativescript.

Pick your poison until official patch is here.

[rigor789]

I'm curious to learn how you usually publish new versions. I've been mostly doing it through XCode directly (ns prepare --release... then open in XCode -> Archive -> Upload) or in many cases through CI and fastlane, so have not really relied on the NativeScript CLI's publish commands. Given apple changes things with their API and tooling every so often, it's a bit of a maintenance overhead for the cli to keep up, and I'd consider dropping those commands in the future in favor of direct XCode, fastlane or direct Transporter uploads separate from the {N} cli, but of course need to gather more information about the current use cases before making any decisions...

[BjornGameDev]

I use the ns publish ios. It is handy as no extra steps are required to upload. Having to use Transporter manually or xcode wouldn't be a big issue. Yet as this is a option currently in the framework it would be cool if it worked. Also would be good to give people time to move over if it was deprecated (don't be Apple). Only benefit could be if someone had some kind of build automation in use.

The current nativescript cli is just using Transporter, it think? It just isn't bundled with xcode anymore. It used to be in the '/Applications/XCode/Contents/SharedFrameworks/ContentDeliveryService.frameworks/Versions/A/itms/bin' folder.

Maybe a good way would be to add a place to save the Transporter location and make it a optional param. That way you can still use it, and less hassle for the cli to check if it is installed and where.

Fastlane has the same bug as nativescript cli, currently. Don't know if they fixed it yet.