Swift: Debug mode not working on Test flight











up vote
3
down vote

favorite












in my project I have code surrounded by marks of DEBUG mode #if DEBUG like this:



#if DEBUG
let goToMainScreensGesture = UITapGestureRecognizer(target: self, action: #selector(navigateToMainStoryboard(_:)))
goToMainScreensGesture.delegate = self
goToMainScreensGesture.numberOfTapsRequired = 2
logoLargeImageView.isUserInteractionEnabled = true
logoLargeImageView.addGestureRecognizer(goToMainScreensGesture)
#endif


But that does not work, is there another alternative to add my own debug mode?



On TestFlight, Apple is automatically moving Debug mode apps to Release mode.
I need to add my own global debug mode to the app for the debugging features to work.



What is the best practices on how to do this right?










share|improve this question






















  • In the project, in which scheme is that macro set, and when you release on TestFlight, which one do you use?
    – Larme
    Nov 11 at 10:09










  • Scheme debug mode
    – Mickael Belhassen
    Nov 11 at 10:13










  • But when you release on that Testflight, what the scheme used? For instance, you can use Debug, Beta and Release. Allowing some new feature on beta.
    – Larme
    Nov 11 at 10:20












  • How do I check it?
    – Mickael Belhassen
    Nov 11 at 10:23










  • Check the on the Archive what scheme it use: stackoverflow.com/questions/21897728/… (to get how find it).
    – Larme
    Nov 11 at 10:24















up vote
3
down vote

favorite












in my project I have code surrounded by marks of DEBUG mode #if DEBUG like this:



#if DEBUG
let goToMainScreensGesture = UITapGestureRecognizer(target: self, action: #selector(navigateToMainStoryboard(_:)))
goToMainScreensGesture.delegate = self
goToMainScreensGesture.numberOfTapsRequired = 2
logoLargeImageView.isUserInteractionEnabled = true
logoLargeImageView.addGestureRecognizer(goToMainScreensGesture)
#endif


But that does not work, is there another alternative to add my own debug mode?



On TestFlight, Apple is automatically moving Debug mode apps to Release mode.
I need to add my own global debug mode to the app for the debugging features to work.



What is the best practices on how to do this right?










share|improve this question






















  • In the project, in which scheme is that macro set, and when you release on TestFlight, which one do you use?
    – Larme
    Nov 11 at 10:09










  • Scheme debug mode
    – Mickael Belhassen
    Nov 11 at 10:13










  • But when you release on that Testflight, what the scheme used? For instance, you can use Debug, Beta and Release. Allowing some new feature on beta.
    – Larme
    Nov 11 at 10:20












  • How do I check it?
    – Mickael Belhassen
    Nov 11 at 10:23










  • Check the on the Archive what scheme it use: stackoverflow.com/questions/21897728/… (to get how find it).
    – Larme
    Nov 11 at 10:24













up vote
3
down vote

favorite









up vote
3
down vote

favorite











in my project I have code surrounded by marks of DEBUG mode #if DEBUG like this:



#if DEBUG
let goToMainScreensGesture = UITapGestureRecognizer(target: self, action: #selector(navigateToMainStoryboard(_:)))
goToMainScreensGesture.delegate = self
goToMainScreensGesture.numberOfTapsRequired = 2
logoLargeImageView.isUserInteractionEnabled = true
logoLargeImageView.addGestureRecognizer(goToMainScreensGesture)
#endif


But that does not work, is there another alternative to add my own debug mode?



On TestFlight, Apple is automatically moving Debug mode apps to Release mode.
I need to add my own global debug mode to the app for the debugging features to work.



What is the best practices on how to do this right?










share|improve this question













in my project I have code surrounded by marks of DEBUG mode #if DEBUG like this:



#if DEBUG
let goToMainScreensGesture = UITapGestureRecognizer(target: self, action: #selector(navigateToMainStoryboard(_:)))
goToMainScreensGesture.delegate = self
goToMainScreensGesture.numberOfTapsRequired = 2
logoLargeImageView.isUserInteractionEnabled = true
logoLargeImageView.addGestureRecognizer(goToMainScreensGesture)
#endif


But that does not work, is there another alternative to add my own debug mode?



On TestFlight, Apple is automatically moving Debug mode apps to Release mode.
I need to add my own global debug mode to the app for the debugging features to work.



What is the best practices on how to do this right?







swift xcode






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 11 at 9:37









Mickael Belhassen

1398




1398












  • In the project, in which scheme is that macro set, and when you release on TestFlight, which one do you use?
    – Larme
    Nov 11 at 10:09










  • Scheme debug mode
    – Mickael Belhassen
    Nov 11 at 10:13










  • But when you release on that Testflight, what the scheme used? For instance, you can use Debug, Beta and Release. Allowing some new feature on beta.
    – Larme
    Nov 11 at 10:20












  • How do I check it?
    – Mickael Belhassen
    Nov 11 at 10:23










  • Check the on the Archive what scheme it use: stackoverflow.com/questions/21897728/… (to get how find it).
    – Larme
    Nov 11 at 10:24


















  • In the project, in which scheme is that macro set, and when you release on TestFlight, which one do you use?
    – Larme
    Nov 11 at 10:09










  • Scheme debug mode
    – Mickael Belhassen
    Nov 11 at 10:13










  • But when you release on that Testflight, what the scheme used? For instance, you can use Debug, Beta and Release. Allowing some new feature on beta.
    – Larme
    Nov 11 at 10:20












  • How do I check it?
    – Mickael Belhassen
    Nov 11 at 10:23










  • Check the on the Archive what scheme it use: stackoverflow.com/questions/21897728/… (to get how find it).
    – Larme
    Nov 11 at 10:24
















In the project, in which scheme is that macro set, and when you release on TestFlight, which one do you use?
– Larme
Nov 11 at 10:09




In the project, in which scheme is that macro set, and when you release on TestFlight, which one do you use?
– Larme
Nov 11 at 10:09












Scheme debug mode
– Mickael Belhassen
Nov 11 at 10:13




Scheme debug mode
– Mickael Belhassen
Nov 11 at 10:13












But when you release on that Testflight, what the scheme used? For instance, you can use Debug, Beta and Release. Allowing some new feature on beta.
– Larme
Nov 11 at 10:20






But when you release on that Testflight, what the scheme used? For instance, you can use Debug, Beta and Release. Allowing some new feature on beta.
– Larme
Nov 11 at 10:20














How do I check it?
– Mickael Belhassen
Nov 11 at 10:23




How do I check it?
– Mickael Belhassen
Nov 11 at 10:23












Check the on the Archive what scheme it use: stackoverflow.com/questions/21897728/… (to get how find it).
– Larme
Nov 11 at 10:24




Check the on the Archive what scheme it use: stackoverflow.com/questions/21897728/… (to get how find it).
– Larme
Nov 11 at 10:24












1 Answer
1






active

oldest

votes

















up vote
0
down vote













Imho, most useful is to create your own custom info.plist variable and check it at runtime. If your debug mode doesn't contain secure data.
Otherwise, you can use 'other linker flags' which depends on your target.






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',
    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%2f53247448%2fswift-debug-mode-not-working-on-test-flight%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








    up vote
    0
    down vote













    Imho, most useful is to create your own custom info.plist variable and check it at runtime. If your debug mode doesn't contain secure data.
    Otherwise, you can use 'other linker flags' which depends on your target.






    share|improve this answer

























      up vote
      0
      down vote













      Imho, most useful is to create your own custom info.plist variable and check it at runtime. If your debug mode doesn't contain secure data.
      Otherwise, you can use 'other linker flags' which depends on your target.






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        Imho, most useful is to create your own custom info.plist variable and check it at runtime. If your debug mode doesn't contain secure data.
        Otherwise, you can use 'other linker flags' which depends on your target.






        share|improve this answer












        Imho, most useful is to create your own custom info.plist variable and check it at runtime. If your debug mode doesn't contain secure data.
        Otherwise, you can use 'other linker flags' which depends on your target.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 11 at 10:57









        Vyacheslav

        13.4k858120




        13.4k858120






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f53247448%2fswift-debug-mode-not-working-on-test-flight%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

            Full-time equivalent

            さくらももこ

            13 indicted, 8 arrested in Calif. drug cartel investigation