Open GoogleCodeExporter opened 9 years ago
Sounds like the server is retuning an empty list instead of giving an outright
failure, which looks to Precipitate like you've removed all your bookmarks.
When I have a chance I'll get the URL for you to test in a browser to see
what's being returned.
Original comment by stuart.morgan
on 27 Mar 2012 at 11:30
Thanks. Here's a followup.
- Removed the prefpane, stopped the service.
- deleted ~/Library/Caches/Metadata/Precipitate
- Rebooted
- reinstalled 1.07
- re-auth'd to google with new app-specific pw
Now I have folders for docs and picasa inside
/Users/XD/Library/Caches/Metadata/Precipitate, but nothing for bookmarks.
Prefpane UI indicates all three services are syncing successfully. See
SyncStatus below.
Bookmarks look and behave normally at https://www.google.com/bookmarks/
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>com.google.precipitate.GoogleBookmarksSource</key>
<dict>
<key>LastAttemptedSync</key>
<date>2012-03-27T19:39:28Z</date>
<key>LastSuccessfulSync</key>
<date>2012-03-27T19:39:28Z</date>
</dict>
<key>com.google.precipitate.GoogleDocsSource</key>
<dict>
<key>LastAttemptedSync</key>
<date>2012-03-27T19:40:17Z</date>
<key>LastSuccessfulSync</key>
<date>2012-03-27T19:40:17Z</date>
</dict>
<key>com.googlecode.precipitate.PicasaWebAlbumsSource</key>
<dict>
<key>LastAttemptedSync</key>
<date>2012-03-27T19:39:32Z</date>
<key>LastSuccessfulSync</key>
<date>2012-03-27T19:39:32Z</date>
</dict>
</dict>
</plist>
Original comment by greg.bumpus
on 27 Mar 2012 at 7:58
Ah, I see what's happening. The XML feed still works in a browser with a
logged-in session, but the trick of making the request directly to get an HTTP
auth isn't working any more. Instead, it's now redirecting to an account login
page.
It's possible that switching to using a fetcher that has authenticated through
the GData API would work now (it didn't used to), but given that this isn't
actually an API it's unlikely.
Original comment by stuart.morgan
on 1 Apr 2012 at 7:28
Original comment by stuart.morgan
on 1 Apr 2012 at 7:32
That's interesting. I'll really appreciate any info from those deep into the
code regarding a fix. I will test any early build as soon as ready.
Original comment by greg.bumpus
on 4 Apr 2012 at 4:10
Original issue reported on code.google.com by
greg.bumpus
on 26 Mar 2012 at 5:51