Hi @crysports, thanks for making this contribution. I see the PO has acknowledged and fixed this report in the latest version . Are you aware you can include in your reports an analysis of what possibly

Hi @masudrana, thanks for making this report The crash log was really helpful. Although the project maintainer thinks it has the same cause as the issue opened by you here - I believe fixing the previous

Hi @italyonion, thanks for making this contribution It appears you are a new contributor to steemit and Utopian. You only opened this account in May, and your first post is a bug-hunting contribution to

Hi @horpeyloaded, thanks for making this contribution. For an application that is designed for mobile users, one would think the developers would go a far way to make it as mobile responsive as possible.

Hi @horpeyloaded, thanks for making this contribution. This is particularly strange. Could be an issue with the set PATH, but then one has to set unique paths for every share service. What do you think

Hi @masudrana, thanks for making this contribution. I can see the project maintainer has acknowledged and fixed the issue in the application's latest release version. Thanks for providing us with a crash

Hi @horpeyloaded, thanks for making this contribution. This is strange. What do you think may have caused this? Are you aware you can include in your reports an analysis of what possibly led to the bug?

Hi @blockchainstudio, thanks for making this contribution. Great to see this has been fixed in SC3 by the steemconnect team. I am in shock that this was not initially implemented in SC2. Considering the

Hi @darewealth, thanks for making this report I see the PO has acknowledged and closed the issue. The crash log must have been helpful in locating the root cause. I look forward to more of your reports.

Hi @harry-heightz, thanks for making this contribution. Thanks for providing us with a crash log. Unfortunately, one can barely make out any useful information as to the reason of the crash. In other words,

Hi @xamir5, thanks for making this contribution I see that the PO has acknowledged the report with a promise to come up with a fix. I appreciate the effort you took in providing us with a logcat> .

Hi @ckole, thanks for making this report A logcat will have been really helpful in this case. Without it, I doubt if we can tell what actually went wrong. This could be a conflict that arose from the two

Hi @ckole, thanks for making this report The log provided here only contains information on the background activity before the application was launched. There is really not much to pick out. To do what

Hi @ckole, thanks for making this contribution. The log you provided is difficult to read. The formatting could be better. I kind of agree with what the PO said - that it could be an issue with the limitation

Hi @crysports, thanks for making this report. It appears to have been fixed in the latest release version. Are you aware you can include in your reports an analysis of what possibly led to the bug? For

Hi @rufans, thanks for making this report. I appreciate the effort in providing a logcat. This one is however bulky and could have maybe been trimmed to show just the important information - the trace

You can just google how to. Or look up this link -

Hi @ckole, thanks for this contribution. The problem here is that the app crashed and not that the music stopped when you clicked exit. Exit like the name implies should completely revoke your access to

Hi @asad44, thanks for making this report I see it has been acknowledged by the project maintainers and appears to be fixed. It seems the build did not previously support android 6.0 and below. Are you

Hi @masudrana, thanks for making this contribution. The cause of this issue is identical to your previous reports. The application attempts to make a write request to local storage but is denied. Write