Skip to content

I can't auth to my workspace with Google #524

@sixhobbits

Description

@sixhobbits

Describe the bug

I use Google Auth to log into Slack, so I need to use the 'User Browser' option. Whenever I try to do that I get this error.

2025-06-16 15:16:05 ERROR 004 (Authentication Error): auth error: auth error:
                      │   browser automation error: failed to launch, you may
                      │   need to close your browser first: [launcher] Failed to
                      │   get the debug url: Opening in existing browser
                      │   session. .

I got this in Edge and Chrome (the two options I see).

If I completely quit Chrome and try again, I get

2025-06-16 15:18:03 INFO  ℹ️ Initialising browser, once the browser appears,
                      │   login as usual

But it hangs on this screen and I can't get any further.

Authentication type (please read)

specify the SSO type, i.e. Google

Google, but can't even get to the step where I choose that.

To Reproduce
Steps to reproduce the behavior:

  • Have an m1 macbook
  • Install slackdump with brew install slackdump
  • Run slackdump archive
  • Choose `Login in browser'
  • Type workspace name acme
  • Choose User Browser
  • Choose Google Chrome

Expected behavior

I'd expect to see my other browsers too (Firefox and Safari) in the options screen.

I'd expect Google Chrome or Edge to show me the slack login page and to let me login with Google.

Output
If applicable, add output to help explain your problem.

2025-06-16 15:16:05 ERROR 004 (Authentication Error): auth error: auth error:
                      │   browser automation error: failed to launch, you may
                      │   need to close your browser first: [launcher] Failed to
                      │   get the debug url: Opening in existing browser
                      │   session. .

Desktop (please complete the following information):

  • OS: Macos
  • OS Version: 15.3.1 (24D70)
  • Slackdump Version: Slackdump 3.1.4 (commit: Homebrew) built on: 2025-06-01T12:04:18Z

Additional context

I also tried with a .env file with token and cookie and it didn't work but I'll open a separate issue for that

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationhelp wantedExtra attention is neededupstreamIssue related to an upstream library

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions