That means you create an IPA (basically a zip containing your signed app) you can distribute over-the-air to register devices. You need to create a provisioning profile for testing so you can connect them to Xcode and install the app to debug, or you can distribute the app Ad Hoc. I usually send this link: and I eventually get the UUID I'm asking for, but I think you should rely on TestFlight if you are dealing with non tech-savvy people.Īnyway, let's suppose you have some devices registered on your developer portal.

I have to say it isn't straightforward to get the UUID from your test devices if you need to ask them to a client, and that's the main advantage of using TestFlight. The former allows you to submit a build to App Store connect and immediately push it to your internal team, up to 25 members, or ask for a review and have up to 10,000 tester receive the build via the Test Flight app on their devices.īut what if you don't want to bother with creating a new app in App Store Connect? Maybe you're in the early stage of development, or just prototyping an idea of an app, or don't yet have access to Connect with your account (that shouldn't be true starting February 2019 as Apple is allowing the same account on the developer portal and Connect).Īd Hoc distribution is an easy and quick way to send an app to test devices you have register on the developer portal. There are two ways to distribute a test version of your app for iOS: TestFlight and Ad Hoc. I want to share my experience building and distributing apps with xcodebuild hoping to help some iOS developer struggling with automating build and distribution via command line.

Debug from mac cleaner ads