I'm experiencing difficulties when configuring OAuth 2.0 Client ID in Google Cloud Console. Specifically, I cannot add Railway app domains with the .up.railway.app suffix to the "Authorized JavaScript origins" field.

Details:

• Current behavior: Domains like https://xxx.up.railway.app are being rejected and cannot be saved

• Only domains with .up.railway.com suffix (e.g., https://xxx.up.railway.com) are accepted

• Previous working state: In July, https://xxx.up.railway.app domains worked perfectly fine

• Current issue scope: Even attempting to save existing configurations with .up.railway.app domains results in validation errors

Expected behavior: Railway app domains with .up.railway.app suffix should be accepted as valid Authorized JavaScript origins, as they were previously.

Additional context: This appears to be a recent change, as the same configuration worked without issues a few months ago. The problem seems to affect all domains ending with .up.railway.app.

Has anyone encountered this issue recently? Any suggestions on how to resolve this or if there have been recent policy changes regarding Railway domains in Google Cloud OAuth configuration?