Open Bug 1937473 Opened 1 year ago Updated 4 months ago

sync suddenly stopped working in Firefox Beta 134.0b10

Categories

(Firefox for Android :: Accounts and Sync, defect)

Firefox 134
All
Android
defect

Tracking

()

UNCONFIRMED

People

(Reporter: tyotomy, Unassigned, NeedInfo)

References

Details

(Whiteboard: [fxdroid][group1])

Attachments

(3 files)

Attached video screen.mp4

Steps to reproduce

  1. Tap the Sync button in the Sync tab list or Account settings
  2. Sign out and then sign in again.

Expected behavior

The synchronization function will work to keep you up to date with the latest information.

Actual behavior

The buttons didn't work at all and no synchronization took place.
When I signed in again, it still didn't sync and the synchronization items column was greyed out.

Device information

  • Firefox version: 134.0b10
  • Android device model: Sharp AQUOS R5G SHG01
  • Android OS version: 12

Any additional information?

Deleting the cache or downgrading to 134.0b7 did not work, but I downgraded further to 133.0b8 and signed in again, and then I was able to sync again.

Same issue for me, on 135.0a1

The severity field is not set for this bug.
:boek, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jboek)
Flags: needinfo?(jboek) → qe-verify+
Whiteboard: [fxdroid][group1]
Severity: -- → S3

I was not able to reproduce this nor on Beta 134.0b10, nor on Beta 135.0b5, nor nightly 136.0a1 from 1/16.
Tested with:

  • Sony Xperia Z5 Premium (Android 7.1.1),
  • Google Pixel 9 Pro (Android 14), and
  • Google Pixel 6 (Android 15).

Could you retest on Beta 135.0b5, or the latest Firefox for Android Nightly and let us know if you are still experiencing this behavior?

Flags: qe-verify+ → needinfo?(tyotomy)

I'm experiencing it in 136.0a1 on a Xiaomi Redmi Note 9 pro

(In reply to Mira Lobontiu (Android QA) from comment #3)

I was not able to reproduce this nor on Beta 134.0b10, nor on Beta 135.0b5, nor nightly 136.0a1 from 1/16.
Tested with:

  • Sony Xperia Z5 Premium (Android 7.1.1),
  • Google Pixel 9 Pro (Android 14), and
  • Google Pixel 6 (Android 15).

Could you retest on Beta 135.0b5, or the latest Firefox for Android Nightly and let us know if you are still experiencing this behavior?

Sorry for the delay in responding.
I am currently not reproducing the problem on my devices with the latest version of Firefox Beta, including the AQUOS R5G which had the problem.
The problem did not occur on other devices with the same version at the time, so something may have triggered the problem, but it is not happening now, so I don't know the details.

Flags: needinfo?(tyotomy)

would it be possible to get any logs adb logcat that are output when tapping the sync button?

Flags: needinfo?(tyotomy)
Flags: needinfo?(GODAXEN)
Attached file LogCat Dump
``
Attachment #9462305 - Attachment description: OK → LogCat Dump
Flags: needinfo?(GODAXEN)

now with the last update (version 136.0a1 build #2016070495) it appears that sync works again.

PD: I think that for beta and nightly is important to add the build version and a reminder to do it can be useful.

I currently do not have this problem and will get logcat if it occurs. Sorry.

Flags: needinfo?(tyotomy)
Attached file logcat.txt

This occurred with AQUOS R5G and Firefox Nightly 137.0a1 #2016072231, so I am attaching the log.
The top is the device with the problem, and the bottom is the device that works fine.

The failing device is seeing:

02-09 16:49:03.838 23399 23520 W sync15::client::sync_multiple: sync failed: Network error: [no-sentry] Network error: Java error: "fetch error: org.mozilla.geckoview.WebRequestError: Request failed, error=0x25, category=0x5", final status=NetworkError

which doesn't give much info, but for some reason it seems to be failing with error NS_ERROR_NOT_RESUMABLE (which tbh doesn't really make sense). Is there anything different/custom about the network config of that device?

Mark, is there anything that we can do to increase our ability to observe or debug these types of issues? It seems like we're getting enough reports that don't feel actionable on their own.

Flags: needinfo?(markh)

(In reply to Mark Hammond [:markh] [:mhammond] from comment #11)

The failing device is seeing:

02-09 16:49:03.838 23399 23520 W sync15::client::sync_multiple: sync failed: Network error: [no-sentry] Network error: Java error: "fetch error: org.mozilla.geckoview.WebRequestError: Request failed, error=0x25, category=0x5", final status=NetworkError

which doesn't give much info, but for some reason it seems to be failing with error NS_ERROR_NOT_RESUMABLE (which tbh doesn't really make sense). Is there anything different/custom about the network config of that device?

Sorry for the delay in replying.
I have AdGuard turned on HTTPS filtering and DNS filtering on both the device with the problem and the device without the problem, and Firefox is excluded from AdGuard, but the problem is not resolved by turning AdGuard on or off, and since I have it on the device without the problem, I think it is excluded.
This problem also occurred with the latest version v136.0b9 on a different device than the one I commented on above.
The only thing I can say is that downgrading to v133.0b9 will keep it synced correctly.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: