Apps Script web apps return 302 → 404 on one Samsung Android device, but works on other devices
18:26 09 Oct 2026

I'm experiencing an unusual issue accessing deployed Google Apps Script web applications on my Samsung Galaxy Z Fold 8.

Problem:

Multiple Apps Script web applications deployed with "Execute as: Me" and "Who has access: Anyone" fail to open on my phone, displaying Google's "Sorry, unable to open the file at this time" error.

Testing performed:

  • Windows PC using Microsoft Edge: Works, HTTP 200.

  • Windows PC using Edge InPrivate: Works, HTTP 200.

  • iPad using Safari: Works.

  • Another person's Android phone: Works.

  • My Galaxy Z Fold 8 using Chrome, Firefox, Samsung Internet, and Edge: Fails.

  • Chrome inside Samsung Secure Folder, including while signed out of Google: Fails.

  • Wi-Fi and cellular connections: Both fail.

  • Cleared Google site cookies, updated phone software, and restarted: No improvement.

  • Google Apps Script dashboard (script.google.com/home): Works normally.

Chrome DevTools findings:

When opening the account-neutral deployment URL:

https://script.google.com/macros/s/DEPLOYMENT_ID/exec

Google returns:

  1. HTTP 302 redirect to /macros/u/2/s/DEPLOYMENT_ID/exec

  2. HTTP 404 Not Found at the redirected address.

Manually accessing /macros/u/0/s/DEPLOYMENT_ID/exec also returns HTTP 404.

On my Windows PC, the account-neutral /macros/s/DEPLOYMENT_ID/exec request returns HTTP 200 and the application loads successfully.

The HTTP 404 response contains Google's generic Drive "Page Not Found" HTML.

Question:

What could cause Google Apps Script deployment URLs to return HTTP 404 on one Android device while working on other devices, including another Android phone? Is there a known issue with account-specific routing or Google authentication on Android?

google-apps-script