Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sharedStorage API unavailable on some devices regardless of tpc-phase-out-facilitated-testing #430

Open
zapo opened this issue Oct 29, 2024 · 8 comments
Labels
chrome-testing Chrome-facilitated testing discussions

Comments

@zapo
Copy link

zapo commented Oct 29, 2024

Hello we're working with sharedStorage API and we have noticed on some devices that that the API is unavailable eventhough some other PS APIs are available (eg navigator.joinAdInterestGroup) regardless the label used for tpc-phase-out-facilitated-testing, including the force treatment label.

For those window.sharedStorage is undefined and can only be turned back on by using --enable-privacy-sandbox-ads-apis=true flag.

If this is expected (due to experiment groups?) and if so is there a documentation describing the proportion of devices having a partial set of APIs enabled?

@zapo zapo added the chrome-testing Chrome-facilitated testing discussions label Oct 29, 2024
@zapo
Copy link
Author

zapo commented Oct 29, 2024

For what it's worth we are experiencing similar issues with navigator.cookieDeprecationLabel, on some device getValue returns a promise that never resolves, and others navigator.cookieDeprecationLabel is undefined or resolves to empty string, while they have the force treatment label. This seems to be a new behavior since upgrading to Chrome 130.

I can file separately if unrelated.

EDIT: cookieDeprecationLabel DOES resolve sorry ... I was using console logging to debug and didn't realize I had a remnant filter 🤦

@bjoberg
Copy link

bjoberg commented Oct 31, 2024

Hi @zapo I am actually running into a similar issue: #429.

What was your remnant filter and how did you get the cookieDeprecationLabel to resolve?

@zapo
Copy link
Author

zapo commented Nov 1, 2024

@bjoberg I forgot I was using a console logging filter and was inspecting the promise result using console.log. The absence of log output lead me to think the then handler was never called like in following screenshot.
image

It's unrelated to the original issue and a debugging mistake. In your ticket the promise does resolves as well but seem to resolve to empty string.

@johnivdel
Copy link

Hi @zapo, would you be able to paste the contents of chrome://version?

For a small set of users, we expect there to be only a subset of APIs supported; see the footnote 1 on this Privacy Sandbox blog.

Roughly 1% of users will have the other APIs available without Shared Storage.

Let me know if you have any further questions or if the above was unclear, thanks!

@bmilekic
Copy link

bmilekic commented Nov 5, 2024

@johnivdel Here's my chrome://version output -- note that I'm a colleague of @zapo and the one with the Chrome instance that appears to have Shared Storage off by default, but the other PS APIs seemingly on.

Google Chrome	130.0.6723.92 (Official Build) (arm64) 
Revision	ef4f16c57010eb3e047ef101019b869296173bd9-refs/branch-heads/6723@{#1518}
OS	macOS Version 15.0.1 (Build 24A348)
JavaScript	V8 13.0.245.18
User Agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
Command Line	/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --restart --restart --flag-switches-begin --privacy-sandbox-enrollment-overrides=https://spangled-lead-muskmelon.glitch.me --flag-switches-end
Executable Path	/Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path	/Users/bmilekic/Library/Application Support/Google/Chrome/Default
Linker	lld
Active Variations	853552cb-ef4fd7e3
f362f7ae-8a514a01
a647d113-ca7d8d80
191df81f-377be55a
158e27e-6edc92c7
f69863c5-ca7d8d80
45bb09c-8c02189c
bb88d3f2-ca7d8d80
db0f7f8d-ca7d8d80
86c1f78-ca7d8d80
f3daed27-ca7d8d80
ee1a3df6-ca7d8d80
3af515aa-ca7d8d80
768eeee-5dd67d03
b1de23e3-3f2a3d9
8e9fafcb-377be55a
9571ff81-ca7d8d80
a6d4bd0c-377be55a
aab1a393-377be55a
dbfa96f6-377be55a
dc88470b-ca7d8d80
13427e22-ca7d8d80
8a8e440e-12ede6a2
6b7d4090-ca7d8d80
efd80f4a-ce53db7b
807f351f-ada841cd
dae40d1d-aefb8fe9
90dda23e-377be55a
b7ed4ad2-ca7d8d80
3d15a2-ca7d8d80
c66576a2-d5b56580
da3a2e5-377be55a
2509a2d9-ca7d8d80
37d8b29f-bb36e9b8
26016f9f-ca7d8d80
bc8fd675-ca7d8d80
3095aa95-3f4a17df
3d828cea-33c3eba5
2353d10c-ca7d8d80
797fe373-ca7d8d80
f112f553-ca7d8d80
cc495fca-9553273a
611660f3-2e6df32
83492eae-9550adcc
ae35eb0-a273df21
86bc59c9-377be55a
ac36f7c6-f9b8d952
adfbede8-ca7d8d80
5133eb43-12ede6a2
d9fcff10-6733876a
16500b7b-20a7d0e1
e4f3e501-e471b7aa
4ea20d73-ca7d8d80
44d0ae84-1d0d835a
a98def31-27d03596
df982186-28ad44a
7627ad7c-79d95619
3864eb98-267ee94d
27b4de92-ca7d8d80
d446ca5c-377be55a
a83aa76f-34824d09
b652e8cd-ca7d8d80
f8411335-12ede6a2
a582a1b8-5ad3f43d
caf19648-ca7d8d80
3c4bd797-7f3e334d
bd6dd170-12ede6a2
669a7db8-ca7d8d80
fc75eabb-377be55a
780df7d2-ca7d8d80
87684b46-ca7d8d80
8b726c45-12ede6a2
92f02c26-a6d95901
ae1581ef-ca7d8d80
c0876afc-377be55a
8926502a-ca7d8d80
b654e8a3-377be55a
31a21008-377be55a
f43fe77d-5d07a5be
96d006a-ca7d8d80
b3a4e30a-ca7d8d80
f42905ff-ca7d8d80
87109b74-3fa75b73
d6bfa1df-9d446b22
b44af8a4-3fa75b73
1bb693bf-cc4e1a9d
7500995e-9d446b22
37509198-9d446b22
ae9d51b2-1f8c5973
e9844d40-ca7d8d80
ad9b71e2-67681518
ff7b894f-377be55a
d2aa7cc-ca7d8d80
d43ddfd9-e36235cc
5a474f9e-ca7d8d80
87e6920a-ca7d8d80
b86bee04-377be55a
725a78a7-33c3eba5
f2700d05-447c4e90
8d7cfdfb-3dbb4b5e
86328c20-ca7d8d80
dcceede7-62b9a496
2394f90f-377be55a
5b2f4944-377be55a
4b82c9ff-ca7d8d80
c88fa1e2-ca7d8d80
ad44b293-377be55a
cb85e943-377be55a
56aa5797-f6e715db
f503a768-ca7d8d80
9dea5087-ca7d8d80
68fef0c-e842c7eb
aa21b99b-a273df21
c63e3410-364f72c4
b76b514f-ca7d8d80
55c5338b-ca7d8d80
b33374a1-ca7d8d80
2ad820b5-666f78d9
59a12fbe-bb472f3f
7769705-d34910a9
45a2f2f-7b6b9ff7
de7bb458-9694bc15
66b7a83f-ca7d8d80
86362250-7ee694f0
ecd9add5-377be55a
4ea303a6-ecbb250e
4190c9c9-ca7d8d80
79662520-ca7d8d80
aa540f4f-ca7d8d80
f3b6291d-ca7d8d80
f5181214-ca7d8d80
68837d01-ca7d8d80
3dec691c-ca7d8d80
1edcddf4-2d58eb1b
5e8e6e2-b8a3c2b8
5f30b51a-377be55a
791c69f2-c605283f
d2094477-1f8c5973
39bb70f9-ca7d8d80
ea0d881d-ca7d8d80
3574b3d7-377be55a
2bac9a6a-ca7d8d80
ced7ce3e-ca7d8d80
f73677d0-258f1474
615f375c-3f4a17df
2a9d508a-377be55a
755d95c0-ca7d8d80
d0083347-644d89db
af07f8be-b149f28c
ccc5f0aa-ca7d8d80
d384e2ea-ca7d8d80
c26ea5ae-ca7d8d80
4b266bfd-ca7d8d80
b6979190-ca7d8d80
dd037d0e-82c2bbe8
5f082a30-ca7d8d80
90860314-18b4e153
494d8760-52325d43
e71a2099-f08f240b
7b2873c2-361a10de
3ac60855-486e2a9c
f48c01d3-324bad6d
63dcb6a3-2624949d
e706e746-6e3b1976
f296190c-e828e9db
4442aae2-4ad60575
f690cf64-6bdfffe7
ed1d377-e1cc0f14
75f0f0a0-e1cc0f14
710c3f90-4ad60575
e2b18481-9d9eea77
e7e71889-4ad60575
3a8271ac-e9e131c
d91dc415-5943c807
841b033b-ca7d8d80
647bb914-ca7d8d80
bea4a9c2-d896a311
d04818be-ca7d8d80
11c437b-ca7d8d80
bdcaab27-ca7d8d80
f9a6f6e9-8345dcb3
4a86715e-95864952
2fed65b6-377be55a
2e8b9b7-861bc63b
1e5f09ff-12ede6a2
a6550954-ca7d8d80
762e8080-afd08687
b2198f12-879548d7
ea12adb7-be9e9c9f
db649fc5-bf7aaf9f
c5eb687a-ca7d8d80

@jkarlin
Copy link

jkarlin commented Nov 6, 2024

Thanks @bmilekic, I can confirm that you're part of the 1% shared storage holdback experiment.

@zapo
Copy link
Author

zapo commented Nov 6, 2024

Thanks @johnivdel and @jkarlin I'm not very familiar with how the experiments are pushed on browser instances. Is it tied to chrome profile / user identity?
For this particular browser instance / experiment, can you confirm that running with --enable-privacy-sandbox-ads-apis=true is the way to go to force enable shared storage?

@johnivdel
Copy link

There are a few options:

  • You can run with --reset-variation-state which will put you in new experiments where you are likely to no longer be in the holdback group
  • You can run with --enable-features=SharedStorageAPI

Let me know in the event these do not work, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chrome-testing Chrome-facilitated testing discussions
Projects
None yet
Development

No branches or pull requests

5 participants