You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After entering the cmd command "poe-stash-cli.exe --account <YOUR_ACCOUNT> --poesessid <YOUR_POESESSID> --league <YOUR_LEAGUE>" without quotations and < >
The output message is "can't scrap data ScrapEverything: ScrapWholeStash: ScrapStash(0): ParseStashTab: json: cannot unmarshal array into Go struct field StashTab.currencyLayout of type models.Layout"
as shown in Image1.png
Release Information
Adapt to the 3.16 poe release
poe-stash-windows-amd64.zip
To Reproduce
Steps to reproduce the behavior:
Run a CMD in the PoE Stash directory
Enter the command "poe-stash-cli.exe --account <YOUR_ACCOUNT> --poesessid <YOUR_POESESSID> --league <YOUR_LEAGUE>"
Output message shown above
Expected behavior
It will fetch everything and generate an html file you can share with others
Screenshots
Image1.png
Desktop
OS: Windows 10
Browser: Chrome
Version: 102.0.5005.115
Additional context
Using the cmd command "poe-stash-cli.exe --interactive" output''s the same result
The text was updated successfully, but these errors were encountered:
Describe the bug
After entering the cmd command "poe-stash-cli.exe --account <YOUR_ACCOUNT> --poesessid <YOUR_POESESSID> --league <YOUR_LEAGUE>" without quotations and < >
The output message is "can't scrap data ScrapEverything: ScrapWholeStash: ScrapStash(0): ParseStashTab: json: cannot unmarshal array into Go struct field StashTab.currencyLayout of type models.Layout"
as shown in Image1.png
Release Information
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It will fetch everything and generate an html file you can share with others
Screenshots
![Image1](https://user-images.githubusercontent.com/107763971/174447585-635d60a4-3e20-4cf3-a3e4-810042d527e3.PNG)
Image1.png
Desktop
Additional context
Using the cmd command "poe-stash-cli.exe --interactive" output''s the same result
The text was updated successfully, but these errors were encountered: