Ad-Hoc Distribution Build for external testing company

Unity Engine
,
1

I have done distribution builds for our own testing devices, i.e. devices IDs connected to our own provisioning profile - no problem there.

However, I am struggling with doing a build for an external testing company who have sent their own certificate and profile for me to use.

I have installed their certificate into my keychain, and their profile into Xcode - and it is listed in Organizer along with my own profiles in Library|Provisioning Profiles. Everything looks ok so far.

In the Xcode Unity project I have set their profile in the place where I would usually set my own distribution profile under Code Signing. This was not enough because their bundle id did not match mine (obviously) and the build failed. To solve this I changed the Info.plist to have their bundle identifier used instead of mine. This then allowed me to build ok, and in the organizer the app showed their id. So I ‘Shared’ it as an IPA and sent it off to them - but they have come back saying “A valid provisioning profile for this executable was not found.”

Can anyone offer some advice here? Thanks.

2

Did you create an Ad-Hoc distribution certificate in your provisioning portal and link it to their devices?

I can highly recommend checking out TestFlight in combination with this Unity TestFlight plugin. This takes away A LOT of hassle with Ad-Hoc builds and testing.

3

No, they sent me both the certificate and the provisioning profile.

I have installed their certificate into my keychain, and their provisioning profile into Xcode (this part doesn’t work without their certificate) - and it is listed in Organizer along with my own profiles in Library|Provisioning Profiles.

4

It looks like what happened was that when creating the IPA the re-sign options reset to our normal distribution profile.

5

Fun stuff, certificates and profiles :wink: Good to know it’s working now.