Open Bug 1996109 Opened 24 days ago Updated 12 days ago

Invalid pairing URL being sent to the FxA client

Categories

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

Product:
Firefox for Android
Component:
Accounts and Sync
Platform:
All
Android
Type:
defect

Tracking

()

People

(Reporter: bdk, Unassigned)

References

Details

(Whiteboard: [fxsync-])

We're currently getting a low, but consistent, number of invalid pairing URLs in the FxA client. The sentry discover tab reports about 10-20 a day on Fenix nightly.

I added some code to track these errors and they all seem to be coming from the begin-pairing-flow. The sanitized URLs are almost always blank, or just a number. I'm not sure how the URLs is generated, does it come from the server? Here's the sanitize_url function for reference on how we generate those.

I don't think this is particularly pressing, but it could be worth taking a look at.

Priority: -- → P1
Whiteboard: [fxsync-]
Severity: -- → S3
Priority: P1 → P2
You need to log in before you can comment on or make changes to this bug.