Unable to fetch articles on new Android device

[AnemonePrune]

Issue details

When I log in the Android app on a new device, it throws an error 500 when it try to fetch articles.
Other devices works fine. I checked wallabag_dir/var/logs/prod.log and these lines are added when i try to sync articles:

-> request.INFO: Matched route "api_get_entries". {"route":"api_get_entries","route_parameters":{"_controller":"Wallabag\\ApiBundle\\Controller\\EntryRestController::getEntriesAction","_format":"json","_route":"api_get_entries"},"request_uri":"https://mywallabagdomain.tld/api/entries.json?order=asc&page=1&perPage=30&since=0&sort=created","method":"GET"} [] -> request.CRITICAL: Uncaught PHP Exception Doctrine\DBAL\Types\ConversionException: "Could not convert database value "a:1:{i:0;s:27:" ? V..." to Doctrine Type array" at /var/www/wallabag/vendor/doctrine/dbal/lib/Doctrine/DBAL/Types/ConversionException.php line 46 {"exception":"[object] (Doctrine\\DBAL\\Types\\ConversionException(code: 0): Could not convert database value \"a:1:{i:0;s:27:\" ? V...\" to Doctrine Type array at /var/www/wallabag/vendor/doctrine/dbal/lib/Doctrine/DBAL/Types/ConversionException.php:46)"} []

Environment

• wallabag version : 2.3.8
• How did you install wallabag? git clone
• Last wallabag version that did not exhibit the issue (if applicable): 2.3.7
• php version: 7.2.24
• OS: Ubuntu Server 18.04 LTS
• type of hosting (shared or dedicated): dedicated
• which storage system you choose at install: MySQL

Steps to reproduce/test case

1. Log in Android app for the first time
2. Launch sync operations

[j0k3r]

What version of MySQL are you using?
We already got someone with that issue wallabag/wallabag#3873 but didn't find how to fix it yet.

[AnemonePrune]

I have MySQL version 5.7.28.

[AnemonePrune]

I upgraded Wallabag to 2.4.0 and the issue still persists.
Nothing shows in wallabag_dir/var/logs/prod.log but I have this in the apache log:
[Mon Dec 14 22:17:43.435346 2020] [proxy:error] [pid 531502] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:12345 (localhost) failed [Mon Dec 14 22:17:43.435409 2020] [proxy_http:error] [pid 531502] [client 192.168.1.47:59502] AH01114: HTTP: failed to make connection to backend: localhost
I upgraded my server to Ubuntu 20.04 LTS, PHP to 7.4.3 and MySQL 8.0.22
I enabled the apache modules proxy and proxy_http.

[virtadpt]

I'm seeing almost the same thing over here:

[2023-01-19 18:08:28] request.INFO: Matched route "api_get_entries". {"route":"a
pi_get_entries","route_parameters":{"_controller":"Wallabag\\ApiBundle\\Controll
er\\EntryRestController::getEntriesAction","_format":"json","_route":"api_get_en
tries"},"request_uri":"https://archive.drwho.virtadpt.net/api/entries.json?detai
l=full&order=asc&page=150&perPage=30&since=0&sort=updated","method":"GET"} []

[2023-01-19 18:08:29] request.CRITICAL: Uncaught PHP Exception Doctrine\DBAL\Typ
es\ConversionException: "Could not convert database value to 'array' as an error
 was triggered by the unserialization: 'unserialize(): Error at offset 11 of 35 
bytes'" at /home/drwho/wallabag/vendor/doctrine/dbal/lib/Doctrine/DBAL/Types/Con
versionException.php line 117 {"exception":"[object] (Doctrine\\DBAL\\Types\\Con
versionException(code: 0): Could not convert database value to 'array' as an err
or was triggered by the unserialization: 'unserialize(): Error at offset 11 of 3
5 bytes' at /home/drwho/wallabag/vendor/doctrine/dbal/lib/Doctrine/DBAL/Types/Co
nversionException.php:117)"} []

Wallabag v2.5.2 (commit 63b7b1c18fbeccfa31f5c9617b1fdccd95d26864). Ubuntu Server v20.04 LTS. php v8.1 (from package). MySQL v8.0.31-0ubuntu0.20.04.2. Wallabagger for Android v2.4.3 (229).

[Strubbl]

@di72nn is this an issue with your api-wrapper?

[di72nn]

It's not an app issue. It's just one of the fields containing old incorrect data (probably the author field). Check this comment: #818 (comment).

[Strubbl]

The link does not work. Strange, the issue #818 does not exist. What happened here?

[di72nn]

Weird. Here's another related issue: #1049. Also this: wallabag/wallabag#4412

[Strubbl]

Now, the 818 link does work again. So this seemed to be a Github issue, that it was 404 yesterday.