Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Unexpected JSON token warning #70

Open
cinghiopinghio opened this issue Oct 31, 2021 · 4 comments
Open

Unexpected JSON token warning #70

cinghiopinghio opened this issue Oct 31, 2021 · 4 comments

Comments

@cinghiopinghio
Copy link

Hi,

Since few days I receive weird warnings from the app on Android.
The app is notifying the following:

Unexpected JSON token at offset 0: Cannot begin reading element, unexpected token: 127
JSON input:

I suspect that one file is broken but I don't know how to find that file.
I checked manually the last changed files in the syncthing directory but I found nothing clearly wrong.
I have no conflicting files.
If I add new entries to the calendar, the devices sync without problems except the notification on Android.

@39aldo39
Copy link
Owner

39aldo39 commented Nov 5, 2021

I have no idea how the ASCII DEL character can end up in the files, but if you use Linux I think you can look for the broken file by executing grep -re "\x{FF}" ~/.local/share/decsync.

@cinghiopinghio
Copy link
Author

Unfortunately I couldn't find any weird character on the device files. The problem persisted.

Now, while forcing the same device to update to v2 for tasks, the problem is magically gone, so I cannot help with further debugging.

@cinghiopinghio
Copy link
Author

Well. After sanitizing my shared folder I got a period of few days where everything worked fine.

Today after a sudden unwanted reboot of the phone, the error came back. I grepped the folder looking for the offending file without success.

Is it possible that the character ended up in the database due to a sudden forced kill of the app?

I got the annoying notification every time the app try to refresh.

@cinghiopinghio
Copy link
Author

The problem was solved when I cleared the app cache through the system settings.

Which favours the database issue hypothesis.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants