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

Version 1.7.0.2 not working with latest Version of shiori 1.7.4 #76

Open
rmayergfx opened this issue Jan 9, 2025 · 4 comments
Open

Comments

@rmayergfx
Copy link

rmayergfx commented Jan 9, 2025

Docker Protokoll is showing
INFO[2025-01-09T13:15:16Z] allowing legacy api access using JWT token method=GET path=/api/accounts username=*******

extension settings always shows
grafik

Installing older extension 1.6.0.1 is working fine.
Why is the xpi not avail in the Assets? No v1.7.0.1 or v1.7.0.2 xpi for manual download.

@fmartingr
Copy link
Member

fmartingr commented Jan 10, 2025

Do you have any more information or logs from the browser? I have been using those two versions since their release without issues.

Why is the xpi not avail in the Assets? No v1.7.0.1 or v1.7.0.2 xpi for manual download.

Previously the release process it was more manual so I uploaded the files myself. Right now it's automated and there's no step in the process to upload the artifacts. I should add that at some point.

@philfeu
Copy link

philfeu commented Jan 10, 2025

Exactly the same problem here on Firefox, Windows 11. Fallback to 1.6.01 runs correctly.

@fmartingr
Copy link
Member

@rmayergfx are you running windows as well?

@rmayergfx
Copy link
Author

rmayergfx commented Jan 15, 2025

@fmartingr
WIN10 22H2 with all updates applied, FireFox 134.0.1

Still missing the xpi on the release site for manually installation. What happens to the Chrome extension?

i am also getting ERRO[2025-01-15T09:36:08Z] Failed to check token error="error parsing token: error parsing token: token is malformed: token contains an invalid number of segments"
ERRO[2025-01-15T10:49:22Z] Failed to check token error="error parsing token: error parsing token: token is malformed: token contains an invalid number of segments"

on reboot of the docker container, i don´t know what to change to fix this.

grafik

With the older release 1.6.0.1 i can setup and see in the log
INFO[2025-01-15T10:59:38Z] allowing legacy api access using JWT token method=GET path=/api/bookmarks username=Ralf

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

3 participants