When trying to "bag" the following article I get a server sync error. The only way to resolve the syncing error is to remove the local database.
http://raspberryjamberlin.de/zero360-part-1-building-the-zero360/
Wallabag Version: 2.0.2 (106)
Android: 7
Phone: SM-G930F (Galaxy S7)
What version of wallabag is running on your server?
How do you "bag" that article? Directly in the app or via sharing from a browser? which browser in the latter case?
When adding this article via wallabag web i cannot reproduce the issue. I am going to try it via app soon
I just tried adding the article via sharing from Firefox Focus and it worked without errors. At least i cannot find an error in the logcat
Ok, I haven't used Android SDK for a while, let me have a shot this evening in trying to retrieve the log files from my phone.
I'm using the latest Wallabag release version 2.2.3 on docker hub.
@Strubbl , could you point me in the right direction. I'm trying to filter the log files from the application but I don't get any useful output like GreenDAO
logcat | grep "InThePoche"
Do you have the debug version of the app installed? I guess otherwise it does not output any messages.
Maybe you also get an error in the wallabag server log? It is located in the wallabag folder under var/logs/prod.log
@Strubbl i am getting the same error when i try to bag the article, I have now posted a more detailed issue in the docker repo of wallabag, maybe have a look please :)
@pixelyo yes, you might be right. The article from @glego also has an emoji in its content (the winking face 馃槈)
the problem with android app with this issue is, that once you try to add a link with an emoji, the article is staying in the queue of articles to be synced/added and I don't know how to remove it from this queue. So this makes me reinstall the wallabag app and that, every time I add such an article.
There should be a way to remove article from the sync queue in the android app, or the sync failing articles should be simply removed automatically.
Yes, you are right. I adjusted the issue's title
@Strubbl thanks, you helped me a lot, you are amazing
@pixelyo I've mentioned in the original issue that you can resolve it by removing the local database. This is an option under the wallabag settings -> miscellaneous -> Wipe Database.
Sorry that I haven't been able to look at the issue more in depth as I was traveling with the kids, but it looks like the root cause has been found.
Thanks allot Guys!
Closed.
Issue was caused by incorrect character set and collation in MySQL.
See