Common Syncing Problems

The most common support query I get — over 90% of all emails — is about Yummy’s ability to sync with Delicious or pinboard. This page summarises the most common error messages, what they mean and what you can do if you get them.

“ says that you’re refreshing too quickly”

If thinks that you’re connecting to their servers too often, they stop responding to your requests. This is most likely to happen if you try to sync multiple clients in rapid succession or, perhaps, start Yummy syncing and press the “Home” button on your iPhone. Yummy does not currently continue syncing in the background so the next time you launch it, it starts the whole process again.

The answer here is to exit Yummy and wait a while before trying again. You might also try switching to a different network (e.g., from 3G to WiFi) and try again.

Error Code 429

This means “ says that you’re refreshing too quickly.” It has exactly the same cause and the exact same solution as the above error experienced when using Delicious. In my experience this is less common and you’re really only likely to see it if you use other third-party clients.

Error Code 999

This is Delicious’ general error; “Something went wrong but we’re not exactly sure what.” In practice is means pretty much the same thing as the ‘refreshing too quickly’ error and can be treated in exactly the same way.

Error Code 500

There are two possible sources for this message. If the error comes directly from Delicious, then your best option is simply to wait a bit and try again. These problems are usually temporary and they usually fix themselves.

Alternatively, it could be your wireless connection. 3G networks, especially, sometimes do weird things with messages before they get to their destination. The quick-and-dirty solution is just to use a different network. WiFi networks are usually more reliable and quicker and have fewer oddities.

The other option is to go into the settings and change the “Sync Speed” option. This will either be set to “Fastest” or “Normal” depending on how you authenticate with Delicious. If you switch this to a slower setting it should make the syncing more reliable, albeit slower.

Error Code 502

Just retrying usually “solves” this problem. I’m pretty confident that this is a configuration error on the Delicious side since I am also seeing this occasionally on the website as well, though I am continuing to investigate.

“The certificate for this server is invalid”

This has happened around the middle of May for the last couple of years. It means that Yahoo! have forgotten to renew their SSL certificates (or that something has been misconfigured). This means that your iPhone cannot establish a secure connection with the servers and, therefore, refuses to continue.

The solution to this is to wait until Yahoo! renew and correctly configure their certificate.

%d bloggers like this: