How to fix: Xcode 9 building loop until exit code 255












6















Please don't mark as duplicate since available threads haven't provided a valid solution.



Since Xcode 9 one of my projects is stuck in a building loop.



The project is building. Running on iPhone and building again and again. Even builds over and over while coding without asking for build or run.



After cleaning, cleaning build folder, deleting Derived Data and restarting, the project crashes after build with:




Command /Applications/Xcode.app/Contents/Developer/usr/bin/ibtool failed with exit code 255. The tool may have crashed. Please file a bug report at http://bugreport.apple.com with the above output and attach any crash logs for ibtool, ibtoold, Xcode, and Interface Builder Cocoa Touch Tool created around the time of this failure. These logs can be found in ~/Library/Logs/DiagnosticReports or /Library/Logs/DiagnosticReports.




After several cleaning and restarting, it finally builds and after a couple of more builds and code changes, the whole process restarts. Building stuck in a loop even without asking to build until 255 exit code.



What am I missing? Help is very appreciated.










share|improve this question




















  • 3





    Same here, I need restart XCode many times during a day! :(

    – Tom Calmon
    Sep 27 '17 at 17:46











  • Seems to be a bug

    – Ludovic
    Sep 28 '17 at 8:05











  • Do you maybe have multiple targets in your project? If so, I managed to stop this behaviour by switching off Edit Scheme / Build / Parallelize Build.

    – yuzer
    Oct 3 '17 at 18:46











  • in the project i'm working on in this very minute and experience this exact behavior on physical devices, i have only one target (but i'm using several pods, if that makes any difference)

    – David Seek
    Oct 3 '17 at 18:57











  • I'm by no means an expert, it's just that I've had this behaviour in several projects (they all use multiple pods, i think they all have more than one target too) and this is the first time that I noticed that Xcode was building other targets. Once I switched off Parallelize Build for these other targets - it stopped, i.e. no more repeated building.

    – yuzer
    Oct 3 '17 at 19:54
















6















Please don't mark as duplicate since available threads haven't provided a valid solution.



Since Xcode 9 one of my projects is stuck in a building loop.



The project is building. Running on iPhone and building again and again. Even builds over and over while coding without asking for build or run.



After cleaning, cleaning build folder, deleting Derived Data and restarting, the project crashes after build with:




Command /Applications/Xcode.app/Contents/Developer/usr/bin/ibtool failed with exit code 255. The tool may have crashed. Please file a bug report at http://bugreport.apple.com with the above output and attach any crash logs for ibtool, ibtoold, Xcode, and Interface Builder Cocoa Touch Tool created around the time of this failure. These logs can be found in ~/Library/Logs/DiagnosticReports or /Library/Logs/DiagnosticReports.




After several cleaning and restarting, it finally builds and after a couple of more builds and code changes, the whole process restarts. Building stuck in a loop even without asking to build until 255 exit code.



What am I missing? Help is very appreciated.










share|improve this question




















  • 3





    Same here, I need restart XCode many times during a day! :(

    – Tom Calmon
    Sep 27 '17 at 17:46











  • Seems to be a bug

    – Ludovic
    Sep 28 '17 at 8:05











  • Do you maybe have multiple targets in your project? If so, I managed to stop this behaviour by switching off Edit Scheme / Build / Parallelize Build.

    – yuzer
    Oct 3 '17 at 18:46











  • in the project i'm working on in this very minute and experience this exact behavior on physical devices, i have only one target (but i'm using several pods, if that makes any difference)

    – David Seek
    Oct 3 '17 at 18:57











  • I'm by no means an expert, it's just that I've had this behaviour in several projects (they all use multiple pods, i think they all have more than one target too) and this is the first time that I noticed that Xcode was building other targets. Once I switched off Parallelize Build for these other targets - it stopped, i.e. no more repeated building.

    – yuzer
    Oct 3 '17 at 19:54














6












6








6


5






Please don't mark as duplicate since available threads haven't provided a valid solution.



Since Xcode 9 one of my projects is stuck in a building loop.



The project is building. Running on iPhone and building again and again. Even builds over and over while coding without asking for build or run.



After cleaning, cleaning build folder, deleting Derived Data and restarting, the project crashes after build with:




Command /Applications/Xcode.app/Contents/Developer/usr/bin/ibtool failed with exit code 255. The tool may have crashed. Please file a bug report at http://bugreport.apple.com with the above output and attach any crash logs for ibtool, ibtoold, Xcode, and Interface Builder Cocoa Touch Tool created around the time of this failure. These logs can be found in ~/Library/Logs/DiagnosticReports or /Library/Logs/DiagnosticReports.




After several cleaning and restarting, it finally builds and after a couple of more builds and code changes, the whole process restarts. Building stuck in a loop even without asking to build until 255 exit code.



What am I missing? Help is very appreciated.










share|improve this question
















Please don't mark as duplicate since available threads haven't provided a valid solution.



Since Xcode 9 one of my projects is stuck in a building loop.



The project is building. Running on iPhone and building again and again. Even builds over and over while coding without asking for build or run.



After cleaning, cleaning build folder, deleting Derived Data and restarting, the project crashes after build with:




Command /Applications/Xcode.app/Contents/Developer/usr/bin/ibtool failed with exit code 255. The tool may have crashed. Please file a bug report at http://bugreport.apple.com with the above output and attach any crash logs for ibtool, ibtoold, Xcode, and Interface Builder Cocoa Touch Tool created around the time of this failure. These logs can be found in ~/Library/Logs/DiagnosticReports or /Library/Logs/DiagnosticReports.




After several cleaning and restarting, it finally builds and after a couple of more builds and code changes, the whole process restarts. Building stuck in a loop even without asking to build until 255 exit code.



What am I missing? Help is very appreciated.







xcode






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 26 '17 at 19:59







David Seek

















asked Sep 26 '17 at 17:25









David SeekDavid Seek

8,987960101




8,987960101








  • 3





    Same here, I need restart XCode many times during a day! :(

    – Tom Calmon
    Sep 27 '17 at 17:46











  • Seems to be a bug

    – Ludovic
    Sep 28 '17 at 8:05











  • Do you maybe have multiple targets in your project? If so, I managed to stop this behaviour by switching off Edit Scheme / Build / Parallelize Build.

    – yuzer
    Oct 3 '17 at 18:46











  • in the project i'm working on in this very minute and experience this exact behavior on physical devices, i have only one target (but i'm using several pods, if that makes any difference)

    – David Seek
    Oct 3 '17 at 18:57











  • I'm by no means an expert, it's just that I've had this behaviour in several projects (they all use multiple pods, i think they all have more than one target too) and this is the first time that I noticed that Xcode was building other targets. Once I switched off Parallelize Build for these other targets - it stopped, i.e. no more repeated building.

    – yuzer
    Oct 3 '17 at 19:54














  • 3





    Same here, I need restart XCode many times during a day! :(

    – Tom Calmon
    Sep 27 '17 at 17:46











  • Seems to be a bug

    – Ludovic
    Sep 28 '17 at 8:05











  • Do you maybe have multiple targets in your project? If so, I managed to stop this behaviour by switching off Edit Scheme / Build / Parallelize Build.

    – yuzer
    Oct 3 '17 at 18:46











  • in the project i'm working on in this very minute and experience this exact behavior on physical devices, i have only one target (but i'm using several pods, if that makes any difference)

    – David Seek
    Oct 3 '17 at 18:57











  • I'm by no means an expert, it's just that I've had this behaviour in several projects (they all use multiple pods, i think they all have more than one target too) and this is the first time that I noticed that Xcode was building other targets. Once I switched off Parallelize Build for these other targets - it stopped, i.e. no more repeated building.

    – yuzer
    Oct 3 '17 at 19:54








3




3





Same here, I need restart XCode many times during a day! :(

– Tom Calmon
Sep 27 '17 at 17:46





Same here, I need restart XCode many times during a day! :(

– Tom Calmon
Sep 27 '17 at 17:46













Seems to be a bug

– Ludovic
Sep 28 '17 at 8:05





Seems to be a bug

– Ludovic
Sep 28 '17 at 8:05













Do you maybe have multiple targets in your project? If so, I managed to stop this behaviour by switching off Edit Scheme / Build / Parallelize Build.

– yuzer
Oct 3 '17 at 18:46





Do you maybe have multiple targets in your project? If so, I managed to stop this behaviour by switching off Edit Scheme / Build / Parallelize Build.

– yuzer
Oct 3 '17 at 18:46













in the project i'm working on in this very minute and experience this exact behavior on physical devices, i have only one target (but i'm using several pods, if that makes any difference)

– David Seek
Oct 3 '17 at 18:57





in the project i'm working on in this very minute and experience this exact behavior on physical devices, i have only one target (but i'm using several pods, if that makes any difference)

– David Seek
Oct 3 '17 at 18:57













I'm by no means an expert, it's just that I've had this behaviour in several projects (they all use multiple pods, i think they all have more than one target too) and this is the first time that I noticed that Xcode was building other targets. Once I switched off Parallelize Build for these other targets - it stopped, i.e. no more repeated building.

– yuzer
Oct 3 '17 at 19:54





I'm by no means an expert, it's just that I've had this behaviour in several projects (they all use multiple pods, i think they all have more than one target too) and this is the first time that I noticed that Xcode was building other targets. Once I switched off Parallelize Build for these other targets - it stopped, i.e. no more repeated building.

– yuzer
Oct 3 '17 at 19:54












1 Answer
1






active

oldest

votes


















0














We ran into this issue as well and it has been driving us crazy. The workaround is to set the "IBToolNeverDeque" environment variable to "1", which will modify the behaviour of ibtool and make it much more stable. We have just published a detailed blog post about this particular issue and how we came to find this solution here.



One thing which would be nice is finding an easy way to set the environment variable such that it gets set when using Xcode. If possible, set it globally on your system.






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%2f46432479%2fhow-to-fix-xcode-9-building-loop-until-exit-code-255%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














    We ran into this issue as well and it has been driving us crazy. The workaround is to set the "IBToolNeverDeque" environment variable to "1", which will modify the behaviour of ibtool and make it much more stable. We have just published a detailed blog post about this particular issue and how we came to find this solution here.



    One thing which would be nice is finding an easy way to set the environment variable such that it gets set when using Xcode. If possible, set it globally on your system.






    share|improve this answer




























      0














      We ran into this issue as well and it has been driving us crazy. The workaround is to set the "IBToolNeverDeque" environment variable to "1", which will modify the behaviour of ibtool and make it much more stable. We have just published a detailed blog post about this particular issue and how we came to find this solution here.



      One thing which would be nice is finding an easy way to set the environment variable such that it gets set when using Xcode. If possible, set it globally on your system.






      share|improve this answer


























        0












        0








        0







        We ran into this issue as well and it has been driving us crazy. The workaround is to set the "IBToolNeverDeque" environment variable to "1", which will modify the behaviour of ibtool and make it much more stable. We have just published a detailed blog post about this particular issue and how we came to find this solution here.



        One thing which would be nice is finding an easy way to set the environment variable such that it gets set when using Xcode. If possible, set it globally on your system.






        share|improve this answer













        We ran into this issue as well and it has been driving us crazy. The workaround is to set the "IBToolNeverDeque" environment variable to "1", which will modify the behaviour of ibtool and make it much more stable. We have just published a detailed blog post about this particular issue and how we came to find this solution here.



        One thing which would be nice is finding an easy way to set the environment variable such that it gets set when using Xcode. If possible, set it globally on your system.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 15 '18 at 22:22









        awakecodingawakecoding

        193110




        193110






























            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%2f46432479%2fhow-to-fix-xcode-9-building-loop-until-exit-code-255%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







            Popular posts from this blog

            鏡平學校

            ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

            Why https connections are so slow when debugging (stepping over) in Java?