Since recently, editing the description takes two clicks instead of just one. The first click turns the content into a textbox, but it remains unfocused until I click it again.

Issue

Server Setup Information:

• Did you test in newest Wekan?: yes
• For new Wekan install, did you configure root-url correctly so Wekan cards open correctly? yes
• Wekan version: 4.49
• Meteor version: 2.0-beta.4
• Node version: 12.19.0
• MongoDB version: 3.2.22
• Operating System: Ubuntu 20.04
• Deployment Method: snap
• Http frontend if any: Apache
• What webbrowser version are you using? Both Firefox 82.0.2 and Chrome 86.0.4240.183 equally affected.
• If using Snap, what does show command sudo snap logs wekan.wekan? nothing

Problem description:
Sorry for not providing animation, as peek doesn’t support Wayland. The steps below should be sufficient though.

Steps to reproduce:

1. Open a card
2. Click on the description once

What I expect to happen:
For the description to have focus (i.e. cursor, to be able to type)

What happens instead:
The description textbox remains unfocused and I can not type into it

Console log contents

site.webmanifest:1 GET https://my-domain.com/site.webmanifest 404 (Not Found)
site.webmanifest:1 Manifest: Line: 1, column: 1, Syntax error.
A bad HTTP response code (404) was received when fetching the script.
mZLgcqMWYXM4o7dmL:1 Uncaught (in promise) TypeError: Failed to register a ServiceWorker for scope ('https://my-domain.com/') with script ('https://my-domain.com/pwa-service-worker.js'): A bad HTTP response code (404) was received when fetching the script.

It seems to refer to to paths in the domain root, whereas my root-url has the path https://my-domain.com/kan. Not sure if that’s related to the issue or not.

With more verbose logging server-side, there’s a ”Deprecated event type” followed by "Exception":"Sabre\\DAV\\Exception\\NotFound" for the file being uploaded. So it’s perhaps correctly reporting that the file (about to be uploaded) does not exist (yet), but for some reason the app receiving this message flips it around, thinking the file does exist, and thus reports a conflict.

Here’s a logcat snippet from another device. The result of ”Existence check” comes back as ”Name collision”, for any and all files.

This is still an issue, and always has been for Samsung devices with One UI’s scrolling screenshot feature.

In short

Since updating the Android app to 3.14.0 RC1 (and server to 20.0.1 earlier), I can not upload anything with the app. Desktop client still syncs just fine.

Steps to reproduce

Try to upload a file (either manually or by taking a photo for auto-upload)

Expected behaviour

File should get uploaded

Actual behaviour

There’s a notification about ”File upload conflict”. Selecting the notification results in ”Error creating conflict dialog”. Going to uploads view and selecting ”Resolve conflict” for a file just results in ”Sync conflict, please resolve manually”.

Can you reproduce this problem on https://try.nextcloud.com?

Trying to add an account in the app causes the app to crash.

Environment data

Android version: 10
Device model: Samsung Galaxy A9 (2018)
Stock or customized system: stock
Nextcloud app version: 3.14.0 RC1 (from Beta channel)
Nextcloud server version: 20.0.1
Reverse proxy: no

Logs

Web server error log

Nothing NC-related

Nextcloud log (data/nextcloud.log)

Nothing related to the uploads, just

• fread(): read of 8192 bytes failed with errno=21 Is a directory
• Undefined offset: 3