Haven't I fixed this already? xD

It shows the push subject, but not the content.
Would it also be possible to show the complete content (as many text as fits into the notification?)

Working.

Is this released? I get this since the last update.

Yes, since ages.
If you get this, it means that for some reason the content cannot be decrypted.
Can you check if there are wrong app tokens in web->settings?

After debugging with @skjnldsv it turns out that those strange notifications only happens when the app is not in foreground.

I'm having this problem, too. Running client version 3.14.0 against server 19.0.5. I think it started after the upgrade from 19.0.4.

I'm having this problem, too. Running client version 3.14.0 against server 19.0.5. I think it started after the upgrade from 19.0.4.

Same here.

As far as I remember new_notification is the default value of push proxy, if no message is set.
@nickvergessen do you have an idea why such messages might be sent?

I had one of these shown as having occurred 4 hours ago. When I log into NextCloud with a web browser, I see a perfectly normal notification from PhoneTrack (with correct notification text) also shown as having occurred about 4 hours ago. I have no other notifications from around that time or since in either environment. This suggests that the notification within the Nextcloud server is handled normally, but is getting lost when picked up or presented by the Android client.

Have you removed account in question on Android or reset app token or something like that?

The problem still occurs. The NC web interface shows a proper notification (again all PhoneTrack in my case telling me I've reached my point quota, but I think that's just because I don't get many other notifications), but "NEW_NOTIFICATION NEW_NOTIFICATION" in the Android notification bar.

do you have an idea why such messages might be sent?

Just to answer this publicly here as well. The subject is the default subject we set. The encrypted subject should be decrypted and displayed instead by the client. However in this case it seems it either fails to decrypt or to load more information from the server.

However in this case it seems it either fails to decrypt or to load more information from the server.

At least on Android side we only show a notification if we can decrypt it and if we can get real info from server:

I have no real idea how this could happen…

Ok. I have had this same problem some time ago with talk notifications, and for testing I have done the same procedure with the Nextcloud app. It has worked. Notifications reappear successfully. The problem lies in the Nextcloud database, specifically in the table _notifications_pushhash which it is structured as follows:
Id
uid
Token
deviceidentifier
devicepublickey
devicepublickeyhash
Pushtokenhash
ProxyServer
apptype
The fact is that what we need for the notifications to work again we must delete the entries that have the account to which the notifications do not work, for this we connect via console to the mysql server.
mysql -u root
We select the nextcloud database.
Use NextCloud;
Let's first see if there are entries for a certain user.
Replace mike with your user.
SELECT * FROM oc_notifications_pushhash WHERE uid='mike';
In case you return a record we will delete it.
DELETE FROM oc_notifications_pushhash WHERE uid='mike';
Delete accounts from the android app and log back in. For me this has worked.

Try now notifications with sudo -u www-data php occ notification:test-push

Cheers.

Ok. I have had this same problem some time ago with talk notifications, and for testing I have done the same procedure with the Nextcloud app. It has worked. Notifications reappear successfully. The problem lies in the Nextcloud database, specifically in the table _notifications_pushhash which it is structured as follows: Id uid Token deviceidentifier devicepublickey devicepublickeyhash Pushtokenhash ProxyServer apptype The fact is that what we need for the notifications to work again we must delete the entries that have the account to which the notifications do not work, for this we connect via console to the mysql server. mysql -u root We select the nextcloud database. Use NextCloud; Let's first see if there are entries for a certain user. Replace mike with your user. SELECT * FROM oc_notifications_pushhash WHERE uid='mike'; In case you return a record we will delete it. DELETE FROM oc_notifications_pushhash WHERE uid='mike'; Delete accounts from the android app and log back in. For me this has worked.

Try now notifications with sudo -u www-data php occ notification:test-push

Cheers.

This worked for me as well, thank you very much!

Unfortunately, this is not a nice solution and does not prevent the problem. Please, dear Nextcloud team, take care of this bug.

Delete accounts from the android app and log back in. For me this has worked.

This is where things become complicated, because of #11090

If reregistering the app is a workaround to fix this issue, would it be a somewhat solution to allow reregistering for notifications without logging out and maybe then also do that automatically when the app receives a broken message?

This may make the experience good enough for end users while the server may log all of this circumstances so it is possible for admins / devs to debug this issue.

And I know, that temporary solution might stay forever, but in perspective of how long this bug exists so far, this may be good enough in practice ;)

I don't know if the following is known to the Nextcloud team, therefore a small description:

Steps to reproduce;

1. get a message or create one using administrator tools
2. see on your Android app that the generic "new notification" appears as notification
3. delete the notifications in the browser
4. see how for each deleted message your phone gets spammed with more generic "new notification" notifications

No matter if the message is already deleted in the app or not each time it will generate enormous amount of spam. I don't know how this is handled now with the messages (Firebase, or own infrastructure) But the way I see it is an unnecessary load on the system.

None of the workarounds or fixes provided here helped so far.

However I received one (!!!) notification properly last week - I don't know what happened as I didn't change anything on my Nextcloud installation but suddenly one notification was displayed properly on my mobile. After that everything is back now to the "new notification" thing. 😢

@jtorqui74

Ok. I have had this same problem some time ago with talk notifications, and for testing I have done the same procedure with the Nextcloud app. It has worked. Notifications reappear successfully. The problem lies in the Nextcloud database, specifically in the table _notifications_pushhash

Tricky fix, but worked for me, this has been bothering me for quite a while now.
Thanks much for finding out !! 😍

Seeing this problem too.

DELETE FROM oc_notifications_pushhash WHERE uid='nursoda';
Delete accounts from the android app and log back in.

Thanks! Since it helped some guys here, I tried that. Without success:

I deleted the rows in the DB and the corresponding account in the app (I use several accounts in the app). I then force-closed the app, re-started it and re-created the just deleted account. Result: Account is available again and does receive test notifications in-app. Yet, no Android notifications. The app does not re-register with the cloud:

nc-user@server /path/cloud $ occ notification:test-push nursoda
No devices found for user

This correlates with not an entry in the DB:

MariaDB [cloud]> SELECT * FROM oc_notifications_pushhash WHERE uid='nursoda';`
Empty set (0,000 sec)

Server: 27.0.1, App 3.25.0, Phone: Pixel 6a running GrapheneOS with their sandboxed Play Service. All other apps work fine including push, e.g. Signal, Threema, Bank apps.

What now? Do I need to wipe all data from the NC app? Might this be a Graphene Play Services bug? How to debug and find out which app or service to blame? What about missing library / invalid notification channels mentioned above? Where are those logs referenced there?

@nursoda It seems that NextCloud app does not request another token unless it is removed and installed again. At least for me it was the only way to get a new token using MicroG after removing the older (broken) token from the server database. It's a pain, but since then notifications have been working fine.

Thanks for that hint. I deleted all data from the app (instead of deleting and re-installing it), and it worked. Quite painful if you use multiple NC instances like me.

Tried again on fresh installation - still not working:

Trying to push to 1 devices

Language is set to en_GB
Private user key size: 1704
Public user key size: 451
Identified 0 Talk devices and 1 others.

Device token:67636
Device token is valid
Device public key size: 451
Data to encrypt is: {"nid":3437,"app":"admin_notifications","subject":"Testing push notifications","type":"admin_notifications","id":"64fd8129"}
Signed encrypted push subject
Deleting device because it is unknown by the push server: 12JrPiB9KvMQbE83xs2Q3dWURmblKztjKdP3o/DEcOyROzp8iIhFqFkj6B5g9QaFW+3+2SnBzIjlIdavTbegA==
Push notification sent, but 1 failed

If the Nextcloud app is open in the foreground and a notification arrives during that time, the notifications will be displayed correctly.

I can confirm that the notification is shown properly when the app is in foreground. When it is in background I only get the generic text "NEW NOTIFICATION"

Is anybody currently investigating this and getting anywhere? If not, I might give this a poke this weekend and see where I get with it.

I subscribe here since I never got a readable notification on my phone and I won't re-install it as I don't want to lose my settings

Would be nice to have an entry in the app settings like "Fix notifications" or something like that, that will trigger new registration with the server. There are other apps that can do it. My setup is quite complex on my phone, and wiping it all just doesn't make sense.

I've been dealing with this for quite some time. Is there any plan to pick this up?

I switched to this notifications app for Nextcloud and it works really well.

https://gitlab.com/Nextcloud-Push

It's a bit old and it does have some scalability shortcomings (they can be worked around but it needs some understanding of the webserver/php config)
I works perfectly for all notifications from the server (2FA, Talk, Calendar, etc.)... And the best part is that it does not depend on google services, so it works even on ungoogled devices.

So the workaround is a great thing, but it's not a permanent solution, especially for users without technical knowledge.

I wouldn't call Nextcloud-push a "workaround", it is a rather specific solution for notifications which has very good use cases but I agree that it is not the solution to this problem.

I know it is not a workaround, but it does solve most evident symptoms in this thread (show correct notifications on a phone).

I don't pretend to minimize the problematic behind reliable push notifications nor the complexities and priorities of the project but... I just don't understand why issues related to notifications take so much time to be addressed when there are alternatives that work and just need a little polish.

This ticket was opened more than 5 years ago, fixed and refixed and it keeps coming back. By the looks of the fixes it seems it's just a matter of following google's firebase dependency. There are other tickets asking for an official alternative to google handled notifications.