Does cloud build support using enterprise provisioning profiles? I’m using an enterprise provisioning profile and p12 that worked on our build machine and on TestFlight, but I get the following error when setting up the project on Unity cloud build: “The provisioning profile and .p12 file are not compatible (certificates did not match)!”
Hi @Plattinator ,
Yes this should be supported in UCB. More than likely it’s an issue with the two files. For example, you may have mixed up a Development Cert p12 with a Production mobile provision file, or vice versa?
Check out this Guide we made if you haven’t already, and if you’re still stuck please file a support ticket and we’ll try to look into it.
Thanks!
hi,
*update, adhoc + cloud build cert generation still works on PC (no mac required)
Getting same error message with enterprise license,
“There was an error:
The provisioning profile and .p12 file are not compatible (certificates did not match)!”
Followed this tutorial to create .p12 key on windows:
(but picked distribution provisioning profile)
Tutorial for doing the cloud ios setup process on Windows could be useful…?
@mgear - you should use a Mac to generate the p12 file. Let us know how it goes!
Yeah it works on mac now.
Would it work on pc if some correct settings are used?
We can’t make a iOS build with our enterprise profile.
Code Sign error: No matching codesigning identity found: No codesigning identities (i.e. certificate and private key pairs) matching [name] were foud.
We have a umlaut (ü) in our code signing identity. Could that be the problem? We can make the build on our local machines and we can make a build using other profiles without the umlaut with Unity Cloud Build.
@TimSchroeder - hmm yeah that sounds like a bug. Can you file a support ticket so we can be sure that is the issue? Thanks!
We are getting the same error, but for an ad hoc profile. Archivibg locally using XCode with the same provisioning profile and signing certificate works fine. Is this a known bug?
We rolled out a fix on this issue. Please let us know if it works properly now.
Hi
we just have the same issue with Umlauts in the enterprise provisioning profile: local build is fine, cloud build fails with
no identity found.
The name is properly displayed in ‘credentials set’ but not in CODE_SIGN_IDENTITY.
I am happy to provide the full build log in private.
The link above causes an infinite redirect loop
Now the enterprise account is not good to apply, many people do not have this kind of account, you can look at this website,https://www.iosenterpriseaccount.com/,
the enterprise program in principle can let a lot of people(no limit) inside the company to use, while the iOS developer program can be published to the public.