Vicu 2.0.1 - Fixes for API token sign-ins

Vicu 2.0.1

Vicu 2.0.1 ships together with Vicu Android 2.0.1. It fixes how sharing, assignees and comments behave when you are signed in with an API token.

This is a pre-release that builds on 2.0.0; if you are coming from 1.10, read the 2.0.0 notes too. If you find a rough edge, please open an issue. The phone side is in the Vicu Android 2.0.1 notes.

Signed in with an API token

Vikunja lets you choose what an API token may do, and it answers a request the token is not allowed to make as if the session had ended. Vicu took that at its word.

• Assigning someone, writing or editing a comment, or sharing a project with a token that lacks that permission no longer says "Your session has expired". Vicu now says what the token is missing: give the token the permissions for task comments, task assignees and project sharing in Vikunja, or sign in with your password instead.
• A comment or assignment made offline that the token is not allowed to send moves to the failed list in the sync panel, with that explanation, and the rest of your offline changes are still sent. Before, it stopped the whole queue and asked you to sign in again.
• Notify me in the comments is only shown when you sign in with your password or single sign-on. Vikunja does not let API tokens follow tasks at all.

If you sign in with your password or single sign-on, nothing changes for you.

Changelog

• 736d6b0 Say what an API token lacks instead of reporting an expired session
• (this release) Version 2.0.1 and its release notes

Full changelog: v2.0.0...v2.0.1