Why are the changes I make in my Storyboard (Xcode) not being reflected on my app?












1















I've been working on an app recently but I ran into an annoying issue. None of the changes I've been making to my storyboard have been reflected on my iPhone (which is being used instead of the simulator).



I've already tried a lot of things such as cleaning the build folder, deleting provisioning profiles, deleting the app on my phone and rebooting it, etc. Any ideas on what else I could do to fix it, or what's causing all of this?



Thanks



(Sorry if it sounds a bit unclear, I just have a hard time describing it)






ios xcode storyboard







share|improve this question

























  • I think there will be some custom lib or any kind of control that is having a custom class like your text field or your button have custom class and it's having problem to update frames so that could be an issue and if you remove it, It will work well check your recent designed screens only.

    – iOS Team
    Jan 2 at 5:46
















1















I've been working on an app recently but I ran into an annoying issue. None of the changes I've been making to my storyboard have been reflected on my iPhone (which is being used instead of the simulator).



I've already tried a lot of things such as cleaning the build folder, deleting provisioning profiles, deleting the app on my phone and rebooting it, etc. Any ideas on what else I could do to fix it, or what's causing all of this?



Thanks



(Sorry if it sounds a bit unclear, I just have a hard time describing it)






ios xcode storyboard







share|improve this question

























  • I think there will be some custom lib or any kind of control that is having a custom class like your text field or your button have custom class and it's having problem to update frames so that could be an issue and if you remove it, It will work well check your recent designed screens only.

    – iOS Team
    Jan 2 at 5:46














1












1








1








I've been working on an app recently but I ran into an annoying issue. None of the changes I've been making to my storyboard have been reflected on my iPhone (which is being used instead of the simulator).



I've already tried a lot of things such as cleaning the build folder, deleting provisioning profiles, deleting the app on my phone and rebooting it, etc. Any ideas on what else I could do to fix it, or what's causing all of this?



Thanks



(Sorry if it sounds a bit unclear, I just have a hard time describing it)






ios xcode storyboard







share|improve this question
















I've been working on an app recently but I ran into an annoying issue. None of the changes I've been making to my storyboard have been reflected on my iPhone (which is being used instead of the simulator).



I've already tried a lot of things such as cleaning the build folder, deleting provisioning profiles, deleting the app on my phone and rebooting it, etc. Any ideas on what else I could do to fix it, or what's causing all of this?



Thanks



(Sorry if it sounds a bit unclear, I just have a hard time describing it)






ios xcode storyboard




ios xcode storyboard






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 2 at 3:28









rmaddy

243k27321383




243k27321383










asked Jan 2 at 3:27









SakunSakun

82




82













  • I think there will be some custom lib or any kind of control that is having a custom class like your text field or your button have custom class and it's having problem to update frames so that could be an issue and if you remove it, It will work well check your recent designed screens only.

    – iOS Team
    Jan 2 at 5:46



















  • I think there will be some custom lib or any kind of control that is having a custom class like your text field or your button have custom class and it's having problem to update frames so that could be an issue and if you remove it, It will work well check your recent designed screens only.

    – iOS Team
    Jan 2 at 5:46

















I think there will be some custom lib or any kind of control that is having a custom class like your text field or your button have custom class and it's having problem to update frames so that could be an issue and if you remove it, It will work well check your recent designed screens only.

– iOS Team
Jan 2 at 5:46





I think there will be some custom lib or any kind of control that is having a custom class like your text field or your button have custom class and it's having problem to update frames so that could be an issue and if you remove it, It will work well check your recent designed screens only.

– iOS Team
Jan 2 at 5:46












2 Answers
2






active

oldest

votes


















1














There could be a myriad of reasons why this could be happening, some of which can be indeterministic in nature.



I'll just list a few fixes down, although some of these you've already tried.




  1. Clean and rebuild.

  2. Quit xCode, delete derived data folder. Deploy again.

  3. Delete the app from your device.

  4. The storboard that you are making changes to, is not the one that is being used in the app.


I think the last one might be related to you. (or whatever changes that you are making, get overwritten by something other code in the app.)






share|improve this answer



















  • 1





    Damn I did everything on your list except clear my derived data folder, turns out that was the solution after all! Thank you!

    – Sakun
    Jan 2 at 15:05











  • Glad that fixed it. :)

    – S Shahid
    Jan 3 at 1:44











  • Damn it, it fixed it for a second and now it went back to what it was doing before. Clearing the Derived Data folder doesn't seem to be doing anything anymore :(

    – Sakun
    Jan 3 at 2:23



















1














As mentioned answer above is correct,



However, The main reason of occurring these issues is of cache memory. As we work and manage lots of things via xcode. Xcode manage all their stuff, so after lot of working there are some cases happened(like: internal source engine crashed for some reason) when our changes are not reflected in the form of output and the reason is made because of cache and derived data are recalled. As mentioned the steps, these will again reset and clear the cache and on working with xcode editor your work will reflected correctly.



It will be a best practice to delete all your derived data and module cache once in a week so there will be no issue occurred during your critical workload.






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%2f54000897%2fwhy-are-the-changes-i-make-in-my-storyboard-xcode-not-being-reflected-on-my-ap%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    There could be a myriad of reasons why this could be happening, some of which can be indeterministic in nature.



    I'll just list a few fixes down, although some of these you've already tried.




    1. Clean and rebuild.

    2. Quit xCode, delete derived data folder. Deploy again.

    3. Delete the app from your device.

    4. The storboard that you are making changes to, is not the one that is being used in the app.


    I think the last one might be related to you. (or whatever changes that you are making, get overwritten by something other code in the app.)






    share|improve this answer



















    • 1





      Damn I did everything on your list except clear my derived data folder, turns out that was the solution after all! Thank you!

      – Sakun
      Jan 2 at 15:05











    • Glad that fixed it. :)

      – S Shahid
      Jan 3 at 1:44











    • Damn it, it fixed it for a second and now it went back to what it was doing before. Clearing the Derived Data folder doesn't seem to be doing anything anymore :(

      – Sakun
      Jan 3 at 2:23
















    1














    There could be a myriad of reasons why this could be happening, some of which can be indeterministic in nature.



    I'll just list a few fixes down, although some of these you've already tried.




    1. Clean and rebuild.

    2. Quit xCode, delete derived data folder. Deploy again.

    3. Delete the app from your device.

    4. The storboard that you are making changes to, is not the one that is being used in the app.


    I think the last one might be related to you. (or whatever changes that you are making, get overwritten by something other code in the app.)






    share|improve this answer



















    • 1





      Damn I did everything on your list except clear my derived data folder, turns out that was the solution after all! Thank you!

      – Sakun
      Jan 2 at 15:05











    • Glad that fixed it. :)

      – S Shahid
      Jan 3 at 1:44











    • Damn it, it fixed it for a second and now it went back to what it was doing before. Clearing the Derived Data folder doesn't seem to be doing anything anymore :(

      – Sakun
      Jan 3 at 2:23














    1












    1








    1







    There could be a myriad of reasons why this could be happening, some of which can be indeterministic in nature.



    I'll just list a few fixes down, although some of these you've already tried.




    1. Clean and rebuild.

    2. Quit xCode, delete derived data folder. Deploy again.

    3. Delete the app from your device.

    4. The storboard that you are making changes to, is not the one that is being used in the app.


    I think the last one might be related to you. (or whatever changes that you are making, get overwritten by something other code in the app.)






    share|improve this answer













    There could be a myriad of reasons why this could be happening, some of which can be indeterministic in nature.



    I'll just list a few fixes down, although some of these you've already tried.




    1. Clean and rebuild.

    2. Quit xCode, delete derived data folder. Deploy again.

    3. Delete the app from your device.

    4. The storboard that you are making changes to, is not the one that is being used in the app.


    I think the last one might be related to you. (or whatever changes that you are making, get overwritten by something other code in the app.)







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jan 2 at 3:37









    S ShahidS Shahid

    6,21983754




    6,21983754








    • 1





      Damn I did everything on your list except clear my derived data folder, turns out that was the solution after all! Thank you!

      – Sakun
      Jan 2 at 15:05











    • Glad that fixed it. :)

      – S Shahid
      Jan 3 at 1:44











    • Damn it, it fixed it for a second and now it went back to what it was doing before. Clearing the Derived Data folder doesn't seem to be doing anything anymore :(

      – Sakun
      Jan 3 at 2:23














    • 1





      Damn I did everything on your list except clear my derived data folder, turns out that was the solution after all! Thank you!

      – Sakun
      Jan 2 at 15:05











    • Glad that fixed it. :)

      – S Shahid
      Jan 3 at 1:44











    • Damn it, it fixed it for a second and now it went back to what it was doing before. Clearing the Derived Data folder doesn't seem to be doing anything anymore :(

      – Sakun
      Jan 3 at 2:23








    1




    1





    Damn I did everything on your list except clear my derived data folder, turns out that was the solution after all! Thank you!

    – Sakun
    Jan 2 at 15:05





    Damn I did everything on your list except clear my derived data folder, turns out that was the solution after all! Thank you!

    – Sakun
    Jan 2 at 15:05













    Glad that fixed it. :)

    – S Shahid
    Jan 3 at 1:44





    Glad that fixed it. :)

    – S Shahid
    Jan 3 at 1:44













    Damn it, it fixed it for a second and now it went back to what it was doing before. Clearing the Derived Data folder doesn't seem to be doing anything anymore :(

    – Sakun
    Jan 3 at 2:23





    Damn it, it fixed it for a second and now it went back to what it was doing before. Clearing the Derived Data folder doesn't seem to be doing anything anymore :(

    – Sakun
    Jan 3 at 2:23













    1














    As mentioned answer above is correct,



    However, The main reason of occurring these issues is of cache memory. As we work and manage lots of things via xcode. Xcode manage all their stuff, so after lot of working there are some cases happened(like: internal source engine crashed for some reason) when our changes are not reflected in the form of output and the reason is made because of cache and derived data are recalled. As mentioned the steps, these will again reset and clear the cache and on working with xcode editor your work will reflected correctly.



    It will be a best practice to delete all your derived data and module cache once in a week so there will be no issue occurred during your critical workload.






    share|improve this answer






























      1














      As mentioned answer above is correct,



      However, The main reason of occurring these issues is of cache memory. As we work and manage lots of things via xcode. Xcode manage all their stuff, so after lot of working there are some cases happened(like: internal source engine crashed for some reason) when our changes are not reflected in the form of output and the reason is made because of cache and derived data are recalled. As mentioned the steps, these will again reset and clear the cache and on working with xcode editor your work will reflected correctly.



      It will be a best practice to delete all your derived data and module cache once in a week so there will be no issue occurred during your critical workload.






      share|improve this answer




























        1












        1








        1







        As mentioned answer above is correct,



        However, The main reason of occurring these issues is of cache memory. As we work and manage lots of things via xcode. Xcode manage all their stuff, so after lot of working there are some cases happened(like: internal source engine crashed for some reason) when our changes are not reflected in the form of output and the reason is made because of cache and derived data are recalled. As mentioned the steps, these will again reset and clear the cache and on working with xcode editor your work will reflected correctly.



        It will be a best practice to delete all your derived data and module cache once in a week so there will be no issue occurred during your critical workload.






        share|improve this answer















        As mentioned answer above is correct,



        However, The main reason of occurring these issues is of cache memory. As we work and manage lots of things via xcode. Xcode manage all their stuff, so after lot of working there are some cases happened(like: internal source engine crashed for some reason) when our changes are not reflected in the form of output and the reason is made because of cache and derived data are recalled. As mentioned the steps, these will again reset and clear the cache and on working with xcode editor your work will reflected correctly.



        It will be a best practice to delete all your derived data and module cache once in a week so there will be no issue occurred during your critical workload.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jan 3 at 7:28

























        answered Jan 3 at 6:19









        Gourav JoshiGourav Joshi

        1,71021937




        1,71021937






























            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%2f54000897%2fwhy-are-the-changes-i-make-in-my-storyboard-xcode-not-being-reflected-on-my-ap%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

            Monofisismo

            Image
            Monofisismo (do grego: monos - "único, singular" e physis - "natureza") é o ponto de vista cristológico que defende que, depois da união do divino e do humano na encarnação histórica, Jesus Cristo, como encarnação do Filho ou Verbo ( Logos ) de Deus, teria apenas uma única "natureza", a divina, e não uma síntese de ambas. O monofisismo é contraposto pelo diofisismo (ou "diafisismo"), que defende que Jesus preservou em si as duas naturezas. Historicamente, o monofisismo se refere primordialmente à posição dos que (especialmente no Egito e, em menor grau, na Síria) rejeitaram as decisões do Concílio de Calcedônia em 451 (o quarto concílio ecumênico). Os membros mais moderados entre eles, porém, defendem a teologia "miafisita", que se tornou a oficial para as Igrejas Ortodoxas Orientais. Muitos ortodoxos orientais, porém, rejeitam essa classificação, mesmo como um termo genérico, mas ele é amplamente utilizado na literatura históri...
            Read more

            Angular Downloading a file using contenturl with Basic Authentication

            Image
            0 I have a contentUrl when user clicks on that,file should be downloaded. If I try to browse the contentUrl in the browser it asks for Userid and password.I believe this is Basic Authentication.I dont want user to enter UserId and Password so I am passing it Authorization(Please see below code). Url looks some thing like this: http://XXX.XXX.XX.XXX:8080/flowable-rest/service/runtime/tasks/90875/attachments/90555/content let username : string = 'admin'; let pwd : string = 'test'; let headers = new Headers(); headers.set('Accept', 'text/json'); headers.append('Content-Type', 'application/json'); headers.set('Access-Control-Allow-Origin', '*'); headers.set('Access-Control-Allow-Methods','POST, GET, OPTIONS, PUT, DELETE'); head...
            Read more

            Olmecas

            Image
            Monumento 1, uma das quatro cabeças colossais encontradas em La Venta, com altura aproximada de 3 metros Olmecas é a designação do povo e da civilização que estiveram na origem da antiga cultura pré-colombiana da Mesoamérica e que se desenvolveram nas regiões tropicais do centro-sul do atual México durante o pré-clássico, próximo de onde hoje estão localizados os estados mexicanos de Veracruz e Tabasco, no Istmo de Tehuantepec, numa zona designada área nuclear olmeca. A cultura olmeca floresceu nesta região aproximadamente entre 1500 e 400 a.C., [ 1 ] e crê-se que tenha sido a civilização-mãe de todas as civilizações mesoamericanas que se desenvolveram posteriormente. [ 2 ] No entanto, desconhece-se a sua exacta filiação étnica, ainda que existam numerosas hipóteses colocadas para tentar resolver esta questão. O etnónimo olmeca foi cunhado pelos arqueólogos do século XX, e não devem confundir-se com os muito posteriores olmecas-xicalancas que ocuparam vários locais do México...
            Read more