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

Corporate Slack session doesn't stay logged-in on the main Wavebox window #1154

Closed
rfgamaral opened this issue Dec 10, 2019 · 6 comments
Closed

Comments

@rfgamaral
Copy link

rfgamaral commented Dec 10, 2019

  • Wavebox Version: 4.11.5beta
  • Operating System & Version: Windows 10
  • Account type (if applicable): Slack

Expected & actual behavior
When my corporate Slack expires I get this screen:
image
After clicking "Sign In", I have to sign back into my workspace so I'm presented with this:
image
I enter my workspace name, click "Continue" and I enter my credentials to login (I have 2 choices here, OAuth with Microsoft Sign-in or user/password, the problem exist with both). After this, I'm properly logged into my corporate Slack workspace but in a pop-up window instead of the main Wavebox window. This pop-up window quickly closes itself and the following screen is displayed continuously until I click anywhere or the "Minimize" button:
image
And then I'm brought back to this screen:
image

Steps to reproduce
I have no idea...

Is the bug persistent or intermittent?
This happens every time my corporate Slack session expires and sometimes, after logging in multiple times, eventually, one of those work correctly and the main Wavebox window displays my Slack window, a lot of the times, it doesn't.

@Thomas101
Copy link
Member

Thanks - should be a fix heading out for this tomorrow :)

@rfgamaral
Copy link
Author

Thanks - should be a fix heading out for this tomorrow :)

Is that fix coming to the Slack service or to Wavebox itself?

@Thomas101
Copy link
Member

It's been fixed in Wavebox 4.11.6 which is now available

@rfgamaral
Copy link
Author

Currently using Wavebox v4.11.11 and I started having this issue again today...

@Thomas101
Copy link
Member

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

@rfgamaral
Copy link
Author

I'm sorry but I don't like Wavebox 10, it doesn't allow me to customize everything as the current Wavebox does. Until feature parity is completed, Wavebox 10 is not for me. I've mentiond this in the Wavebox 10 issue in the past.

Is there nothing that can be done with the current Wavebox version to solve this? It's only happening with Slack and the corporate version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants