Search Unity

  1. We've closed the job boards. If you're looking for work, or looking to hire check out Unity Connect. You can see more information here.
    Dismiss Notice
  2. We're running great holiday deals on subscriptions, swag and Asset Store packages! Take a peek at this blog for more information!
    Dismiss Notice
  3. Check out our Unite Austin 2017 YouTube playlist to catch up on what you missed. More videos coming soon.
    Dismiss Notice
  4. Unity 2017.2 is now released.
    Dismiss Notice
  5. The Unity Gear Store is here to help you look great at your next meetup, user group or conference. With all new Unity apparel, stickers and more!
    Dismiss Notice
  6. Introducing the Unity Essentials Packs! Find out more.
    Dismiss Notice
  7. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice
  8. Unity 2017.3 beta is now available for download.
    Dismiss Notice

Using Enterprise provisioning profile (iOS)

Discussion in 'Unity Cloud Build' started by Plattinator, Sep 8, 2014.

  1. Plattinator

    Plattinator

    Joined:
    Dec 28, 2011
    Posts:
    17
    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)!"
     
  2. hypeNate

    hypeNate

    Joined:
    Apr 4, 2014
    Posts:
    258
    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.

    https://build.cloud.unity3d.com/support/guides/ios

    Thanks!
     
  3. mgear

    mgear

    Joined:
    Aug 3, 2010
    Posts:
    4,065
    hi,

    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..?
     
    Last edited: Feb 11, 2015
  4. hypeNate

    hypeNate

    Joined:
    Apr 4, 2014
    Posts:
    258
    @mgear - you should use a Mac to generate the p12 file. Let us know how it goes!
     
  5. mgear

    mgear

    Joined:
    Aug 3, 2010
    Posts:
    4,065
    Yeah it works on mac now.

    Would it work on pc if some correct settings are used?
     
  6. TimSchroeder

    TimSchroeder

    Joined:
    Aug 27, 2014
    Posts:
    9
    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.
     
  7. hypeNate

    hypeNate

    Joined:
    Apr 4, 2014
    Posts:
    258
    @TimSchroeder - hmm yeah that sounds like a bug. Can you file a support ticket so we can be sure that is the issue? Thanks!
     
  8. poshaughnessey

    poshaughnessey

    Joined:
    Jul 12, 2012
    Posts:
    31
    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?
     
  9. David-Berger

    David-Berger

    Unity Technologies

    Joined:
    Jul 16, 2014
    Posts:
    646
    We rolled out a fix on this issue. Please let us know if it works properly now.
     
  10. lores3000

    lores3000

    Joined:
    Feb 23, 2016
    Posts:
    1
    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.
     
  11. Octaga

    Octaga

    Joined:
    Sep 16, 2015
    Posts:
    1
    The link above causes an infinite redirect loop