FxA: OriginMismatch
bendk opened this issue · 1 comments
bendk commented
We're currently getting about 10-50 OriginMismatch errors a day on Fenix nightly.
I believe the only source of this is an invalid pairing URL. Are these origin mismatches expected?
┆Issue is synchronized with this Jira Task
┆Epic: Moving fxa-client functionality out of android-components
bendk commented
It's an expected error when you try to pair two devices that have different server configs (for example one pointed at prod and one at stage). #5921 makes is so we'll just count these in glean, not create sentry reports, and not include them in the fxa_other counts. This seems good enough for now, let's close this.