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

token creation error (login) #77

Open
waterfox22 opened this issue Nov 23, 2024 · 2 comments
Open

token creation error (login) #77

waterfox22 opened this issue Nov 23, 2024 · 2 comments

Comments

@waterfox22
Copy link

got a error when launched login in hearthstone folder

libsoup-ERROR **: 04:10:15.215: libsoup3 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.

pacman -Q | grep libsoup outputs: libsoup 2.74.3-1 libsoup3 3.6.1-1

i tried to delete one of the libsoup libraries, but it's impossible since webkit2gtk can't work with only libsoup2 or with only libsoup3 (i tested it)
i tried to reinstall all dependencies, also did pacman -Syu
i tried to compile login.c with libsoup2, got only a black screen

i'm using Arch Linux with KDE Plasma

@waterfox22
Copy link
Author

waterfox22 commented Nov 23, 2024

just now i found a workaround

cd into hearthstone-linux/token/, build an exe with make, you'll get an Token.exe in this dir

now install mono sudo pacman -S mono

open your browser, authorize in battle net, then open dev console in a new tab, select network and go to https://eu.battle.net/login/en/?app=wtcg, in request headers find cookie and find gs-hs= (first row), copy your token after equals sign until ;

then again cd into hearthstone-linux/token/ and execute token encryption mono Token.exe YOUR-TOKEN, it'll create a token file

finally, move token file from hearthstone-linux/token/ to hearthstone-linux/hearthstone/

@0xf4b1
Copy link
Owner

0xf4b1 commented Dec 1, 2024

I'm not really sure what works wrong with libsoup2 and libsoup3, it still works fine on Ubuntu 24.04. as before and I dont know what changed elsewhere.

Yes, you can use the token tool as workaround instead, this was actually the method to store the token before the login tool was contributed.

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