Since Wallabag 2.0.2 I see errors when deleting articles using the app:

This error does not seem to affect the actual deletion of the article.
Android 6.0.1 / Wallabag _master_ (formerly 2.3 branch)
// for search: Error: com.squareeup.moshi.JsonDataException: Expected an int but was NULL at path $.id
Yes, same error here with the same app and server version
After a quick test, it seems that the uid and id fields from original entry are lost just after the Doctrine flush:
https://github.com/wallabag/wallabag/blob/master/src/Wallabag/ApiBundle/Controller/EntryRestController.php#L562-L564
Sadly, the issue is still present with my fix released in wallabag 2.3.1
I have the same issue following the upgrade to the last release version of wallabag (2.3.2). My wallabag is self-hosted on Debian/nginx with HTTP/2 support. I will try to see what's going on in the logs asap.
Edit: no error that I can see in nginx's debug logs.
Any news on this issue? It is quite annoying to see the error each time an article is deleted from the app.
Please tell me if there is something I could provide to help solve this problem. Thanks
Do you see any error in the var/logs/prod.log of the wallabag server?
When I try to delete on my phone an article with the app, I have the error mentioned above in a notification, and the following message in var/logs/prod.log on the server:
[2018-03-19 08:03:37] request.INFO: Matched route "api_delete_entries". {"route":"api_delete_entries","route_parameters":{"_controller":"Wallabag\ApiBundle\Controller\EntryRestController::deleteEntriesAction","_format":"json","entry":"964","_route":"api_delete_entries"},"request_uri":"https://wallabag.anbuco.fr/api/entries/964.json","method":"DELETE"} []
[2018-03-19 08:03:37] request.ERROR: Uncaught PHP Exception Symfony\Component\HttpKernel\Exception\NotFoundHttpException: "Wallabag\CoreBundle\Entity\Entry object not found." at /var/www/wallabagv2/vendor/sensio/framework-extra-bundle/Request/ParamConverter/DoctrineParamConverter.php line 66 {"exception":"[object] (Symfony\Component\HttpKernel\Exception\NotFoundHttpException(code: 0): Wallabag\CoreBundle\Entity\Entry object not found. at /var/www/wallabagv2/vendor/sensio/framework-extra-bundle/Request/ParamConverter/DoctrineParamConverter.php:66)"} []
Despite the error, the article seems deleted on both the web interface and in the app.
"Uncaught PHP Exception" looks like an entirely server error. Do you have any idea how we can fix this in the app itself without working around it? Maybe somehow handle the error in a better way or sth. like this...
Meanwhile i am opening an issue in the core repository so that it is going to be fixed in the API soonâ„¢
Isn't that "NotFound" error happens only when app tries to retry the removal (after the first one failed on the client side because of the null id)?
No, i added an URL via web app. Then synced my Android app and deleted that article via app. Got the same error
Since I updated my phone, I cannot reproduce the bug anymore... No modifications were made on the server. Strange!
Still no luck and have this problem too. It does not affect me much, though
@linusboyle Have you tried deleting the cache of the app (via the application informations on Android) then doing a full synchronization of the articles?
@linusboyle Have you tried deleting the cache of the app (via the application informations on Android) then doing a full synchronization of the articles?
Yes, and it does not help.
I use Android 7. Maybe as mentioned above, a system update is required
Same problem here. Wallabag app have been downloaded from F-Droid, it is version 2.0.2 (106) of Wallabag app.
@oupala
Is this problem still existing with Version 2.1.0 (109)? It is available with fdroid.
@Kdecherf Can you confirm this issue is fixed? Have you tried it?
@Strubbl yep, the PR has been applied on my instance, the issue does not show up since then.
@Strubbl I'm now using version 2.1.0 (109) from F-Droid and I still have the same error on android when deleting an article.
This issue should be fixed with the next wallabag server release. See
So if that wallabag server version gets released, this issue should not occur in the app anymore - even without an app update.
Ok, I understand the problem was on the server side. Thanks for the information.