Could not connect to simplenote server

[fladd]

I put in my correct credentials in .nvpy.cfg.

[yuuki0xff]

Does the log file contain error messages? Usually, the log file is located on ~/.nvpy/nvpy.log.

[fladd]

Yes, it says:

2019-07-25 15:55:05,879 - DEBUG - Starting full sync.
2019-07-25 15:55:07,696 - ERROR - Sync step 1 error - Could not update note af4f81adc6792da60f1fa848deef924a to server: {u'modifydate': 1474831663.700904, u'tags': [u'test'], u'deleted': False, u'createdate': 1443298589.169, u'shareURL': u'', u'publishURL': u'9TrVP2', u'systemtags': [u'markdown', u'published'], u'content': u'# Title #\n\nThis is a test.\n\n## Section 1 ##\n\nNow a list:\n\n- a\n- b\n- c\n\nSome code:\n\n```\ndef test(a, b):\n    return a + b\n```\n\n\n', u'version': 39, u'systemTags': [u'markdown', u'published'], u'key': u'af4f81adc6792da60f1fa848deef924a', u'modificationDate': 1474831663.700904, u'creationDate': 1443298589.169}

[yuuki0xff]

Sorry for the late reply.
It seems that failed to update the note object via Simperium API. Perhaps this issue will be fixed by following way.

1. Close nvpy.
2. Update the note from Web UI (https://app.simplenote.com/) or official mobile app. The title of the note to be updated is # Title #.
3. Start nvpy.

If it couldn't fix the problem, please run the following command and show the error messages.

# Update nvpy to the latest development version
python2 -m pip install --upgrade 'git+https://github.com/cpbotha/nvpy.git#egg=nvpy'

[stochashtic]

I have the same issue with error message "HTTP Error 400: Bad Request" (pop-up message + in log file)

nvpy 1.2.2-dev

No problems syncing FROM server a week ago when I installed this version. Problem only arose from trying to sync TO server today when I updated a note.

Now it's in a loop trying to update the note to server so I can't test whether syncing FROM server is also an issue now.

[yuuki0xff]

Now it's in a loop trying to update the note to server so I can't test whether syncing FROM server is also an issue now.

Please follw the steps below. Note that local changes are discarded.

1. Exit the nvpy.
2. Find the local key of the note that failed to update. See ~/.nvpy/nvpy.log.
3. Remove ~/.nvpy/<LOCAL_KEY>.json.
4. Start the nvpy.

For more than half a year, this problem has not occurred on my computers. So difficult to identify the cause. Please let me known if you have noticed anything.

[stochashtic]

Okay, so I deleted the note from the local store as you advised, and all seems to be working now.

->Syncing both ways works again

[stochashtic]

Premature happiness.

I edited a few notes and no problem. But then ....

Issue has returned. Same error after editing a (different) note.

[stochashtic]

Testing ...

I edited a different note than the one having the issue and no problem (synced).
I can see several notes with tags (recently added) in nvpy that don't exist in Simplenote.
Weirdly, I can't add tags anymore in nvpy (not even working locally)
If I add a tag on Simplenote, it syncs fine to nvpy.

I wonder if the issue is with syncing tags from nvpy to server???

[stochashtic]

Further testing...

Tags not working locally is a UI issue when the suggested tags list pops up. Will raise separate thread later

Tags are not the issue. I was able to update tags on one note.
So it appears as a random issue. Some notes work; some don't.

All very weird.

[stochashtic]

Confirming issue is still there. nvpy unusable for me. Forced to use Simplenote directly.

[yuuki0xff]

Thank you for your testing.

I fixed the UI issue on 8264790. In addition, I fixes minor issues. These are available on the master branch.

For sync issue, I need more information. Please show the local and remote note when sync error occur. Of course, you can mask the content field to protect your private data.

Two notes can be accessed in the follwing ways:

• Local note: ~/.nvpy/<LOCAL_KEY>.json
• Remote note: ./debug-utils/get-note-from-server.py <REMOTE_KEY>

I would appreciate your cooperation to solve this issue.

[stochashtic]

I wiped my whole note cache and re-started. Stable so far. Will update if issue re-arises. Apologies for delay in responding.