Hi @muhammadarif, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. And I see he fixed it in the latest release version. I love that you included a logcat

Hi @friendsmobile, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. I love that you included a logcat but these days we expect a bit of analysis to

Hi @friendsmobile, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. And I see he fixed it in the latest release version. I love that you included a logcat

Hi @peerzadaaabid, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. I love that you included a logcat but these days we expect a bit of analysis to

Hi @tobias-g, thanks for making this contribution The report is very well detailed. I like that you included an analysis. It helped bring to light what exactly went wrong. Your correspondence with the

Hi @muhammadarif, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. I understand that this is not a crash report but we still expect a bit of analysis

Hi @peerzadaaabid, thanks for making this contribution Unfortunately, this issue cannot be scored. I noticed the issue with the long posts was first submitted by you and acknowledged here. Since this was

Hi @friendsmobile, thanks for making this contribution Unfortunately, this contribution cannot be scored. The report is based on a project that is still in its pre-alpha stage. You can confirm this information

Hi @xee-shan, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. Hopefully, a fix is in the works. I see you did not include a logcat. The root cause of

Hi @friendsmobile, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. And I see he fixed it in the latest release version. I love that you included a logcat

Hi @jubreal, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. Took a long while for this to be confirmed but still very legit. I understand that this

Hi @xamir5, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. The PO claims to have fixed this. The fix should be available in the next release version.

Hi @peerzadazeeshan, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. Hopefully, a fix is in the works. I see you did not include a logcat. The root

Hi @friendsmobile, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. And I see he fixed it in this commit - I love that you included a logcat but these

Hi @muhammadarif, thanks for making this contribution Unfortunately, this contribution cannot be scored. Looking at the release page, I can see the PO was aware of the issue and had already fixed it before

Hi @sargoon, thanks for making this report Great to see that this issue has been acknowledged by the PO. I am very hopeful of a fix coming out soonest. Do you know you can include in your reports, an analysis

Hi @muhammadarif, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. And I see he fixed it in the latest release version. I love that you included a logcat

Hi @sagorahmed, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. And I see he fixed it in this commit - I love that you included a logcat but these days

Hi @xamir5, thanks for providing this report I can see that the contribution has been acknowledged by the PO. Hopefully, a fix is in the works. I love that you included a logcat but these days we expect

Hi @tobias-g, thanks for making this contribution It is very well detailed. I like that you included an analysis. It helped bring to light what exactly went wrong. Your answers to the PO's questions were