[BUG] All notifications are 0s ago

[nicklutt]

Describe the bug There is a discrepancy in the timestamp display for notifications in the app. Every notification, regardless of when it was actually received, is displayed as "0 seconds ago". This issue is not observed on the Gotify server, where the correct time is shown.

Expected behavior The app should correctly display the time elapsed since each notification was received, consistent with the time displayed on the Gotify server. Each notification's timestamp should accurately reflect how long ago it was received, rather than showing "0 seconds ago."

Screenshots If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

• Device: [iPhone14]
• OS: [iOS17.4.1]
• Version of Container [latest]
• Version of iGotify [latest

[androidseb25]

What timezone or better what time format do you have?

The reason why he write 0s is that he can't parse the date for some reasons 🤨

[nicklutt]

TZ: Europe/amsterdam in the containers and on my phone 24H Amsterdam zone

[androidseb25]

Hi, i've testet now on my second iphone with all the settings and created a Gotify and iGotify instance with TZ Amsterdam

and i can't reproduce the problem :/ everything is working as expected. Take a look at the sdcreenshots

[nicklutt]

I redeployed the containers and reconnected iGotify, and I see a normal time in the app ✌️

Strange, But I didn't change anything in config or compose. But it's fixed, so you can close the bug ✅

[androidseb25]

ok really strange 😅

[nicklutt]

But thank you. I bought you a coffee ☕️

[androidseb25]

ok thx, not for that 🙏🏼

[ihor-sokoliuk]

Hello @androidseb25 !

I am facing the same issue with the 0s ago for each message.

Both gotify and igotify have the same time zone America/Chicago.

Restarts, redeployment, and reconnection of docker containers, and the iOS app won't work.

Also I noticed an error igotify container logs about connection to the gotify server failed, retrying in 10 seconds. And yet, I can see a new notification in the app. Maybe these are two related issues, or maybe they are not :)

I hope you can help me with that!

Thanks!

[androidseb25]

Hi, no both thinks don't related to each other, the 10s issue is only for information purpose, because sometimes the websocket connection can be lost and he is trying to reconnect. You can read about here #50 and the release for that is 1.2.0.3.

The seconds issue is a bit difficult to fix, because the timestamps that i parse are all correct. the only thing that can be the problem is the timelineview from swiftui, until now i can't reproduce this issue :/

[nicklutt]

Hello @androidseb25 !

I am facing the same issue with the 0s ago for each message.

Both gotify and igotify have the same time zone America/Chicago.

Restarts, redeployment, and reconnection of docker containers, and the iOS app won't work.

Also I noticed an error igotify container logs about connection to the gotify server failed, retrying in 10 seconds. And yet, I can see a new notification in the app.

Maybe these are two related issues, or maybe they are not :)

I hope you can help me with that!

Thanks!

My fix: after I removed the containers (gotify and iGotify). And redeployed the docker-compose it was fixed.