Pedro1664
commented
1 year ago I have reported this issue on my new machine and not yet received any reply, is a fix being worked on?
Closed WisdomSky closed 1 year ago
Pedro1664
commented
1 year ago I have reported this issue on my new machine and not yet received any reply, is a fix being worked on?
tigerinus
commented
1 year ago Describe the bug The main appstore will not display unless if you installed a third-party appstore.
To Reproduce Steps to reproduce the behavior:
- Remove all custom appstores you installed and leave only the main appstore.
- Open CasaOS Dashboard and open the Appstore.
- See the list is empty.
Expected behavior The apps in the main Appstore should be displayed.
Video https://clipchamp.com/watch/rAjO0L6rRvU
Additional context
The weird behavior occurred after the latest commit of the main branch of the Main Appstore.
casaos-cli app-management register app-store https://github.com/IceWhaleTech/CasaOS-AppStore/archive/refs/heads/main.zipBut if you use the commit prior to the latest commit instead, it works fine as usual.
casaos-cli app-management register app-store https://github.com/IceWhaleTech/CasaOS-AppStore/archive/3b573262f064faa29e72a0169e3d4293e599b3e3.zipWith this information, it's surmised that there is something in the latest commit that caused this issue to occur.
Can you share the log by running
sudo journalctl -xef -u casaos-app-management
JaviTio
commented
1 year ago Hello , I have installed the app today, Debian 11 (Proxmox LXC container) and executed 'wget -qO- https://get.casaos.io | sudo bash'
i ran "sudo journalctl -xef -u casaos-app-management",
Jun 27 12:08:27 CasaOs-Debian11 casaos-app-management[578]: 2023-06-27T12:08:27.917Z error error when deserializing {"err": "[]model.ServerAppList: decode slice: expect [ or n, but found \u0000, error found in #0 byte of ...||..., bigger context ...||...", "content": "{\"code\":401,\"mssage\":\"验签失败\"}", "property": "data.list", "func": "v1.(*appStore).AsyncGetServerList", "file": "/home/runner/work/CasaOS-AppManagement/CasaOS-AppManagement/service/v1/appstore.go", "line": 163}
I also i get "content": "{\"code\":401,\"mssage\":\"验签失败\"}" doing 'curl https://api.casaos.io/casaos-api/v2/app/newlist -H "Authorization: token (of course with a valid token)"' (following the guide https://wiki.casaos.io/en/troubleshooting/appstore-does-not-load)
tigerinus
commented
1 year ago Hello , I have installed the app today, Debian 11 (Proxmox LXC container) and executed 'wget -qO- https://get.casaos.io | sudo bash'
i ran "sudo journalctl -xef -u casaos-app-management",
Jun 27 12:08:27 CasaOs-Debian11 casaos-app-management[578]: 2023-06-27T12:08:27.917Z error error when deserializing {"err": "[]model.ServerAppList: decode slice: expect [ or n, but found \u0000, error found in #0 byte of ...||..., bigger context ...||...", "content": "{\"code\":401,\"mssage\":\"验签失败\"}", "property": "data.list", "func": "v1.(*appStore).AsyncGetServerList", "file": "/home/runner/work/CasaOS-AppManagement/CasaOS-AppManagement/service/v1/appstore.go", "line": 163}I also i get
"content": "{\"code\":401,\"mssage\":\"验签失败\"}"doing 'curl https://api.casaos.io/casaos-api/v2/app/newlist -H "Authorization: token (of course with a valid token)"' (following the guide https://wiki.casaos.io/en/troubleshooting/appstore-does-not-load)
This is a different subject from the original issue, which talks about 3rd party AppStore management in 0.4.4-alpha
Your issue is about AppStore loading from released version, either v0.4.3 or earlier.
Closing and locking this issue to avoid more confusion.
@WisdomSky let's continue this conversation over Discord.
Describe the bug The main appstore will not display unless if you installed a third-party appstore.
To Reproduce Steps to reproduce the behavior:
Expected behavior The apps in the main Appstore should be displayed.
Video https://clipchamp.com/watch/rAjO0L6rRvU
Additional context
The weird behavior occurred after the latest commit of the main branch of the Main Appstore.
But if you use the commit prior to the latest commit instead, it works fine as usual.
With this information, it's surmised that there is something in the latest commit that caused this issue to occur.