I built the apk from master (to test #811) and when I perform a complete update in the app. I see this error.

@tcitworld I think this is important, I can't use the app because I can't update. I'm going to a previous version by now. I will test again if you release some fix.
That's a long shot, but can you run this on your server?
select id, url, published_by from wallabag_entry where published_by like '%;a:%';
// Update: I'm able to see the exactly same error if I manipulate an entry to have another array inside of authors array.
@di72nn bingo!
id = 629
url = https://www.newyorker.com/magazine/2016/02/29/a-new-generation-of-airships-is-born?mbid=rss
published_by = a:1:{i:0;a:1:{i:0;s:19:"Jeanne Marie Laskas";}}
Btw, in wallabag web I see just Array

~Could be related to https://github.com/wallabag/wallabag/issues/3867~ (_edit: I should read better :sweat_smile:_)
By the way, the Array does not show up anymore on current server master
I guess the extraction was fixed.
To make the error searchable: Error: com.squareup.moshi.JsonDataException: Expected a string but was BEGIN_ARRAY at path $._embedded.items[29].pubulished_by[0].
Thanks for the report, maybe it'll help someone else!
@di72nn is fixed in wallabag app or in wallabag web?
That just shouldn't happen. Refetch the article (on the server) and the problem should be gone. I think the extraction rule was broken in the past or something like that.
@di72nn how is that? I have my own server, if I don't update the server or something I get the same result, Array...
Edit: don't worry, it's not that important. i will fix manually
The entry in question was fetched with older server version (in the early 2017), if you refetch it with 2.3.8, the field should update with the correct value.
Most helpful comment
That's a long shot, but can you run this on your server?
// Update: I'm able to see the exactly same error if I manipulate an entry to have another array inside of authors array.