okay so as per the hypothetical situation as and crash is observed in the system so it may be any kind of issue maybe an exception maybe an inner maybe or anything it can be anything okay so first of all the practice we follow to debug in to F to efficiently debug this code is basically we apply logs so there are basically basically many types of logs that is verbose level logs information level logs debug level logs and error level logs so all these logs we use in our application and everywhere the application can throw an error okay so first of all I'll go to my lock at in the Android studio and I'll just search where the flow actually crashed on my emulator emulator or hardware anything anyway so first of all I'll check for the logs where it crash suppose on screen one pressing on a button one the application crashed okay so now I'll check after pressing of the button one what what has happened such that the application is crashing so for example the button the view of the button may not have been in initialized by using data binding or a fine view by ID so so because of that the application may get crashed when I click on that button so I'll just go through the logs first so I'll see the last log that is printed in my locket and after which it has been printed so after once I find my error I'll I'll try to check I'll try to check around my code like what has gone wrong there and if it's an obvious silly mistake it can be resolved then and there but if it's an complex issue then we need to create some POC's of similar kind on a smaller scale of applications to test that why it is going wrong so in after if if I am not able to find it in my locket like in the locket sometimes the values are missed as it goes very fast and so the next step what I would do is I would apply a debugger attach a debugger to my application so now I will attach a debugger to my application and I'll take it to the point where the crash has happened and then click on the button again and the debugger will start reflecting in my Android studio so now I'll press f8 or step over or step into anything in the debugger to go step by step inside my flow of the code methods and methods inside methods and whatever may cause the crash so with that I will come to know that the what values are being fed suppose it's a null pointer exception so I know that this particular object of the component has not been initialized since it is the value shown in the debugger is null so likewise I'll try to I try to debug my code and resolve the issues
