[Notifications] logs failed to push notification

[samuraikid0]

Ok seems to be working correctly, it seems it was something on my end
but logs still show the following

f-droid version
latest 0.1.18
android 15

I've notice that on databag logs at start of an notification it says

2025/12/30  /internal/api_setPushEvent.go:90 failed to push notification

2025/12/30  /internal/api_setPushEvent.go:90 failed to push notification

and nextcloud give an id that exists (94_XR) followed by a 404 that doesn't exist (RHjcZW)

 [30/Dec/2025: ] "POST /index.php/apps/uppush/push/94_XRbw6XrZLSmb74lQgPzCqEsc HTTP/1.1" 201 1525 "-" "Go-http-client/2.0"

 [30/Dec/2025:] "POST /index.php/apps/uppush/push/RHjcZW1Tdd784vnfjwdYwog2n1g HTTP/1.1" 404 1471 "-" "Go-http-client/2.0"

related to the pr comment no worries
Happy New Year
Cheers !

[samuraikid0]

further blocking a certain ua will make the .go:90 error disappear
and show
2026/01/03 /internal/api_setPushEvent.go:141 Post "https://repeater.coredb.org/notify": dial tcp 52.89.116.243:443: i/o timeout

Can you explain ?
https://repeater.coredb.org/notify

everything works with or without this address being blocked

[balzack]

The first message seems to be for unified push, the endpoint being invoked appears to be one defined by unified push.

The endpoint is registered at login time when it detects you support unified push, and gets invoked for a push notification.

The second message is for when unified push is not used, and is trying to use firebase notifications. It will use this path if unified push was not detected.

'repeater.coredb.org' is a server I now have to host in order to support firebase. The server may be trying to invoke that endpoint if there is a client where unified push was not detected

[samuraikid0]

Ok thanks for the explanation never saw that repeater. pop-pop on the logs just when it got blocked

So the op log is just 'cosmetic'
/internal/api_setPushEvent.go:90 failed to push notification

Back then I remember you tweak something to better clean non used unified push ids maybe that's the case for

[30/Dec/2025:] "POST /index.php/apps/uppush/push/RHjcZW1Tdd784vnfjwdYwog2n1g HTTP/1.1" 404 1471 "-" "Go-http-client/2.0"