I'm in. Team name : The Syndicate

Hi @xamir5, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. And I see the issue has been fixed and closed. I love that you included a logcat but these

Hi @darewealth, thanks for making this contribution I see the issue has been acknowledged by the PO. A brief analysis would have helped any reader in understanding the bug further . Still a good contribution.

Hi @blockchainstudio, thanks for making this report I noticed this issue has been fixed, you have made a pull request to that effect. Great of you to have fixed this. I like that you have provided a detailed

Hi @blockchainstudio, thanks for making this report I noticed this issue has been fixed, your pull request was merged. Great of you to have fixed this. I like that you have provided a detailed analysis

Hi @ckole, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. And I see the issue has been fixed and closed. I love that you included a logcat but these

Hi @friendsmobile, thanks for making this contribution Unfortunately this contribution cannot be reviewed. The PO was aware of the bug and had already fixed it in version 1.1.6 of the app, even before

Hi @jerryloyal, thanks for making this contribution Unfortunately, this contribution cannot be reviewed. The new guidelines state that for a contribution to be eligible for a review, it must be acknowledged

Hi @sargoon, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. You have not included a logcat. These days we expect a logcat and a bit of analysis to

Hi @asad44, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. And I see the issue has been fixed and closed. I love that you included a logcat but these

Hi @blockchainstudio, thanks for making this report I noticed this issue has been fixed, your pull request was merged. Great of you to have fixed this. I like that you have provided a detailed analysis

Hi @muhammadarif, 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 complement

Hi @asad44, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. I know that this is not a crash case but these days we expect a bit of analysis to complement

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 @sagorahmed, 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 complement

Hi @asad44, 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 complement

Hi @asad44, thanks for making this contribution I can see that the contribution has been acknowledged by the PO. And I see one of the maintainers fixed it in this pull request - I love that you included

Hi @blockchainstudio, thanks for making this report I noticed this same issue as well while checking the est. account value on the busy.org wallet. I had to use a different frontend for this purpose. I

Hi @friendsmobile, thanks for making this contribution The behaviour described is particularly strange. The selected interval should be updated like expected. I know this is not a crash report but an analysis

Hi @darewealth, thanks for making this contribution The behaviour described is particularly strange. The app is expected to function as expected afterwards. I know this is not a crash report but an analysis