Screen goes black after posting comment

[krestenlaust]

Description
The instant I press send, the screen goes black and the application closes. When I open the app again the screen is just black, and I have to force close the app to restart it.

The comment is submitted and visible.

How to Reproduce I think this is an issue oddly specific to my phone, since it's so simple to reproduce.

1. Make a comment
2. Screen goes black

Screenshots
Difficult to document.

Device & App Version:

• Device: OnePlus 6T
• OS: Android 11
• Version: 0.2.1-alpha.1+11

[krestenlaust]

This is 100% consistent and happens every time. I'm not sure what options I have for providing logs

[hjiangsu]

I have not been able to reproduce this on my end unfortunately, so it's hard for me to figure out the root cause at the moment

[krestenlaust]

Strange. It doesn't do it now. It's happened to me probably 10 times already in the past. I haven't upgraded either.

[krestenlaust]

Is there any logging system I can refer to if this happens again?

[hjiangsu]

There is no logging at the moment, but maybe that might prove useful to have if its do-able. Previously, the logging was done through Sentry as it detects all errors/exceptions, but I've removed that in the latest version

[krestenlaust]

Just wanted to let you know, that this bug still affects me. It's probably half of the time I post.

[hjiangsu]

Is this with the latest pre-release? v0.2.1-alpha.4+13?

[krestenlaust]

I have been using v0.2.1-alpha.1+11. For some reason I haven't been getting update notifications.

[micahmo]

@krestenlaust Since you're using an alpha, I'm assuming you're installing from GitHub? Thunder does not support in-app updates at this time. You might check out Obtainium which is a cool app that can install and keep other apps up-to-date based on GitHub releases.

[krestenlaust]

Thunder used to support in-app update notifications. I might look at Obtainium to replace the lost functionality.

[micahmo]

Thunder used to support in-app update notifications.

Hmm, the code does seem to be there, but it's never worked for me. 😊 @hjiangsu, is this something we officially support? Should we see if it still works?

But yes, Obtainium does the job nicely as well.

[hjiangsu]

Hmm, the code does seem to be there, but it's never worked for me.

It should still be working. I wonder if it stopped because of the migration from my personal GitHub account to the organization account? This might be something we need to double check

[micahmo]

I wonder if it stopped because of the migration from my personal GitHub account to the organization account?

I think it has more to do with the semver parsing. Right now we're doing kind of a primitive string comparison. I'll take a look at this.

[krestenlaust]

This issue just happened on the latest version. I guess I'll have to wait for a logging system to be implemented (#340)

[krestenlaust]

I've managed to produce a screen recording of the issue (mainly to prove my sanity 😄 ) https://github.com/thunder-app/thunder/assets/17174333/542c9c90-8b6c-4b89-a5cf-b63798b69717

Reproductive steps:

1. Create comment
2. Roll the celestial die (50/50)
3. Get a black screen if unlucky.

Force closing the application temporarily resolves the issue.

The comment is still posted, so it isn't a critical issue, but it's an inconvenience.

Edit: for some reason the video won't embed, like in the other thread.

[hjiangsu]

That's really weird, I have no idea what could be causing that issue.

If there was a solid grey screen rather than a black screen,then it could've been a a more reproducible issue (since that usually indicates an error that we can trace back in debug mode)

But because its a black screen, I'm not entirely sure what's happening