Yes, so recently there was a bug at our end, I'll not go to go in the details, but I'll just give a gist of it about what that bug was. So the bug was kind of actually suppose there is a IVI level UI, okay, and it has hard keys along with soft keys, and our application is running in the IVI screen, okay, so now my screen is displayed. And now suppose I press a hard key button. So what whenever a hard key button is pressed, so it has the highest priority in an IVI system. So whatever the hard keys, the function will be initiated. Okay, so now what happens suppose I have a screen and update going on and you press an hard key. So now the since the hard key is suppose a home button, okay, so now a home button is pressed and my application is in the middle of the user consent, okay, so it is basically asking would you like to proceed with an update and some and the user then presses the hard key and screen moves on to the home screen and now my user consent pop up has gone. Okay, so what will happen here since the scenario is it should not get dismissed and it should not flicker because when the home first the home screen will be displayed and then pop up will reappear again. But that is not that was not the requirement from our client. So he does not want the screen to flicker like the pop up is being displayed already and then we press the home button and there's a slight flicker between the transitioning behind behind where the home button home screen is transited and then the pop up appears again. So such flicker was not expected by the client. So here we were stuck for quite a long time but then using some unconventional methods like since the priority of the home button like the hard keys is the highest in an IVA system. Okay, so now I cannot achieve that my requirement of pop up not getting dismissed and display again and basically giving an effect of a flicker. So now how will I handle it? So basically, I had to work with other teams and ultimately I came up with a solution that we should give that particular since it was only a singular use case, we can give that pop up the priority of the hard key event, okay, since it is an update pop up. So it is very necessary for the user to press a yes or no to perform the update or cancel the update till then the pop up won't dismiss it by itself. Okay, so now, what I had to do my pop up was of the type toast, okay. So the type of my pop up was a toast and the hard key event screen has the highest priority of type overlay. Okay, so these are the types that are defined in a window manager and a custom overlay that basically a screen is being converted to an custom overlay. Okay, so now what was done here was I, I had to change the type of my pop up from toast, which is by default given to it by the Android system to the overlay, which was not totally conventional since the hard key should always have the highest priority and no other screens should have the priority same as this, but we had taken the client confirmation and I had to convert that particular pop up from a toast to an overlay and due to which now when the home button, hard key button was basically pressed, so there was no flicker. It was simultaneous like my pop up was my pop up kept displaying and the background screen changed to home. So that was an expected behavior where no flicker was observed and we could achieve our requirement finally. So that's how I have done one of the unconventional bug solving.
