Updated Product from Email to Synchronisation

Marking dupe as #5404 has a bit more information about this issue.

*** This bug has been marked as a duplicate of bug 5404 ***

Comment 3 Andre Klapper 2009-10-14 16:25:11 UTC

So a potential fix for this would be showing the error popup until the user
clicks it away, or what is the proposal?

(In reply to comment #3)
> So a potential fix for this would be showing the error popup until the user
> clicks it away, or what is the proposal?

That would probably work quite well when the sync has been triggered manually.
For automatic syncs happening in the background this would be too annoying.

(In reply to comment #4)
> That would probably work quite well when the sync has been triggered manually.
> For automatic syncs happening in the background this would be too annoying.

Well, yes and no.

Two points:

This bug relates to the "initial synchronisation", not any subsequent
synchronisation once the account has been setup. As such, I believe a specific
scenario should be used that would display the error longer (an example of how
unbalanced the UI during the initial synchronisation is that the warning
message that users shouldn't use Mail for Exchange and the Desktop Tool at the
same time never goes away unless clicked on, but the error messages don't stay
displayed) until user acknowledgement. Also, why is a summary screen being
displayed after a succesful initial synchronisation and but nothing if the
synchronisation fails? What happens to contacts or agenda items? How can a user
know what caused the failure? etc

When talking about subsequent synchronisations (automatic or
manually-triggered), there shouldn't be a change in the error reporting,
considering that the window which shows the "Manual Synchronisation" button can
be closed by an off-click, while still leaving the Synchronisation Process
running.

*** This bug has been confirmed by popular vote. ***

Comment 7 Andre Klapper 2010-01-05 17:02:32 UTC

So this currently includes several proposals which makes this becoming quite
complex. What exactly is the proposal now?
Summary screen showing the error if something went wrong?
Making the yellow error messages not go away until being tapped?

Comment 8 Andre Klapper 2010-01-05 17:17:18 UTC

(reverting unplanned severity change)

If the synchronisation fails, the user should be given the option to retry,
cancel or ignore.

Retry: The synchronisation restarts completely.
Cancel: Any temp files are cleaned up and the account is removed.
Ignore: The user accepts that the initial synchronisation failed, but doesn't
want to either cancel or retry at this time. The account is added however, and
synchronisation will occur during next scheduled events.

In order to allow for users to make an educated decision, the summary screen
should be displayed to inform the user correctly (in order to also diagnostic
which part caused the failure).

Based on the above, I propose that the both the yellow warning message remains
displayed until the user taps it, AND the summary screen is subsequently
displayed. Any probable causes (connectivity, wrong return from server, etc)
should be documented or logged either in the summary screen or a log file
available to the user.

Keeping the yellow blurb up until the user confirms could be very bad.

Sometimes I have flaky internet connection and the sync attempts to run
constantly, giving me many yellow blurbs.  If each one became persistent, or in
any other case where the sync kept retrying, it could lock up the UI and the
user wouldn't be able to do anything about it.

A better solution would be to do what Maemo 5 does if packages need updating. 
Put up a flag in the status bar and the user can click on it and take action
whenever they want.

Zach,

Please take into account that this is *ONLY* for the *INITIAL* synchronisation,
not any subsequent synchronisations, as indicated by the bug report.

Obviously, we don't want to trouble the user as soon as he walks away from a
hotspot, or into a hotspot, and the connection is switched/interrupted.
However, initial synchronisation is something the user has to stay up-to-date
about.

I hope this clears up things,

Comment 12 Andre Klapper 2010-01-14 12:32:22 UTC

Today Nokia released the Maemo5 update version 2.2009.51-1 for public (also
called "PR1.1" sometimes).
If you have some time we kindly ask you to test again if the problem reported
here still happens in this new version - just leave a comment (and feel free to
update the "Version" field to the new version if it's still a problem).

Comment 13 Andre Klapper 2010-01-18 16:26:14 UTC

Again: Any news for 2.2009.51-1 here, or everything as before?

(In reply to comment #13)
> Again: Any news for 2.2009.51-1 here, or everything as before?
> 

Problem still exists... still get stuck in the sync.

Comment 15 Andre Klapper 2010-04-09 15:31:47 UTC

In the upcoming PR1.2 release the error note stays on screen until user clicks
on it, if the first sync fails.

Comment 16 Andre Klapper 2010-05-19 15:04:22 UTC

Providing more verbose output for error messages is currently not planned by
Nokia for Maemo5 as this would require some code changes and quite some
translator work. Hence closing as WONTFIX to reflect internal status.