commit | ce2d1034d5a43f861ee67566a8fe02a19b47e171 | [log] [tgz] |
---|---|---|
author | Robbie Gibson <rkgibson@google.com> | Wed Apr 02 22:06:04 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 02 22:06:04 2025 |
tree | 0197c23f1b15a07cb3960f4e916ed81a225186bb | |
parent | 284d8f2fc9b8b58c99ceaa939d5381fb4882889b [diff] |
Reland "[iOS] Make use of the default status API" This is a reland of commit 925b71a1a3308507876f1f1229a02865c06137fa There were 2 issues in the initial commit that caused a revert: First, the Default Status API doesn't exist on maccatalyst, so many symbols are undefined there. This was fixed by skipping the default status checks on maccatalyst. Second, storing the fake system call directly caused a static initializer issue. This was fixed by storing the fake system call in a static variable declared in a method instead. Original change's description: > [iOS] Make use of the default status API > > Integrates with the Default Status system API. The integration works as > follows (high-level summary): > > - Clients that are on iOS 18.4+ and have completed the First Run > Experience since at least 28 days are randomly assigned to a > cohort number between 1 and 4 at startup. The idea is to spread > clients out throughout the year: > - Cohort 1: January, May, September > - Cohort 2: February, June, October > - Cohort 3: March, July, November > - Cohort 4: April, August, December > - At each startup, if the current time is in or after the month > corresponding to the client's cohort number for this quarter, > the system's Default Status API is queried and the results are > recorded to histograms and local prefs. > - Clients can still report their default status if they are outside > their assigned cohort's reporting months, but they do so in > different histograms, so that the impact of "cohort drift", a > phenomenon where clients will tend to report later and later each > year depending on usage frequency, can be better evaluated. > > Bug: 401075747 > Change-Id: I97b28d0c41dff367abcff21de89f0fc5418a79aa > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6282328 > Reviewed-by: Robbie Gibson <rkgibson@google.com> > Commit-Queue: Robbie Gibson <rkgibson@google.com> > Reviewed-by: Olivier Robin <olivierrobin@chromium.org> > Reviewed-by: Rohit Rao <rohitrao@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1439483} Bug: 401075747 Change-Id: I5345263c83ba7829f834c2948f8ae8097ce103e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6409732 Commit-Queue: Robbie Gibson <rkgibson@google.com> Reviewed-by: Olivier Robin <olivierrobin@chromium.org> Reviewed-by: Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/main@{#1441828}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.