Weavebox Authentication flow of Slack is in a strange state, and doesn't work.

[the-simian]

• Wavebox Version:4.11.11
• Operating System & Version: Mac OSX 10.14.6
• Account type (if applicable): Slack

Expected & actual behavior
sign in on Slack causes the window to appear in the wrong place and not 'replace the sign in' fingerprint window.

Screenshots & Reproduction

1. A slack account in a sandboxed workspace has been signed out, as it does periodically.
   

2. I've tried signing into this account already, and you can see in the pop up it shows it, but also prompts for the space.

3. if I type in the name or select the 'already authenticated item below' what happens is it shows me signing in in that popup. I cannot really capture this as a screenshot (it happens fast). The window is immediately minimized/dissapears. I am left with this screen.
   

4. All I can do is minimise, or click off the modal. Its like in an endless loop now, never really authenticating
   
   All of the slack services on this email are doing this. Its very strange. Usually they periodically sign me out, but these cannot sign back in through wavebox. I can see that slack itself works (I cna sign in on the website). Its something about how wavebox is handling the authentication flow.

[the-simian]

I wanted to add I also use Wavebox on Windows, 64 bit and it works just fine on that platform.

[Thomas101]

Thanks for reporting. It looks like this is down to the third party cookie shakeup that's happening with Chrome.

We launched Wavebox 10 at the end of last year, which is built directly on Chromium so doesn't have some of the same issues that the Wavebox 4 (based on Electron) has in its network architecture.

I'd recommend giving it a try, there's so more info on how to switch here and some info about the underlying changes here.

You can download the latest version here

[the-simian]

@Thomas101 hey thanks for replying, I'll try to migrate when I can. I appreciate you letting me know about the new release as well.

[Jodything]

I am on Wavebox v 10.0.69.2 stable MacOS Catalina and am seeing this same issue.

[Thomas101]

@Jodything someone reported that clearing browsing data under Settings > Profiles seemed to fix this. It would be great to know if this fixes it for you too.

We're having trouble reproducing this with version 10 our end across lots of different slack accounts, so any extra info you have would be really helpful

[Jodything]

Hey @Thomas101 that seemed to do the trick! Thanks for the quick reply

[Jodything]

This particular SSO with slack uses google authenticator for logging in if that info helps at all.

[j0hnm4r5]

This happens to me every time my Slack account decides to log out — I need to clear the profile to get the app to display in the main window instead of a popup.

I also use a Google SSO to log in, and am currently on Wavebox 10.0.54-1 core on macOS 10.15.

[Thomas101]

@j0hnm4r5 it's probably worth updating Wavebox, 10.0.121 is the latest version and has numerous fixes over 10.0.54

[Kukkerem]

I have a similar problem, Version 10.0.493.2 stable, 5.10.30-1-MANJARO x86_64. I have 6 Slack accounts, and after clearing browser data, restarting Wavebox, I can log in for 2-3 seconds, and it throws me back to the "Sign back in" page. It started today before I updated Wavebox.

[robiningelbrecht]

Can confirm this problem

[sschaefa]

Same thing happens since today for all my slack accounts. Clearing cookies & cache did not help.

[robiningelbrecht]

For those who are looking for a "workaround". In Wavebox, I hit CTL+T which opens a new chromium tab and then I just navigated to the web based version of Slack in separate tabs. I know this isn't a fix, but it does the trick for now...

[lskupnjak]

Some thing for me, and it's really annoying :) Using MacOs.

[sschaefa]

Same thing happens since today for all my slack accounts. Clearing cookies & cache did not help.

Now Slack magically works again for all accounts, but the "!" badge is still there, so I don't see unread numbers in the badge. It's something. :-)

[Thomas101]

we've just pushed 10.0.495 out with a fix for this

[robiningelbrecht]

Can confirm the update fixes the problem for me.

[lskupnjak]

@Thomas101 Thank you, it seems the problem is fixed! :)

[sschaefa]

Fixed it for me as well. I am impressed about the response time. Thank you so much!

[the-simian]

I'm no longer experiencing this, thank you