It seems that Safari’s new cross-site tracking feature is hindering the implementation of Google OAuth2 (at least when logging in to Google for websites). I am facing this problem with the project that I am currently developing, and I will be grateful for the consultation of anyone who has encountered the same problem.
Additional Information:
- When clearing all caches / cookies, the login stream works correctly the first time you log in.
- When updating, entering the input stream recognizes that you have already authenticated with the OAuth provider, opens a pop-up window and closes it immediately (this is the expected behavior for sources already allowed).
- after the pop-up window closes, the finality of the authentication flow breaks and silently crashes without errors abandoned inside the code, and no user has returned.
Removing the "prevent cross-site tracking" option allows you to maintain the input stream as intended.
source share