Gumbo does not display the correct stream information.

[Straga27]

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

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.

[Seldszar]

• 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]

Yes and yes.

…

On Thu, 12 May 2022, 12:20 Alexandre Breteau, ***@***.***> wrote: - 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? — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOTJHEVQHULSEHPCK6I3RRDVJTSO5ANCNFSM5VXTC6WQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Seldszar]

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]

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]

Apologies for not getting back to you. There are no errors in the console tab, but in the network tab the three bugged channels in the extension show up with a 302 status code. [image: image.png] For the record this is still happening for sure.

…

On Thu, May 12, 2022 at 2:51 PM Alexandre Breteau ***@***.***> wrote: Can you go to this URL (about:debugging#/runtime/this-firefox), click the extension's "Inspect" button and see if there's any errors in the "Console" tab? If there's no errors, while keeping the toolbox open, can you open the popup, click the refresh button then go to the "Network" tab and see if there's any requests? If that's the case, is there any requests with a status code other than 200? — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOTJHEXMBQXOEMUORKVYULTVJUEFJANCNFSM5VXTC6WQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Seldszar]

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

[Straga27]

My bad.

There you go.

[Seldszar]

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]

I took the nuclear option and just erased all of my cache data for the browser. Uninstalled the extension and then reinstalled it. Fixed. What was making me suspicious was that Gumbo was logged in automatically when I was reinstalling the extension before I took out the entire cache. This lead me to think I had some dodgy cache data from twitch that the extension was falling over I suppose. Thanks for the help! Your extension is great.

…

On Sat, 21 May 2022, 13:56 Alexandre Breteau, ***@***.***> wrote: 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. — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOTJHES6HXV4WWA26CADF2LVLDMQTANCNFSM5VXTC6WQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Seldszar]

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.