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
JSONException: No value for Invalid #291
Comments
The value for the json key "Invalid" is null for some reason. Looks like an upstream problem of some kind. |
I dont think that it omits empty values, though perhaps the answer was something else than the config, hence it wasn't present at all? But then you wouldn't be able to traverse all the way down to the invalid key. |
|
|
This is a very frequent problem based on logs from the play store:/ |
I tracked all upstream paths but could not see a pattern which would lead to a missing 'invalid' field. Therefore syncthing-android/src/main/java/com/nutomic/syncthingandroid/syncthing/RestApi.java Line 533 in 2ed6dac
|
It would help to find out under what circumstances this happens. I just tried some things and couldn't reproduce. Maybe it was fixed upstream in the meantime? |
No nothing changed in that regard. If we disable this fix, it will trigger this bug very infrequently. |
Is this still relevant? |
It is, with daily crashes on the play store dashboard. |
Do you have an indication if it is specific to a version of android or syncthing or syncthing-android? |
Not relevant any more, ecause Gson ignores missing keys. |
* Fix crash notification reason is off-screen (fixes syncthing#294) * Indicate a broken config on the welcome wizard (fixes syncthing#293) * SyncthingService must stop if the config got corrupted (fixes syncthing#292) * Show crash notification extraInfo below notification title (fixes syncthing#294) * Fix NPE when config elements gui, options are missing (fixes syncthing#291) * Updated de translation * Update en translation * Updated translations * Remove debug log
Not sure?
The text was updated successfully, but these errors were encountered: