726088 - "canceling and rescheduling sync because it ran too long"

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: Android Sync, defect, P3)

Description

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Attachment: logcat

When trying to sync with a Sony Ericsson, asset does not match:


02-10 18:53:36.080: D/dalvikvm(1778): GC freed 8878 objects / 861376 bytes in 134ms
02-10 18:53:37.010: E/vending(1778): [41] UpdateTask.doInBackground(): Image response asset ID 5084781000954763510, no matching asset response
02-10 18:53:37.210: I/ActivityManager(1158): Starting activity: Intent { act=android.settings.ACCOUNT_SYNC_SETTINGS cmp=com.android.providers.subscribedfeeds/com.android.settings.AccountSyncSettings (has extras) }
02-10 18:53:37.240: V/SyncSettings(1158): Got account: Account {name=[e-mail], type=org.mozilla.firefox_sync}

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Note: I don't see any of the bookmarks imported in Fennec.

Comment 2

[Richard Newman [:rnewman]]

The log tag "vending" is nothing to do with us; that's some Android daemon.

There are oddities in the log, such as:

  Could not find method android.util.Base64.encode, referenced from method ch.boye.httpclientandroidlib.impl.auth.BasicScheme.authenticate

and:

handleSyncHandlerMessage: sync context doesn't match, dropping: mActiveSyncContext null != startTime 182734050, mTimeoutStartTime 182734050, mHistoryRowId 211, syncOperation authority: org.mozilla.fennec_aurora.db.browser account: Account {name=[e-mail], type=org.mozilla.firefox_sync} extras: [] syncSource: 0 when: 182734012 delay: 0 key: {authority: org.mozilla.fennec_aurora.db.browser account: Account {name=[e-mail], type=org.mozilla.firefox_sync} extras: []} pendingOperation: android.content.SyncStorageEngine$PendingOperation@45c7fc90


but here's the problem:

canceling and rescheduling sync because it ran too long: authority: org.mozilla.fennec_aurora.db.browser account: Account {name=[e-mail], type=org.mozilla.fir

Well, that explains it.

Comment 3

[David Chan [:dchan]]

(In reply to Richard Newman [:rnewman] from comment #2)
> The log tag "vending" is nothing to do with us; that's some Android daemon.
> 
> There are oddities in the log, such as:
> 
>   Could not find method android.util.Base64.encode, referenced from method
> ch.boye.httpclientandroidlib.impl.auth.BasicScheme.authenticate
> 

The Xperia is running Android 2.1 (API level 7). android.util.Base64 requires API level 8 [1]

[1] - http://developer.android.com/reference/android/util/Base64.html

Comment 4

[Allison Naaktgeboren :ally]

This sounds like it is below our supported version and beyond our control. Is there anything we can do?

Comment 5

[Richard Newman [:rnewman]]

(In reply to :Ally Naaktgeboren from comment #4)
> This sounds like it is below our supported version and beyond our control.
> Is there anything we can do?

We could ship our own Android base64 lib. I'd be happier to just push on Bug 662891.

Comment 6

[Richard Newman [:rnewman]]

Filed Bug 730637 to track Base64.

Gonna INCOMPLETE this one, because addressing the system 5-minute timeout seems like a fool's errand.