Closed jonvuri closed 12 years ago
If NV is timing out when attempting to login, then that simply means Simplenote is not returning a response to NV. There's nothing you can do about this aside from contacting Simplenote support.
I've seen a huge uptick in these reports with nothing changing on the nvALT end but haven't had a chance to ask Simplify what's up.
Huh... After you said that, I figured that nvALT could have done something to the data or config to screw something up, so I tried moving the Notational Data directory somewhere in an attempt to force NV to start fresh and pull everything from Simplenote. Little did I know that it would be smart enough to track the move; the setting simply changed when I reopened NV. However, it DID fix the problem. It logged in and synced just fine. Color me very confused at this point (but happy that it's worked out).
I actually encountered this issue first in nvALT. Changing back to Notational Velocity, I found the same issue. This doesn't necessarily narrow it down to a Simplenote issue, though, since nvALT is just a fork.
This happens every single time NV tries to sync for me. It hasn't synced at all for some time now.
Notational Velocity[777]: Fetcher(104EDF0, https://simple-note.appspot.com/api/login) returned The request timed out.