Is anyone else having trouble with devRant and connection issues?

@Alice Lol, thank you for verifying Alice! Although I hate it’s happening to others, I’m glad I’m not the only one!

@Alice Devastating... my phone through Verizon has been acting up ever sense I signed the net neutrality petition.

I wasn’t sure if it was just me lol.

Nope works fine for me :)

@linuxxx must be nice! Lol

@AnonyOps Sure xD

Works fine here ☝️

Only when I don't switch TOR circuits for a day or two. 😋

Hmm, weird. I haven’t heard of any issues and none of our monitoring seems to show any problems.

Seems odd that a few people have experienced it here. I’ll keep digging, please let me know if it keeps happening. Thanks!

Yeah, it’s still on-going. What @Alice had said, that’s what’s been going on. Will keep you updated if things improve! Thanks @dfox

Hmmm, very weird. I’ve looked at all of our logs and I don’t see any errors.

When it fails to load, if you refresh right away, does it load successfully?

@Alice very weird - what sorting method are you using?

@Alice that’s really weird. Thanks for the video. I honestly
have no idea what this could be. This rant is the only instance I’ve heard of this. This might be an obvious question - but are you able to connect to other services OK? The rant loading failure video you showed is the same behavior I sometimes see when my phone thinks o have LTE but I really have no connection.

@AnonyOps are you still seeing this behavior?

@Alice hmmm, so weird. I’ve looked at pretty much every log possible. I see no slow queries, no errors, etc.

Maybe try deleting all the local app data?

Also, does this ever happen for more than a few seconds? Like minutes? If it happens for longer, have you been able to try just going to devrant.com in your mobile browser while the issue is happening? I’m curious if it’s accessible for you during the time.

@Alice when you say multiple, is it you and @AnonyOps? Were there any other posts on this? It would help to have any more information.

Though I would say with connection issues, in general I would expect a lot of people to be experiencing it and that’s what we’ve seen in the past when there have been issues.

@dfox Yeah I am, even while using WiFi but before I thought it was just a WiFi connection as the WiFi in my area is shit. But for some reason, I’m having the same issues Alice is having. They come in spurts. I’ll start documenting them all and attempting to gather screenshots etc to help figure out what’s going on. It’s not a huge deal - especially with the limited amount of people experiencing anything similar, but I’ll definitely help you get to the root of the problem.

@AnonyOps thanks, that would be great.

@Alice thanks for checking. Question - how often do you get the rant timeout issue? I can put in some additional logging on the rant load API endpoint and we can match it up with when you get the timeout.

@Alice @AnonyOps I added a debug log to the load rant API. Next time you try to load a rant and it times out, please record the time it happened and let me know. Thanks!

@dfox Thanks for al your help, D! We appreciate it, I’ll definitely log the time stamp. I haven’t had any trouble today, fingers crossed!

@Alice thanks. I was able to match it up exactly with the logging. Unfortunately though, it shows nothing out of the ordinary. The load time for the actual resources on the API call was very quick. So it has to be something else outside the server I think.

When this started happening, was your Android OS updated recently? Also what device/Android version are you using?

@Alice thanks. I’m kind of stumped here.

Only other thing I can think of here is maybe some kind of DNS issue since our DNS ttl is pretty short-lived. Can you close devRant everywhere (app, desktop, etc.) and then wait 10-15 mins (or whenever you want to load it up again) and go to the mobile site first? Whatever hits devrant.com would be caching the DNS response.

Also, did you try restarting your phone?

@dfox 11:49 a loading error has occurred

2:18 update

@Alice @AnonyOps thanks for the additional info. I looked at all of the cases and I wasn’t able to see anything out of the ordinary. I’m trying to think what I could be missing here.

Any other ideas? This is a tricky one. Sorry I haven’t figured I out yet.

@dfox don’t apologize bud, you’re perfectly fine! It’s not a big deal like I said; it’ll work itself out, for all we know it could definitely be on our end. It’s 3:06 am here though and I’ve got to attempt to catch some 💤, I’ll think of a few things and definitely let you know. Don’t stress though!

@AnonyOps thank, I appreciate that!

How has this been the past 2 days?

@dfox I don’t recall seeing anything today and yesterday I don’t either... there is a faint memory of maybe one error occurring earlier in the day yesterday; but other than that I don’t recall anything else.

@AnonyOps thanks, that’s great news! Hopefully it stays like that :)

@dfox Definitely, did you change anything or ever find anything?

@AnonyOps nope, I did not find anything or change anything. Has it still been ok?

@Alice what about you?

It happened again just now at 3:20, but this is the first time in a few days

@dfox it’s happening again bro,

@AnonyOps hmmm, did it happen at all before that since the last time? I still haven’t received any other reports of this.

@Alice that makes sense and I think it’s a good point. I don’t want to try to make it seem like the connection error dialog should never be seen. It’s definitely not perfect and could show up next time you open the app if it was closed during a network request or something, and some other edge cases.

What I would definitely say is a problem is if you’re seeing the dialog while using the app normally once it’s been opened and are on a solid connection. So it kind of depends when it comes up/how often.

It’s happening while using and the majority of the time I force the app closed and it works or a refresh and being patient seems to help, not sure. Anything I can do to help? Like I’ve said earlier it’s not a big deal, just want to make sure it’s known.

@AnonyOps that does seem odd. I’m trying to think how this can be debugged.

I can maybe try adding some more debugging in for when that error shows up. If you can think of any other pattern or timing for when it shows up, that would be helpful too.