Starred messages count is different between web app and android app

[gjanssens]

trafficstars

Current Nextcloud server version: 24.0.3 Current Android Nextcloud News version: 0.9.9.75

It has been the case for quite some time that the counters for starred message differ in the web app and in the nextcloud news android app.

With the most recent update of the server I had to re-login in the android app and now the starred messages counter on the android app is 0. On the server however it's 910.

If I unstar a message via the webinterface and restar it again, that message will reappear in the android app as well (and the count properly increments by one). It would however be very cumbersome to unstar and restar 910 messages one by one. Is there a better way to handle this ?

[David-Development]

@gjanssens Which version of the nextcloud news app (web) are you using?

Which hardware are you running your nextcloud server on? Is it a 32bit system? -> https://github.com/nextcloud/news/issues/1320

I can't really think of any other reason that would explain such synchronization issues. Are you using the "Login using Nextcloud Files App" or the "Manual login" inside the android app?

There is a report of sync issues in the other direction (marking them as read in the web interface) https://github.com/nextcloud/news-android/issues/1105 but I believe your issue is different from that.

[gjanssens]

@David-Development I'm currently using version 18.1.0 of the nextcloud web app. The problem has been going on for quite a while though, at least back to whatever version was in NextCloud 20, maybe longer. I never bothered with reporting as I thought it to be an obvious bug many users would run into :(

Anyway, the nextcloud server runs on a 64bit system.

I didn't remember which login method I was using. So I tried both to see if there's a difference. Interestingly enough it now properly reports starred messages :confused: Additionally it does now recount them via both login methods while logging in and it will update when I make changes via the web app.

So there's no more bug to solve here...