-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[API] getRead
attribute behavior change in 15.4.0
#1328
Comments
|
I may retry if you want but when I tried yesterday it didn't change a thing 😔 |
So I've just tried again, same behavior with curl \
-H "Accept: application/json" \
-H "Authorization: Basic XXXXXXXXXXXXXX" \
"https://nextcloud.domain.name/apps/news/api/v1-2/items?getRead=0" \
| json_pp \
| tail -n 6
"unread" : false,
"updatedDate" : null,
"url" : "..."
}
]
} Thanks for your feedback. 👋 |
I may not be contributing much diagnostic data, but I can confirm that since the 15.4.0 update that third party apps are just showing all entries as unread such as Fiery Feeds on iOS. That app was last updated 2mo ago and was working properly until the 15.4.0 update went live on my Nextcloud instance. Since then every time the app syncs it pulls all items as unread. I did update to the latest 15.4.2 version and the issue still exists as well. Based on what I've seen so far, it appears like an issue in the the 15.4.0 update. However if this is due to feature deprecation and the iOS app developer needs to update his app to use new methods please let me know and I'll pass the info along to the iOS dev. |
could you try applying https://patch-diff.githubusercontent.com/raw/nextcloud/news/pull/1340.patch and see if that fixes it? |
Sorry but it does not change a thing, still getting the whole items set 🙄 |
Any "news" on this @SMillerDev ? I can do more tests if you want. Bye 👋 |
I'm still thinking what could have caused this, but coming up empty. Maybe it's the boolean/no-boolean magic happening here: #1344 ? |
Nice catch, definitely seems related. I even wonder whether @tweitzel has already nailed down this issue. As the other OP, I also use PostgreSQL (I thought this detail was irrelevant here, it looks like Web development kidded me again). |
I'm reproducing it on MariaDB. Holler if you have test cases and commands to run that would capture the data you need. |
OK here we go. I turned on the mysql query log on my instance and did a bunch of tests. The web UI appears to be working correctly. The API client (fiery feeds on ios) is not. Starting with our test object:
I pull to refresh in the feed that it belongs to:
Opening the item:
What does it look like now?
Pull to refresh. The item is still there.
Now, the web UI:
Test item:
Clicking on it:
Reload feed:
Now let's mark all as read:
This worked in the web UI. Now look at the fiery feeds app:
All items are returned. |
I think this is where it goes wrong, since there is a dedicated unread type I don't take |
Fiery feeds just released an update that works around this issue. So at least the gordian knot is cut. |
Fix confirmed in v15.4.4 : curl \
-H "Accept: application/json" \
-H "Authorization: Basic XXXXXXXXXXXXXX" \
"https://nextcloud.domain.name/apps/news/api/v1-2/items?getRead=false" \
| json_pp
{
"items" : []
} Thank you, all 🙏 |
IMPORTANT
Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)
Explain the Problem
Hello over here ! Actually more of a question than a "bug".
I've noticed an API (breaking) change after the 15.4.0 update. It looks like the
getRead
parameter is not taken into account anymore.From CHANGELOG, I thought about a #1056-related change ?
So, is the legacy documentation now outdated or is it more of a regression ?
Thanks for your time 🙏
Steps to Reproduce
apps/news/api/v1-2/items?getRead=false
(legacy) API endpointSystem Information
The text was updated successfully, but these errors were encountered: