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
- Set ”Mobile Push Notifications” to ”Trigger push notifications when”: ”Away or offline” (and send ”For all activity”)
- Using web interface on desktop, set your status to Away
- (Still in the web interface) receive a message in the currently open channel (which immediately marks it read)
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.
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).
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).
All of my devices are affected by this, or something very similar. My server is running Ubuntu 16.06 with Nextcloud 14.0.1 (in a subdirectory). Here’s logs from my
I trimmed them down to (what appears to me as) the essential, filtered out some noise and replaced my username and the server hostname.
Steps to reproduce:
- (On desktop) Create a new subdirectory under the sync directory, add two JPEG files into it. Wait for changes to sync.
- (On mobile) Open Nextcloud, select the newly created directory, switch to grid view.
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.
Having just installed one this weekend, I can confirm that at least ML-2165 (the non-wifi, USB-connected one) works under 12.04.3, with suld-driver-4.01.17 installed from the SULD repository.
Olisin kommentoinut het tuonne, mutta olitkin, ruoja, sulkenut kommentoinnin sieltä. Mutta siis omistan tuollaisen Samsung E1080:n, mikäli siihen viittasit parin kympin puhelimella, ja se on kyllä aivan perusvarma peli, juuri sellainen että ”vain puhelimen” haluavan kuvittelisin olevan tyytyväinen. Tekstiviestitoiminto siinä tosin on ja vähän jotain muutakin enemmän kuin puhelin. Minulla se toimittaa tällä erää herätyskellon virkaa, kun toista SIM-korttia ei enää ole.
Maksoin siitä kympin. DNA-kaupan sisäänheittotarjous. Liittymän torppasin kätevästi maksuhäiriöllä.