rusq / slackdump

Save or export your private and public Slack messages, threads, files, and users locally without admin privileges.
GNU General Public License v3.0
813 stars 60 forks source link

Exits at login stage #289

Open doppelganger007 opened 1 month ago

doppelganger007 commented 1 month ago

Describe the bug I choose Email (automatic) and then input my Slack login info on the login screen. When I hit return, the window closes but nothing else opens. The same thing happens when I try other login options (Email manual, Manual, SSO).

Authentication type (please read) Tried entering my information manually and using SSO sign-on with Google.

To Reproduce Steps to reproduce the behavior:

  1. Run slackdump from Windows Command Prompt. Follow the tree of choices to anywhere that eventually leads to a login page.

Expected behavior I'm guessing a window's supposed to pop up showing that I've logged in, so that I can proceed with the export.

Output The Slackdump window disappears and no information appears.

Desktop (please complete the following information):

KrisPistofferson commented 3 weeks ago

Hi @doppelganger007 Did you have any luck with this? I'm getting the same issue

Thanks

rusq commented 3 weeks ago

Hey, friends, sorry about the delay. What version are you both using?

For version 2.5+

  1. Run the auth reset to ensure that nothing is left: .\slackdump.exe -auth-reset
  2. Try -legacy-browser command line switch like so:
.\slackdump.exe -legacy-browser <add your switches and ids>

For version 3.0+:

  1. Run uninstall: .\slackdump.exe tools uninstall
  2. Run with legacy browser .\slackdump.exe workspace new -legacy-browser <your workspace>
KrisPistofferson commented 3 weeks ago

Hi @rusq

Thanks for getting back. I was running 2.5.8 right out of file explorer (selecting options with the arrows) Do you reckon I'll have more luck if I try the long version through terminal?

Many thanks

rusq commented 4 days ago

Hey @KrisPistofferson, you might have tried already, and it might have not worked. I think your best bet for now is do the manual token extraction, until I get around to fix this.