Bugs after latest Vikunja update

pqc · July 23, 2024, 10:27pm

My YunoHost server

Hardware: VPS bought online
YunoHost version: 11.2.23
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

If your request is related to an app, specify its name and version:
Vikunja v0.24.1~ynh1

Description of my issue

I upgraded to the latest Vikunja version, the upgrade was successful. But things aren’t working correctly for me after the upgrade, for example, when I click any of my projects, nothing gets displayed in the main area, just a white screen, or when I try to add a reaction (a new feature in 0.24.0), I get an error (404), the new “Views” feature also isn’t working for me, also gives me an error (404).

I’m wondering if anyone else is running into this issue or if it’s something specific to me.

stilobique · July 24, 2024, 11:48am

Have you look the log app, or the console log ?

pqc · July 25, 2024, 12:40am

Thanks for responding! I looked at the YunoHost logs (before initially posting), it showed that the upgrade was successful, I can’t find any errors in there.

In the web browser console, I see a bunch of Uncaught (in promise) Object { stack: "AxiosError errors.

Maybe I’ll try reinstalling, instead of upgrading.

pqc · July 25, 2024, 3:16am

Maybe I’ll try reinstalling, instead of upgrading.

Just following up, I tried a fresh install and I’m experiencing the same issues.

stilobique · July 25, 2024, 8:21am

Hum, alright, it’s an issue with Vikunja . And not easy to find any help.

pqc · July 26, 2024, 9:01pm

A little more digging into this and from what I’m seeing it looks like an issue w/ YunoHost…

Vikunja version 0.23.0 introduced a change which merged the API and frontend:

Previously, the API and frontend parts of Vikunja were located in separate repositories. This made sense from an architectural point of view, but also meant that you had to deploy both parts individually.

With this release, the two repositories (and the desktop package as well) are merged into one. This enables us to create a single binary release artifact, simplifying the deployment and hosting of Vikunja a lot.

In a nutshell, the API now contains the frontend files as well.

And it looks like (I’m not an expert here) the way Vikunja is built w/ YunoHost, it’s still using the frontend and API separately:

github.com

YunoHost-Apps/vikunja_ynh/blob/e3c10fb15c1e0fc4084cde982c6a2534e2abcf36/manifest.toml#L49-L65


      
          [resources.sources.back]
          arm64.url = "https://dl.vikunja.io/api/0.22.1/vikunja-v0.22.1-linux-arm64-full.zip"
          arm64.sha256 = "50a1670c0fde858c1cd7bc72cc670c4011a688a20b07ee62fab11bcca3eab01e"
          amd64.url = "https://dl.vikunja.io/api/0.22.1/vikunja-v0.22.1-linux-amd64-full.zip"
          amd64.sha256 = "c3e21ca5ccace3f9eaa423bab8c1cfc3e7de15d5c593db0aa6e4dbd9883469e6"
          armhf.url = "https://dl.vikunja.io/api/0.22.1/vikunja-v0.22.1-linux-arm-7-full.zip"
          armhf.sha256 = "72f50404df57d75060bdd0d162e12cba20269a0def7b38993e1b61c4cf3d69d2"
          i386.url = "https://dl.vikunja.io/api/0.22.1/vikunja-v0.22.1-linux-386-full.zip"
          i386.sha256 = "de1e271b6d3fe6024b790b95c1bf946a415598b31192638ef85589cd2c35f996"
          in_subdir = false
          format = "zip"
          
          [resources.sources.front]
          url = "https://dl.vikunja.io/frontend/vikunja-frontend-0.24.1.zip"
          sha256 = "2278ba1d7f50bf656a771378a7a47434730496fe1867d4d4964020a2e7a713ff"
          in_subdir = false
          format = "zip"

pqc · August 1, 2024, 9:12pm

I just updated Vikunja to the latest version and it was fixed!

system · August 16, 2024, 9:13pm

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.