3PC Breakage Report: https://medium.com/google-developers/smart-home-cloud-services-with-google-part-2-3901ab39c39c I'm redoing this project (putting nodejs 18 instead of nodejs 10 or 12). It's working in firefox (completely releasing cookies) but it doesn't work in chrome in android cell and in computer windows 11 [383751192]

Can't Repro

Bug

Status Update

No update yet.

Description

ay...@google.com

created issue on behalf of ne...@gmail.com #1

Dec 12, 2024 04:47PM

https://medium.com/google-developers/smart-home-cloud-services-with-google-part-2-3901ab39c39c You can follow these steps described in this medium. Previously with the old chrome I didn't have any of these problems

Comments

ra...@google.com <ra...@google.com> #2Dec 20, 2024 03:57PM

Reassigned to ne...@gmail.com.

Thank you for filing this issue!

To help reproduce the breakage on our end, please provide us with the necessary test login credentials or a test 1P site (or a “sandbox demo” environment such as glitch.com or JS Fiddle or Project IDX).

Any sensitive details (such as test login credentials) can be shared using the “Restrict this comment/attachment” feature. Look for the eye+lock icon below the comment box when responding to the ticket on issuetracker.google.com.

If the above are not possible, please provide a single screen recording that shows all of the following steps:

User journey with third-party cookies enabled
Disable third-party cookies by enabling the 'test-third-party-cookie-phaseout' flag and disabling the 'tpcd-metadata-grants' flag from chrome://flags (learn more)
User journey with third-party cookies disabled
Developer console debug output showing which third-party cookie is causing breakage using the Chrome DevTools Issues tab

ne...@gmail.com <ne...@gmail.com> #3
Restricted
Dec 20, 2024 05:43PM

Learn More

pr...@google.com <pr...@google.com> Dec 20, 2024 05:43PM

Reassigned to 3p...@google.com.

ne...@gmail.com <ne...@gmail.com> Dec 20, 2024 05:43PM

deleted

Restricted

0 B

deleted

Restricted

0 B

deleted

Restricted

0 B

deleted

Restricted

0 B

ne...@gmail.com <ne...@gmail.com> #4
Restricted
Dec 23, 2024 04:02PM

Learn More

deleted

Restricted

0 B

ay...@google.com <ay...@google.com> #5Dec 23, 2024 11:12PM

Reassigned to ne...@gmail.com.

Project files aren't the best resources for us to help verify if the issue is truly third-party cookie related.
Could you provide a screen recording that shows:

Intended or succesful user journey with cookies enabled
User journey not working as intended when cookies are disabled

ne...@gmail.com <ne...@gmail.com> #6Dec 23, 2024 11:32PM

Ok.

https://www.youtube.com/shorts/f5V-sXhbNBc

https://www.youtube.com/watch?v=XVjS3vJh-LE

pr...@google.com <pr...@google.com> Dec 23, 2024 11:32PM

Reassigned to 3p...@google.com.

ay...@google.com <ay...@google.com> #7Dec 23, 2024 11:45PM

@ne...@gmail.com Thank you for the links, we'll look into this and loop back once we have an update.

Please note: there may be delays in response time given holiday season in our US offices.

ay...@google.com <ay...@google.com> #8
Restricted
Dec 23, 2024 11:49PM

Learn More

ne...@gmail.com <ne...@gmail.com> #9Dec 30, 2024 03:03AM

Comment has been deleted.

Message last modified on Jan 17, 2025 07:22PM

ch...@google.com <ch...@google.com> #10Jan 2, 2025 04:26PM

Hi, thank you for the report. Testing indicates that your issue might not be related to third-party cookies being enabled or disabled. Since the application appears to be having issues with sign-in regardless of if third-party cookies are enabled or disabled. If you’d like to replicate the testing done to come to this conclusion, please follow the steps below.

1. Open chrome://settings/cookies?search=Privacy+and+security and check to see if the button for “Block all third-party cookies” is on or off.
2. Navigate to

https://garagem-1f07e.web.app/login the site indicated in the video attached to the bug report,

https://www.youtube.com/watch?v=XVjS3vJh-LE
3. Click on the “Sign in with Google” button on the site.
4. Follow the sign in process.
5. Site will return to the home page with no indication that login has occurred. It will look the same as it did after the completion of step 2.
6. Open chrome://settings/cookies?search=Privacy+and+security and toggle the button for “Block all third-party cookies” so that it is the opposite of what it was in step 1. To enable or disable third-party cookies.
7. Repeat steps 2-5. Behavior of the site should be the same, indicating that third-party cookie blocking is not changing site behavior.

ne...@gmail.com <ne...@gmail.com> #11Jan 2, 2025 07:41PM

I'm glad you used the term "may" of doubt at the beginning of your current explanation. Well, I really assure you that https://

https://garagem-1f07e.web.app/link-account works very well on the Android 13 that I have in the car and

https://garagem-1f07e.web.app/login works very well on the old Chrome that I have on an Ubuntu 20.10 machine (from when the project was made) and it works very well on today's Firefox (if all cookie options are enabled, on the current Firefox)

ne...@gmail.com <ne...@gmail.com> #12Jan 2, 2025 07:43PM

*Note correction: if all cookie options are disabled in firefox

ne...@gmail.com <ne...@gmail.com> #13Jan 3, 2025 06:10PM

Pls talk about using document.cookie and __session tô solve my issue in my Angular client project

ne...@gmail.com <ne...@gmail.com> #14Jan 3, 2025 08:21PM

Pls help-me to put document.cookie = '__session=' + token + ';max-age=3600'; in my Angular Client Project from this:

https://medium.com/google-developers/smart-home-cloud-services-with-google-part-2-3901ab39c39c

Captura de tela 2025-01-03 172005.png

1 MB

View

Download

ne...@gmail.com <ne...@gmail.com> #15Jan 6, 2025 08:00PM

https://stackoverflow.com/questions/79333995/3rd-party-cookies-in-android-14-new-chrome-using-angular-firebase-auth-hosting-a

be...@google.com <be...@google.com> #16Jan 6, 2025 09:29PM

Reassigned to ne...@gmail.com.

We haven't enabled 3PC blocking for any new clients in the last 6+ months. The DevTools warnings are shown even when 3PC are not blocked, as a means to warn developers about upcoming changes.

If it confirmed that this issue is unrelated to 3PC blocking, another recommendation is that you could compare netlogs to see what is different between versions by following the Troubleshoot Chrome network issues article.

This bug is primarily for helping identify 3PC related issues; beyond that, we cannot assist with any implementations or troubleshooting.

ne...@gmail.com <ne...@gmail.com> #17Jan 6, 2025 09:58PM

You have all my codes for this project(

https://garagem-1f07e.web.app/login) that have already been sent in a restricted way up there. Please send a video like the one below that I made (I made it on the Galaxy S24 with Android 14, you must use Android 14 or higher in your video Or New Google Chrome) and that will be enough for me.

https://www.youtube.com/shorts/f5V-sXhbNBc

https://garagem-1f07e.web.app/login

be...@google.com <be...@google.com> #18Jan 7, 2025 09:56PM

Status: Won't Fix (Not Reproducible)

We were unable to reproduce user-facing breakage related to third-party cookie dependencies on our end.

However, we recognize that we may have missed something in our attempt to reproduce breakage. If this issue persists for you, please submit a new report with more details.

ne...@gmail.com <ne...@gmail.com> #19Jan 7, 2025 10:24PM

Actually, I need your support now, to upgrade the front-end from Angular 07 to Angular 19 (preferably) and AngularFire19, etc... I'm trying this on my own, but I don't know Angular. If you want, I can resend the sources (in a restricted way, of course) and you could send it to me in advance. Yesterday, I tried again in another browser that showed me errors that the Angular update could be the final solution to my issue.

deleted

0 B

deleted

0 B

ne...@gmail.com <ne...@gmail.com> #20Jan 11, 2025 03:15PM

https://stackoverflow.com/questions/79333995/3rd-party-cookies-in-android-14-new-chrome-using-angular-firebase-auth-hosting-a

I need help in

This

ne...@gmail.com <ne...@gmail.com> #21Jan 11, 2025 04:18PM

https://issuetracker.google.com/issues/389280099

ne...@gmail.com <ne...@gmail.com> #22Jan 13, 2025 02:32PM

Note-01: I think the solution necessarily goes through the last answer of this post:

https://www.googlecloudcommunity.com/gc/Serverless/Session-cookie-won-t-be-set-due-to-domain-name-mis-match-despite/m-p/610335/highlight/true

ne...@gmail.com <ne...@gmail.com> #23Jan 15, 2025 04:22PM

I'm switching from signinWithDirect to signinWithPopup (because a test project about firebase auth that I have, worked with Popup and presented my error that the main project using Direct).

The issue atual (When I switching) is(photo ATTACHED): main-NYXVCRV2.js:8 Cross-Origin-Opener-Policy policy would block the window.closed call.

deleted

0 B

IssueTracker