Azure Piplines Configuration for Xcode Managed Profile Setup - Possible? Documented?












2















Environment



Server - Azure Pipelines
Hosted MacOS agent


Issue Description



I'm using the following configuration in my Xcode project (w automatic code signing):



enter image description here



Is it possible to have Pipelines build and sign a project using this configuration if I've manually installed all of the provisioning profiles and certs in my pipeline prior to building?



Is there any documentation for this scenario or a how-to guide? Alternatively, if this is not possible perhaps a definitive statement on this and advice on what to try next in order to work. For instance - do I need to convert this project from an automatically signed one to a manual one?



I'm using the following page which mentions automatic signing but doesn't give any instructions on how to configure (but does mention this as an option):



https://docs.microsoft.com/en-us/azure/devops/pipelines/apps/mobile/app-signing?view=vsts&tabs=apple-install-during-build



enter image description here



Any help would be appreciated.



Thanks,



Andrew










share|improve this question





























    2















    Environment



    Server - Azure Pipelines
    Hosted MacOS agent


    Issue Description



    I'm using the following configuration in my Xcode project (w automatic code signing):



    enter image description here



    Is it possible to have Pipelines build and sign a project using this configuration if I've manually installed all of the provisioning profiles and certs in my pipeline prior to building?



    Is there any documentation for this scenario or a how-to guide? Alternatively, if this is not possible perhaps a definitive statement on this and advice on what to try next in order to work. For instance - do I need to convert this project from an automatically signed one to a manual one?



    I'm using the following page which mentions automatic signing but doesn't give any instructions on how to configure (but does mention this as an option):



    https://docs.microsoft.com/en-us/azure/devops/pipelines/apps/mobile/app-signing?view=vsts&tabs=apple-install-during-build



    enter image description here



    Any help would be appreciated.



    Thanks,



    Andrew










    share|improve this question



























      2












      2








      2








      Environment



      Server - Azure Pipelines
      Hosted MacOS agent


      Issue Description



      I'm using the following configuration in my Xcode project (w automatic code signing):



      enter image description here



      Is it possible to have Pipelines build and sign a project using this configuration if I've manually installed all of the provisioning profiles and certs in my pipeline prior to building?



      Is there any documentation for this scenario or a how-to guide? Alternatively, if this is not possible perhaps a definitive statement on this and advice on what to try next in order to work. For instance - do I need to convert this project from an automatically signed one to a manual one?



      I'm using the following page which mentions automatic signing but doesn't give any instructions on how to configure (but does mention this as an option):



      https://docs.microsoft.com/en-us/azure/devops/pipelines/apps/mobile/app-signing?view=vsts&tabs=apple-install-during-build



      enter image description here



      Any help would be appreciated.



      Thanks,



      Andrew










      share|improve this question
















      Environment



      Server - Azure Pipelines
      Hosted MacOS agent


      Issue Description



      I'm using the following configuration in my Xcode project (w automatic code signing):



      enter image description here



      Is it possible to have Pipelines build and sign a project using this configuration if I've manually installed all of the provisioning profiles and certs in my pipeline prior to building?



      Is there any documentation for this scenario or a how-to guide? Alternatively, if this is not possible perhaps a definitive statement on this and advice on what to try next in order to work. For instance - do I need to convert this project from an automatically signed one to a manual one?



      I'm using the following page which mentions automatic signing but doesn't give any instructions on how to configure (but does mention this as an option):



      https://docs.microsoft.com/en-us/azure/devops/pipelines/apps/mobile/app-signing?view=vsts&tabs=apple-install-during-build



      enter image description here



      Any help would be appreciated.



      Thanks,



      Andrew







      ios xcode devops azure-pipelines xcodebuild






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 15 '18 at 11:53







      Andrew Lombard

















      asked Nov 15 '18 at 11:17









      Andrew LombardAndrew Lombard

      212114




      212114
























          1 Answer
          1






          active

          oldest

          votes


















          0














          To help anyone who comes across this later.



          The issue in my case was that I have a solution with multiple targets (App, Widget, Siri Intent, and Siri UI). Each of these requires it's own provisioning profile and needs to be signed independently - this is where I ran into trouble (the default configuration seemed to try and apply the App profile to all Targets when signing).



          To help anyone who struggles with this - in order to solve I needed the following steps in Xcode:




          1. Convert the project to manual signing.

          2. Archive and export in Xcode

          3. 'Distribute via App Store'

          4. Select to Export but not submit and choose a location

          5. Selected the desired provisioning profiles for the export.

          6. After export head to saved location and grab 'exportOptions.Plist'.

          7. Choose .plist for 'export options' in the appropriate DevOps
            pipeline.


          Voila you can sign your solution with multiple schemes!



          Hope this helps someone.



          Andrew



          PS - At some moment I will confirm that setting everything back to automatic signing works with exportOptions.Plist and will report back.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53318284%2fazure-piplines-configuration-for-xcode-managed-profile-setup-possible-documen%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            To help anyone who comes across this later.



            The issue in my case was that I have a solution with multiple targets (App, Widget, Siri Intent, and Siri UI). Each of these requires it's own provisioning profile and needs to be signed independently - this is where I ran into trouble (the default configuration seemed to try and apply the App profile to all Targets when signing).



            To help anyone who struggles with this - in order to solve I needed the following steps in Xcode:




            1. Convert the project to manual signing.

            2. Archive and export in Xcode

            3. 'Distribute via App Store'

            4. Select to Export but not submit and choose a location

            5. Selected the desired provisioning profiles for the export.

            6. After export head to saved location and grab 'exportOptions.Plist'.

            7. Choose .plist for 'export options' in the appropriate DevOps
              pipeline.


            Voila you can sign your solution with multiple schemes!



            Hope this helps someone.



            Andrew



            PS - At some moment I will confirm that setting everything back to automatic signing works with exportOptions.Plist and will report back.






            share|improve this answer




























              0














              To help anyone who comes across this later.



              The issue in my case was that I have a solution with multiple targets (App, Widget, Siri Intent, and Siri UI). Each of these requires it's own provisioning profile and needs to be signed independently - this is where I ran into trouble (the default configuration seemed to try and apply the App profile to all Targets when signing).



              To help anyone who struggles with this - in order to solve I needed the following steps in Xcode:




              1. Convert the project to manual signing.

              2. Archive and export in Xcode

              3. 'Distribute via App Store'

              4. Select to Export but not submit and choose a location

              5. Selected the desired provisioning profiles for the export.

              6. After export head to saved location and grab 'exportOptions.Plist'.

              7. Choose .plist for 'export options' in the appropriate DevOps
                pipeline.


              Voila you can sign your solution with multiple schemes!



              Hope this helps someone.



              Andrew



              PS - At some moment I will confirm that setting everything back to automatic signing works with exportOptions.Plist and will report back.






              share|improve this answer


























                0












                0








                0







                To help anyone who comes across this later.



                The issue in my case was that I have a solution with multiple targets (App, Widget, Siri Intent, and Siri UI). Each of these requires it's own provisioning profile and needs to be signed independently - this is where I ran into trouble (the default configuration seemed to try and apply the App profile to all Targets when signing).



                To help anyone who struggles with this - in order to solve I needed the following steps in Xcode:




                1. Convert the project to manual signing.

                2. Archive and export in Xcode

                3. 'Distribute via App Store'

                4. Select to Export but not submit and choose a location

                5. Selected the desired provisioning profiles for the export.

                6. After export head to saved location and grab 'exportOptions.Plist'.

                7. Choose .plist for 'export options' in the appropriate DevOps
                  pipeline.


                Voila you can sign your solution with multiple schemes!



                Hope this helps someone.



                Andrew



                PS - At some moment I will confirm that setting everything back to automatic signing works with exportOptions.Plist and will report back.






                share|improve this answer













                To help anyone who comes across this later.



                The issue in my case was that I have a solution with multiple targets (App, Widget, Siri Intent, and Siri UI). Each of these requires it's own provisioning profile and needs to be signed independently - this is where I ran into trouble (the default configuration seemed to try and apply the App profile to all Targets when signing).



                To help anyone who struggles with this - in order to solve I needed the following steps in Xcode:




                1. Convert the project to manual signing.

                2. Archive and export in Xcode

                3. 'Distribute via App Store'

                4. Select to Export but not submit and choose a location

                5. Selected the desired provisioning profiles for the export.

                6. After export head to saved location and grab 'exportOptions.Plist'.

                7. Choose .plist for 'export options' in the appropriate DevOps
                  pipeline.


                Voila you can sign your solution with multiple schemes!



                Hope this helps someone.



                Andrew



                PS - At some moment I will confirm that setting everything back to automatic signing works with exportOptions.Plist and will report back.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 21 '18 at 12:44









                Andrew LombardAndrew Lombard

                212114




                212114






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53318284%2fazure-piplines-configuration-for-xcode-managed-profile-setup-possible-documen%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    這個網誌中的熱門文章

                    Xamarin.form Move up view when keyboard appear

                    Post-Redirect-Get with Spring WebFlux and Thymeleaf

                    Anylogic : not able to use stopDelay()