1884641 - [POCKET] A periodic Firefox job resets region settings and disables Pocket

Status: RESOLVED WORKSFORME

(Firefox :: New Tab Page, defect)

Description

[Artem S. Tashkinov]

Steps to reproduce:

I've no idea what IP geographic provider Mozilla uses but my IP belongs the the territory where Pocket works, yet your provider insists my IP comes from an unrelated county in the EU where Pocket is not featured/disabled/whatever.

I'm extremely tired of fixing/reverting the values of these three variables which periodically get reset and thus I'm left without Pocket:

browser.region.update.region
browser.search.region
doh-rollout.home-region

How can I force Firefox not to alter them?

Whether it's a bug or not, it's up to you to decide. I just need a solution.

What sucks even more is how completely opaque the Pocket integration is. Firefox simply decides based on some unknown factors (an IP provider which seemingly you have no control over) whether you'll get it or not and there are no user visible toggles to configure it. That looks like madness to me. How is it even possible?

What if I am a US citizen travelling the world and I want to get/see Pocket articles?

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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

For more information, please visit BugBot documentation.

Comment 2

[Scott [:thecount] Downe]

I don't know what's going on with why your region is being incorrectly determined, but if you set browser.region.update.enabled to false, it should stop resetting it.

I did notice you listed browser.region.update.region, which is not a pref I am aware of. Did you mean browser.region.update.enabled instead? Maybe you did, and maybe that's not been working for you?

Comment 3

[Artem S. Tashkinov]

The region settings are stored in

browser.region.update.region
browser.search.region
doh-rollout.home-region

I didn't know browser.region.update.enabled existed, so it settles it for me.

Comment 4

[Scott [:thecount] Downe]

Glad it's sorted now, and thanks for reaching out.