Hi @ammaraisafti, thanks for making this report Just like it were in your previous report, the steps you provided were easy to follow,but the actual and expected behaviors described are mixed up. Please

Hi @ammaraisafti, thanks for making this report While the steps you provided were easy to follow, the actual and expected behaviors you described were mixed up. Please try to place the correct description

Hi @masudrana, thanks for making this report The behavior experienced was totally unexpected. I like how well you collaborated and responded to the PO's inquiries. There was no thorough analysis but I

Hi @xamir5, thanks for making this contribution. The log provided is really precise and should be supported with a detailed explanation. I can see the PO has acknowledged the ticket and fixed it in this

Hi @sagorahmed, thanks for making this contribution The behavior you described is particularly strange and the logcat you provided is pretty precise but can still be supported with a detailed analysis.

Hi @sagorahmed, thanks for making this contribution The log is pretty precise but can still be supported with a detailed analysis. I see the PO has rectified this issue in this commit - . Good of you to

Hi @masudrana, thanks for making this contribution I see this issue has been acknowledged by the PO. The respective descriptions of the actual and expected behaviors were lacking in details and could have

Hi @asad44, thanks for making this contribution. The log provided is really precise and should be supported with a detailed explanation. I can see the PO has acknowledged the ticket. He claims it should

Hi @friendsmobile, thanks for making this contribution. The log provided is really precise and should be supported with a detailed explanation. I can see the PO has acknowledged the ticket. A fix will

Hi @xee-shan, thanks for making this report I see the PO has acknowledged the report. A logcat would have been really helpful to help determine what led to the crash. The behavior is particularly strange.

Hi @asad44, thanks for making this contribution. The log is pretty precise and can still be supported with a detailed explanation. I see the PO has acknowledged the ticket. I am sure he is going to have

Hi @muhammadarif, thanks for making this contribution The log provided is not as precise and should be supported with a detailed explanation. I can see the PO after a careful observation, has acknowledged

Hi @asad44, thanks for making this contribution. The log provided is not as precise and should be supported with a detailed explanation cause I can barely detect any information pointing to the cause of

Hi @asad44, thanks for making this contribution. The log provided is not as precise and should be supported with a detailed explanation. I can see the PO after a careful observation, has acknowledged and

Hi @asad44, thanks for making this contribution. The log provided is not as precise and should be supported with a detailed explanation cause I can barely detect any information pointing to the cause of

Hi @masudrana, thanks for making this contribution. The log provided is not as precise and should be supported with a detailed explanation cause I can barely detect any information pointing to the cause

Hi @sargoon, thanks for making this report I see the PO has acknowledged the report. The logcat you provided does not contain any useful information as to what caused the issue. It is still a wonder as

Hi @ammarraisafti, thanks for making this report I see the PO has acknowledged the report. The behavior is particularly strange. A logcat would have been helpful in discovering the root cause of the issue.

Hi @jubreal, thanks for making this report I see the PO has acknowledged the report. The behavior is particularly strange. A logcat would have been helpful in discovering the root cause of the issue. Good

Hi @ammarraisafti, thanks for making this report I see the PO has acknowledged the report. The behavior is particularly strange. A logcat would have been helpful in discovering the root cause of the issue.