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

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

Summary

Mobile devices receive ”ghost” notifications for already read messages, when set to receive notifications ”when Away or offline”, and receiving user is set to be Away.

Steps to reproduce

1. Set ”Mobile Push Notifications” to ”Trigger push notifications when”: ”Away or offline” (and send ”For all activity”)
2. Using web interface on desktop, set your status to Away
3. (Still in the web interface) receive a message in the currently open channel (which immediately marks it read)

Expected behavior

Nothing happens on the mobile device (no notification).

Observed behavior (that appears unintentional)

The mobile device receives a notification about the already read message. The notification immediately disappears. If you weren’t looking at the device, you’re left wondering why it alerted you.

Other info

If your status is set to Online instead of Away (at step 2), the mobile device receives no notification (as expected). If ”Trigger push notifications when” is set to ”Online, away or offline” (at step 1), the mobile device receives no notification irrespective of your Online/Away status (also as expected).

Environment Information

I’m self-hosting Mattermost 5.26.1 with self-hosted MMPNS 5.22.4. Mattermost Mobile is at version 1.34.0. My mobile devices have Android 10 (Samsung) and Android 7.1.2 (LineageOS 14.1).

I don’t know if this is an issue with the client or the server; I can re-report against the latter if appropriate.

I have the same issue on my Samsung Galaxy A9 phone, with ”android.process.media has stopped” appearing for virtually every photo taken (though the uploads seem to still go through). My Samsung Galaxy Tab S5e does not have the same issue, nor do I recall seeing this on any other Android devices (from other manufacturers).

I don’t use alarmapp (to my knowledge, though I’m not sure which app that is).

Hi! I’ve been a happy Freecell player for years now, thanks for the nice app.

I recently got a new Samsung S5e tablet, which supports Android’s new split-screen mode, which is obviously very handy for multitasking. But unfortunately Freecell seems to be one of the few applications that do not support this mode: trying to do so just brings up Freecell (alone) with a ”Can’t use this app in Multi window view” message. (I’m attaching a screenshot.)

So I thought I’d send in this wishlist ticket for getting multi-window support in Freecell. I’d particularly like to be able to play videos on the one side while playing Freecell on the other.

A hint for anyone googling for this: make sure that the value of gcmSenderId in your AndroidManifest.xmlstill has the trailing backslash (\) after you’ve changed the project number to your own. Otherwise the value gets interpreted as int, when it should be a string, which is one way to trigger the issue of devices being assigned empty/null IDs.

(The building instructions do have this documented in bold, but it’s still very easy to miss, I know I did. Complicating the debugging was my Nexus 5X, which kept getting a proper device ID even when all other devices using the same broken build failed to.)

Reproducible here on a Galaxy Tab 4 (SM-T530), Android 5.0.2.

I just migrated from Owncloud 8.2 to Nextcloud 9.0.52. Everything else (i.e. the web interface, desktop client) seems to work just fine, but I can’t get the Nextcloud Android app to connect with the server. I can enter the URL (no errors), my login and password, but the ”Connect” button feels totally unresponsive, it does nothing at all no matter how much I tap it. No error messages are given by the app nor is there anything correlating with the attempts in server logs.

This happens on both my phone (Nexus 5X, Android M) and tablet (Samsung Tab 4, Android L). I also tried the Beta app from F-Droid and the issue is present there too. It’s also present in both my WLAN and when using a direct 3G connection on the phone (so I don’t think the WLAN router’s firewall is the cause either).

The Owncloud app on the same devices still works with the server, although I haven’t tried logging out and re-connecting it.

The server is on shared hosting where I have shell access.

Any suggestions?

What blew my mind was that my now three years old phone is capable of doing the same. State of The Art was literally the first thing I loaded after installing an emulator. Epic times were relived.

Tämän (ja tähän perustuvan uutisen) mukaan Android-sovellus edellyttää 2.3:n tai uudemman, Playssa esittelyn mukaan sovellus toimii ”laitteilla, joissa Android 2.2 tai uudempi”, eli jompi kumpi väittämä kaivannee päivitystä.

Onko kanavalähetysten tuki tulossa myöhemmin myös 3.0:aa vanhempiin Anteroihin?