-
Notifications
You must be signed in to change notification settings - Fork 258
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
java.lang.IllegalArgumentException: Unknown server version
#1075
Comments
Thanks for the report!
That's the kind of error you should report as soon as you get it. The problem that the app (specifically my library) doesn't have proper version parsing, so it fails on the It gets stuck because some operations use version check (article deletion in your stacktrace). If the operation cannot be performed, the app stops any sync to prevent data loss. Obviously I need to fix the version check, but in the meantime there are two workarounds:
|
Ok, I went into And that fixed it! The surprising part is that this version number has been there since at least April last year. I'm surprised I haven't deleted a single article in 18 months, and then did it in close succession in all three installs of the app I have. I'll leave this issue open for the app fix, but my problem is solved. Thanks! |
The app didn't have that version-related logic for most operations until around |
Issue details
I have been receiving error notifications from the app for the last couple of week, with the following stacktrace.
This seems to block any sync, up or down.
Oddly enough, I have been receiving it at different times on various devices, but once this happens once, it doesn't go away. Weirder too, is that I did not change anything on either the server or the app(s) (one of the apps in my own debug build, so I know it has not been updated, and was working before).
I can also get the versions manually just fine from the JSON API, though it is not a JSON object, but a simple string.
There are 6609 articles in this instance (using MySQL).
Or... Looking at the Wallabag logs just now, a DB error due to a duplicate tag? But those logs are from a month ago.
The only think I can think of is an increase in the number of articles in Wallabag.
Duplicate?
Have you searched the issues of this repository if your issue is already known? yes
Actual behaviour
Expected behaviour
Steps to reproduce the issue
Environment details
Logs
App
Logcat
wallabag server
prod.log (last entry from a month before this test)
Web server
Just a single hit, then nothing.
Your experience with wallabag Android app
Have you had any luck using wallabag Android app before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
It's awesome. I can't really read anything without it (so this issue is super frustrating; but this is a testament of how good Wallabag is)
The text was updated successfully, but these errors were encountered: