Google Docs not updating - stalled error message in system prefs pane

[GoogleCodeExporter]

What steps will reproduce the problem?

   The problem is ongoing and occurred when I first attempted an update
through the system prefs pane.

What is the expected output? What do you see instead?

   I would expect to see the Google Docs error message clear after a
successful update.  Instead, the error message has not changed - and the
update button does not become available again until after I close the
system prefs pane.  See comments below for error message.

What version of the product are you using? On what operating system?

   Version: 1.0.  Mac OS X 10.5.4

Please provide any additional information below.

From comment in Issue 4: I'm having a similar problem under Mac OS X
10.5.4.  My bookmarks update fine - no Docs, unfortunately.  My
~/Library/Caches/Metadata/Precipitate/com.google.precipitate.GoogleDocsSource
does not exist.  My console.log has no messages from Precipitate.  I do see
a red status message in the Precipitate system panel: "Failed Jul 4, 2008
9:11 AM (No login information)"  This message has not changed even after
multiple attempts to refresh.  I know my login is working because the
Bookmarks are updating fine. Additionally, the only way I can get the
"Refresh Now" button to be active is to close the System Preferences window
and open it again.

Hope this helps! It's a great product idea - and looking forward to seeing
a fully functioning app.

Original issue reported on code.google.com by nfre...@gmail.com on 4 Jul 2008 at 10:54

[GoogleCodeExporter]

If you've visited Google Bookmarks in your browser, it may not be trying to use 
your
login information. If you search for "precipitate" in Keychain Access (in
Applications/Utilities), is there an entry?

You said the Refresh Now button is disabled; is there a spinner running next to 
it?
If so, there is a sync in progress, so the button is supposed to be disabled
(quitting and re-opening prefs will cause it not to know that there is a sync
happening, which is why it would re-enable).

Original comment by stuart.morgan on 4 Jul 2008 at 11:05

[GoogleCodeExporter]

"If you've visited Google Bookmarks in your browser, it may not be trying to 
use your
login information."

OK.  I have visited the bookmarks in my browser.

"If you search for "precipitate" in Keychain Access (in 
Applications/Utilities), is
there an entry?"

Yes, there is a "Precipitate: Google Account" entry.

"You said the Refresh Now button is disabled; is there a spinner running next 
to it?"

Yes, there is a spinner.  But I've left it sitting for over 30 minutes - but 
perhaps
that's just not long enough?  Thinking about it now, I suppose the amount of 
data
being downloaded could be significant enough to warrant a longer download time. 
Perhaps this warrants an indication of sync status to the user (e.g., estimate 
of
time left)?

"quitting and re-opening prefs will cause it not to know that there is a sync
happening, which is why it would re-enable"

Does this mean a sync is supposed to continue in the background even when the 
prefs
pane is closed?  If so, then a sync should have been running for a time going on
seven+ hours now - unless hitting the re-enabled refresh button restarts the 
sync (or
stalls it in a bad state).

Let me know if I can provide any other info to help you debug this.

Original comment by nfre...@gmail.com on 4 Jul 2008 at 11:34

[GoogleCodeExporter]

By the way, I have an iStat menu showing the amount of network traffic in and 
out of
my machine.  Just now, the precipitate pref pane had the refresh spinner running
after I had hit the re-enabled Refresh Now button but there was no network 
traffic. 
So, I'm guessing the sync is in a bad state and not able to restart or continue.

Original comment by nfre...@gmail.com on 4 Jul 2008 at 11:43

[GoogleCodeExporter]

Same as Reported by nfreier

What steps will reproduce the problem?

   The problem is ongoing and occurred when I first attempted an update through the system prefs pane.

What is the expected output? What do you see instead?

   I would expect to see the Google Docs error message clear after a
successful update.  Instead, the error message in red reads "Failed 4 Jul 2008 
15:46 (No login information)". If 
I hit the refresh button, the Google bookmarks update time changes to current. 
The spinner is still running.

What version of the product are you using? On what operating system?

   Version: 1.0.  Mac OS X 10.5.4

Please provide any additional information below.

I only have 2 Google docs right now.
The only doc in /Users/klaus/Library/Caches/Metadata/Precipitate/ is 
"SyncStatus"

Original comment by KFech...@gmail.com on 4 Jul 2008 at 11:55

[GoogleCodeExporter]

Yes, the sync happens in the background regardless of the pref pane being open; 
the
pref pane is just there to allow configuring it and checking on status.

Could you both install the just-released 1.0.1? While the bug it fixes isn't 
likely
to be related, installing it should kill and restart the background agent then 
start
a new sync, which would help if your agent is somehow wedged.

Original comment by stuart.morgan on 5 Jul 2008 at 1:15

[GoogleCodeExporter]

After installing the 1.0.1 version, precipitate synced the google docs properly 
- and
it works great!  I love this app - very cool.  I suspect you are right - that 
this
just killed and restarted the agent.  If I can be of any help in tracking down 
the
initial cause of this, let me know.

Original comment by nfre...@gmail.com on 5 Jul 2008 at 1:36

[GoogleCodeExporter]

Do you have any PDFs in your Google Docs account? One possibility is that the 
first
error was because it started syncing before the account info was there, then 
the fact
that it never updated again was because of the bug 1.0.1 fixed.

Original comment by stuart.morgan on 5 Jul 2008 at 3:53

[GoogleCodeExporter]

Yes, I have PDFs in my account.  That seems like a reasonable explanation - 
though it
seems odd that I don't have any messages in the console log.  Nonetheless, 
thanks for
the fix.  Already seeing the benefits.  Cheers.

Original comment by nfre...@gmail.com on 5 Jul 2008 at 4:31

[GoogleCodeExporter]

Closing as a duplicate of the PDF issue then, since the failure message seems 
to have
been a red herring.

Original comment by stuart.morgan on 5 Jul 2008 at 5:43

• Changed state: Duplicate