Skip to content

Fix Google Secure Signals UI detection for client-server and server-side#174

Merged
eiman-eltigani-ttd merged 7 commits intomainfrom
eee-UID2-6639-separate-ui-detection
Mar 9, 2026
Merged

Fix Google Secure Signals UI detection for client-server and server-side#174
eiman-eltigani-ttd merged 7 commits intomainfrom
eee-UID2-6639-separate-ui-detection

Conversation

@eiman-eltigani-ttd
Copy link
Contributor

@eiman-eltigani-ttd eiman-eltigani-ttd commented Mar 9, 2026

Added refresh/retry logic so the UI stays in sync with the server:

  • Moved the secure signals script from header to after token callback to prevent sync (consistent with client-side)
  • Lengthened/added timeouts used to check storage
  • Added an additional check to client server to check if token exists on refresh and retry if need (consistent with client-side) & updated one of the env variables to include a default just incase

@eiman-eltigani-ttd
Copy link
Contributor Author

I confirmed that the token is being read and stored locally in the deployed sites but will deploy and test after to confirm these new changes address any premature checks/sync issues

@eiman-eltigani-ttd eiman-eltigani-ttd merged commit afd1356 into main Mar 9, 2026
2 checks passed
@eiman-eltigani-ttd eiman-eltigani-ttd deleted the eee-UID2-6639-separate-ui-detection branch March 9, 2026 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants