-
Notifications
You must be signed in to change notification settings - Fork 93
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
Comments
For what it's worth we are experiencing similar issues with 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 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 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. |
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! |
@johnivdel Here's my
|
Thanks @bmilekic, I can confirm that you're part of the 1% shared storage holdback experiment. |
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? |
There are a few options:
Let me know in the event these do not work, thanks! |
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?
The text was updated successfully, but these errors were encountered: