Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gumbo does not display the correct stream information. #49

Closed
Straga27 opened this issue May 12, 2022 · 10 comments
Closed

Gumbo does not display the correct stream information. #49

Straga27 opened this issue May 12, 2022 · 10 comments
Labels
bug Something isn't working

Comments

@Straga27
Copy link

Straga27 commented May 12, 2022

Describe the bug
Gumbo is displaying streams that are offline as online and is reporting a runtime of the stream into 60+ hours which is incorrect

To Reproduce
I'm logged into twitch via Gumbo and opening the extension and clicking on followed streams displays the wrong info.

Expected behavior
Opening the followed streams section should display the correct info

Screenshots
image

Desktop (please complete the following information):

  • OS: Windows 10 pro
  • Browser Firefox
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version 100.0

Additional context
I have logged out and re authenticated Gumbo numerous times to try and fix the problem to no avail.

@Straga27 Straga27 added the bug Something isn't working label May 12, 2022
@Seldszar
Copy link
Owner

  • Is clicking the refresh button (the one on the right side of the search bar) does something, like an animation?
  • Did you try re-installing the extension and/or update it?

@Straga27
Copy link
Author

Straga27 commented May 12, 2022 via email

@Seldszar
Copy link
Owner

Seldszar commented May 12, 2022

Can you go to this URL (about:debugging#/runtime/this-firefox), click the extension's "Inspect" button?

While keeping the Toolbox open, open the extension's popup and click the refresh button. Go back to the Toolbox and do the following steps:

  • Go to "Console" and see if there are any errors
  • Go the "Network" tab and see if there are any requests
    If that's the case, is there any requests with a status code other than 200?

@Seldszar
Copy link
Owner

Update about your situation, A new version (1.8.6) is going to be available with the addition of a "Reset Extension" button in Settings ("Advanced" section). I hope this last recourse will finally help.

@Straga27
Copy link
Author

Straga27 commented May 14, 2022 via email

@Seldszar
Copy link
Owner

Sorry but the image you attached isn't viewable. Please upload this image somewhere so I can take a look.

@Straga27
Copy link
Author

My bad.
image
There you go.

@Seldszar
Copy link
Owner

It looks like the API responses have been wrongly cached. Can you, from the Toolbox, do and Ctrl+F5 in order to purge the request cache, then click on the refresh icon in the extension window (top-right icon)?

Hopefully it'll fetch the most recent data. However I don't know how this cache issue happened in the first place, but it doesn't seem to be something on my part because this cache behavior is being dictated by the API server itself. I'll see if I can do add a cache busting for this particular case.

@Straga27
Copy link
Author

Straga27 commented May 21, 2022 via email

@Seldszar
Copy link
Owner

That's what I was thinking as well.

In case other users have this similar issue and for future ones, I changed the fetch mode (3a57c82) so every API request will skip the browser's cache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants