Closed Bug 1772232 Opened 2 years ago Closed 2 years ago

Enable/Implement remote settings on Android

Categories

(GeckoView :: General, enhancement, P2)

Unspecified
All
enhancement

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: agi, Assigned: agi)

References

(Depends on 1 open bug)

Details

(Whiteboard: [geckoview:m104?])

This is likely going to turn into a meta.

We currently do not support Remote Settings on Android which prevents us from using a lot of features inside Gecko related to security and privacy and more.

This is potentially related to intermediate certificates (Bug 1520297), OneCRL (Bug 1667179), ETP updates, and upcoming projects.

We should look into understanding why we can't reuse existing Desktop code.

How did you determine that RemoteSettings is not working? Could you share reproduction steps that shows that the feature is still broken on Nightly?

I am suggesting to test on Nightly (or at least Beta) because of the recent fix for bug 1761953.

Agi is investigating.

Assignee: nobody → agi
Severity: -- → S3
Priority: -- → P2
Whiteboard: [geckoview:m104?]

(In reply to Rob Wu [:robwu] from comment #3)

How did you determine that RemoteSettings is not working? Could you share reproduction steps that shows that the feature is still broken on Nightly?

So far it's mostly tribal knowledge. I don't think anybody in mobile knows exactly what the status of Remote Settings is. I see that bug and others seem to suggest it's enabled but we've thought it's not for a long time. I'll update this bug with my findings.

Depends on: 1617971

OK so I verified that Remote Settings do in fact work on GeckoView/Fenix. At this point I'm not sure where the knowledge that they didn't work come from.

I verified that:

  • we do update the settings when they are stale (i.e. older than 24h).
  • OneCRL receives updates from remote settings about revoked roots.
  • Dumps are loaded correctly from the APK.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.