AVD process gets killed as soon as I end debugging












0














My Setup is:
Server: Asp.Net and SignalR-Server
App: SignalR-Client



My App uses "Invoke" to invoke a function on my Server which should return a MyObject-Object. But the response isn't arriving at my client and the app 'hangs' in the async void in which the Invoke is located.



As soon as I end the debugging of the app the whole
AVD-Process gets killed with no error message shown in the Emulator or Visual Studio.



I think this happens of a Exception which is 'silently' thrown.



How could the AVD get killed with an Exception of my app?










share|improve this question






















  • Without any code showing what you are doing it is impossible to say what is going on. It is odd that the AVD is getting killed (which I assume means the AD shuts down and the AVD window is closed? Or does the AVD just become non-responsive? ) Also "Async void" methods should be avoided except for event handlers. If there is an exception in an "async void" method (that is not an event handler) it will get swallowed by the runtime. See: docs.microsoft.com/en-us/dotnet/visual-basic/language-reference/…
    – jgoldberger - MSFT
    Nov 19 '18 at 19:05










  • @jgoldberger the emulator process keeps getting killed without any hint why this happens. I am using override functions like OnResume which is by design void...
    – Snickbrack
    Nov 19 '18 at 19:15






  • 1




    Did you add the async keyword to the OnResume method, e.g. protected override async void OnResume()? And if so, are you then awaiting the call to the async method and wrapping it in a try/catch to make sure you catch any exceptions that may happen in the async method? IOW, please show your code.
    – jgoldberger - MSFT
    Nov 19 '18 at 20:10
















0














My Setup is:
Server: Asp.Net and SignalR-Server
App: SignalR-Client



My App uses "Invoke" to invoke a function on my Server which should return a MyObject-Object. But the response isn't arriving at my client and the app 'hangs' in the async void in which the Invoke is located.



As soon as I end the debugging of the app the whole
AVD-Process gets killed with no error message shown in the Emulator or Visual Studio.



I think this happens of a Exception which is 'silently' thrown.



How could the AVD get killed with an Exception of my app?










share|improve this question






















  • Without any code showing what you are doing it is impossible to say what is going on. It is odd that the AVD is getting killed (which I assume means the AD shuts down and the AVD window is closed? Or does the AVD just become non-responsive? ) Also "Async void" methods should be avoided except for event handlers. If there is an exception in an "async void" method (that is not an event handler) it will get swallowed by the runtime. See: docs.microsoft.com/en-us/dotnet/visual-basic/language-reference/…
    – jgoldberger - MSFT
    Nov 19 '18 at 19:05










  • @jgoldberger the emulator process keeps getting killed without any hint why this happens. I am using override functions like OnResume which is by design void...
    – Snickbrack
    Nov 19 '18 at 19:15






  • 1




    Did you add the async keyword to the OnResume method, e.g. protected override async void OnResume()? And if so, are you then awaiting the call to the async method and wrapping it in a try/catch to make sure you catch any exceptions that may happen in the async method? IOW, please show your code.
    – jgoldberger - MSFT
    Nov 19 '18 at 20:10














0












0








0







My Setup is:
Server: Asp.Net and SignalR-Server
App: SignalR-Client



My App uses "Invoke" to invoke a function on my Server which should return a MyObject-Object. But the response isn't arriving at my client and the app 'hangs' in the async void in which the Invoke is located.



As soon as I end the debugging of the app the whole
AVD-Process gets killed with no error message shown in the Emulator or Visual Studio.



I think this happens of a Exception which is 'silently' thrown.



How could the AVD get killed with an Exception of my app?










share|improve this question













My Setup is:
Server: Asp.Net and SignalR-Server
App: SignalR-Client



My App uses "Invoke" to invoke a function on my Server which should return a MyObject-Object. But the response isn't arriving at my client and the app 'hangs' in the async void in which the Invoke is located.



As soon as I end the debugging of the app the whole
AVD-Process gets killed with no error message shown in the Emulator or Visual Studio.



I think this happens of a Exception which is 'silently' thrown.



How could the AVD get killed with an Exception of my app?







android xamarin visual-studio-2017 android-avd






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '18 at 18:12









SnickbrackSnickbrack

388728




388728












  • Without any code showing what you are doing it is impossible to say what is going on. It is odd that the AVD is getting killed (which I assume means the AD shuts down and the AVD window is closed? Or does the AVD just become non-responsive? ) Also "Async void" methods should be avoided except for event handlers. If there is an exception in an "async void" method (that is not an event handler) it will get swallowed by the runtime. See: docs.microsoft.com/en-us/dotnet/visual-basic/language-reference/…
    – jgoldberger - MSFT
    Nov 19 '18 at 19:05










  • @jgoldberger the emulator process keeps getting killed without any hint why this happens. I am using override functions like OnResume which is by design void...
    – Snickbrack
    Nov 19 '18 at 19:15






  • 1




    Did you add the async keyword to the OnResume method, e.g. protected override async void OnResume()? And if so, are you then awaiting the call to the async method and wrapping it in a try/catch to make sure you catch any exceptions that may happen in the async method? IOW, please show your code.
    – jgoldberger - MSFT
    Nov 19 '18 at 20:10


















  • Without any code showing what you are doing it is impossible to say what is going on. It is odd that the AVD is getting killed (which I assume means the AD shuts down and the AVD window is closed? Or does the AVD just become non-responsive? ) Also "Async void" methods should be avoided except for event handlers. If there is an exception in an "async void" method (that is not an event handler) it will get swallowed by the runtime. See: docs.microsoft.com/en-us/dotnet/visual-basic/language-reference/…
    – jgoldberger - MSFT
    Nov 19 '18 at 19:05










  • @jgoldberger the emulator process keeps getting killed without any hint why this happens. I am using override functions like OnResume which is by design void...
    – Snickbrack
    Nov 19 '18 at 19:15






  • 1




    Did you add the async keyword to the OnResume method, e.g. protected override async void OnResume()? And if so, are you then awaiting the call to the async method and wrapping it in a try/catch to make sure you catch any exceptions that may happen in the async method? IOW, please show your code.
    – jgoldberger - MSFT
    Nov 19 '18 at 20:10
















Without any code showing what you are doing it is impossible to say what is going on. It is odd that the AVD is getting killed (which I assume means the AD shuts down and the AVD window is closed? Or does the AVD just become non-responsive? ) Also "Async void" methods should be avoided except for event handlers. If there is an exception in an "async void" method (that is not an event handler) it will get swallowed by the runtime. See: docs.microsoft.com/en-us/dotnet/visual-basic/language-reference/…
– jgoldberger - MSFT
Nov 19 '18 at 19:05




Without any code showing what you are doing it is impossible to say what is going on. It is odd that the AVD is getting killed (which I assume means the AD shuts down and the AVD window is closed? Or does the AVD just become non-responsive? ) Also "Async void" methods should be avoided except for event handlers. If there is an exception in an "async void" method (that is not an event handler) it will get swallowed by the runtime. See: docs.microsoft.com/en-us/dotnet/visual-basic/language-reference/…
– jgoldberger - MSFT
Nov 19 '18 at 19:05












@jgoldberger the emulator process keeps getting killed without any hint why this happens. I am using override functions like OnResume which is by design void...
– Snickbrack
Nov 19 '18 at 19:15




@jgoldberger the emulator process keeps getting killed without any hint why this happens. I am using override functions like OnResume which is by design void...
– Snickbrack
Nov 19 '18 at 19:15




1




1




Did you add the async keyword to the OnResume method, e.g. protected override async void OnResume()? And if so, are you then awaiting the call to the async method and wrapping it in a try/catch to make sure you catch any exceptions that may happen in the async method? IOW, please show your code.
– jgoldberger - MSFT
Nov 19 '18 at 20:10




Did you add the async keyword to the OnResume method, e.g. protected override async void OnResume()? And if so, are you then awaiting the call to the async method and wrapping it in a try/catch to make sure you catch any exceptions that may happen in the async method? IOW, please show your code.
– jgoldberger - MSFT
Nov 19 '18 at 20:10












1 Answer
1






active

oldest

votes


















0














As for many inconsistencies I needed to let Visual Studio clean the whole project.



I think it is an underlying process which does some caching of files or values and then the application itself cannot use the cached data as I changed the usage of this data.



This is really annoying because now I always let Visual Studio clean the code after each edit on the code. And with this procedure I am getting less 'error-less' errors which aren't real errors...



Thanks anyway :)






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%2f53380418%2favd-process-gets-killed-as-soon-as-i-end-debugging%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














    As for many inconsistencies I needed to let Visual Studio clean the whole project.



    I think it is an underlying process which does some caching of files or values and then the application itself cannot use the cached data as I changed the usage of this data.



    This is really annoying because now I always let Visual Studio clean the code after each edit on the code. And with this procedure I am getting less 'error-less' errors which aren't real errors...



    Thanks anyway :)






    share|improve this answer


























      0














      As for many inconsistencies I needed to let Visual Studio clean the whole project.



      I think it is an underlying process which does some caching of files or values and then the application itself cannot use the cached data as I changed the usage of this data.



      This is really annoying because now I always let Visual Studio clean the code after each edit on the code. And with this procedure I am getting less 'error-less' errors which aren't real errors...



      Thanks anyway :)






      share|improve this answer
























        0












        0








        0






        As for many inconsistencies I needed to let Visual Studio clean the whole project.



        I think it is an underlying process which does some caching of files or values and then the application itself cannot use the cached data as I changed the usage of this data.



        This is really annoying because now I always let Visual Studio clean the code after each edit on the code. And with this procedure I am getting less 'error-less' errors which aren't real errors...



        Thanks anyway :)






        share|improve this answer












        As for many inconsistencies I needed to let Visual Studio clean the whole project.



        I think it is an underlying process which does some caching of files or values and then the application itself cannot use the cached data as I changed the usage of this data.



        This is really annoying because now I always let Visual Studio clean the code after each edit on the code. And with this procedure I am getting less 'error-less' errors which aren't real errors...



        Thanks anyway :)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 '18 at 11:49









        SnickbrackSnickbrack

        388728




        388728






























            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%2f53380418%2favd-process-gets-killed-as-soon-as-i-end-debugging%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

            MongoDB - Not Authorized To Execute Command

            How to fix TextFormField cause rebuild widget in Flutter

            in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith