# Sandbox OAuth authorize page renders blank (empty #root) — app config verified correct **URL:** \ **Category:** Questions\ **Created:** [July 4, 2026, 11:33pm UTC](https://developer.squareup.com/forums/t/sandbox-oauth-authorize-page-renders-blank-empty-root-app-config-verified-correct/26738 "2026-07-04T23:33:16Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![voqua.ai](https://avatars.discourse-cdn.com/v4/letter/v/2acd7d/32.png) [@voqua.ai](https://developer.squareup.com/forums/u/voqua.ai)\ **Post date:** [July 4, 2026, 11:33pm UTC](https://developer.squareup.com/forums/t/sandbox-oauth-authorize-page-renders-blank-empty-root-app-config-verified-correct/26738/1 "2026-07-04T23:33:16Z")
Our sandbox OAuth authorize flow is stuck on a blank white page. Endpoint: `squareupsandbox dot com/oauth2/authorize` with client\_id `sandbox-sq0idb-LS1d6e7fIzICamMFT9aZ-A`. The page’s JS/CSS assets load successfully, but the #root container never renders any content (0 child elements) - no login form, no consent screen, nothing. Reproduced consistently across fresh page loads, incognito mode, and brand new state tokens/minimal query params (removing state and session=false didn’t help). App config (redirect URI, scopes, client\_id) all verified correct in the Developer Console, and using the console’s own “Authorize test account” shortcut works fine and issues valid tokens - so this appears isolated to the hosted authorize page’s front-end rendering, not our app setup. Can someone from the team take a look? ---
**Author:** ![Square-Dev-AI](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/square-dev-ai/32/2513_2.png) [@Square-Dev-AI](https://developer.squareup.com/forums/u/Square-Dev-AI)\ **Post date:** [July 4, 2026, 11:33pm UTC](https://developer.squareup.com/forums/t/sandbox-oauth-authorize-page-renders-blank-empty-root-app-config-verified-correct/26738/2 "2026-07-04T23:33:23Z")
👋 I’m Square Dev AI, here to help answer your question! Based on the information you’ve provided, the following documentation will help answer your question: > **[Square Sandbox](https://developer.squareup.com/docs/devtools/sandbox/overview)** > > An overview of the Square Sandbox, which can be used to simulate orders, invoices, payments, and transactions in a test environment. > **[Test Authorization with Web Server](https://developer.squareup.com/docs/oauth-api/walkthrough)** > > Learn how to build a Square OAuth API flow to authorize your application to access a Square account. > **Additional Documentation** > > [Test Authorization with Web Server](https://developer.squareup.com/docs/oauth-api/walkthrough) > [OAuth API](https://developer.squareup.com/docs/oauth-api/overview) > [OAuth API](https://developer.squareup.com/docs/oauth-api/how-it-works) If this documentation helped you find a solution, please check the box indicating that this reply solves the problem. Otherwise one of our Developer Advocates will provide additional assistance shortly. ---
**Author:** ![shay049ana](https://avatars.discourse-cdn.com/v4/letter/s/8dc957/32.png) [@shay049ana](https://developer.squareup.com/forums/u/shay049ana)\ **Post date:** [July 9, 2026, 6:41am UTC](https://developer.squareup.com/forums/t/sandbox-oauth-authorize-page-renders-blank-empty-root-app-config-verified-correct/26738/3 "2026-07-09T06:41:34Z")
Hello, Check if the sandbox URL has a trailing slash or missing redirect\_uri mismatchthose are the most common causes of a blank white page in the OAuth authorize flow. [Milestone Card](https://www.mymilestoneccard.com) ---
**Author:** ![getpworks](https://avatars.discourse-cdn.com/v4/letter/g/6a8cbe/32.png) [@getpworks](https://developer.squareup.com/forums/u/getpworks)\ **Post date:** [October 22, 2026, 11:38pm UTC](https://developer.squareup.com/forums/t/sandbox-oauth-authorize-page-renders-blank-empty-root-app-config-verified-correct/26738/4 "2026-10-22T23:38:21Z")
Same issue here, still happening as of October 22, 2026. In our case the SPA assets do not even load: the page shell HTML arrives (title “Square OAuth Flow”) but the JavaScript and CSS files return 404. Reproduced with curl: the authorize page on the sandbox host references its JS and CSS assets by hashed URLs, and each request 301-redirects to the production host, where those exact hashed paths return 404. Result: empty root element, blank white page in every browser we tried. Our config is verified correct as well (seller test account launched from the Developer Console first, redirect URI exact match, valid scopes), and the console’s “Authorize test account” path still issues tokens fine, so we can keep developing. But the hosted sandbox authorize screen is effectively unusable for any developer right now. Looks like an asset-hosting misconfiguration: the sandbox page references asset hashes that do not exist on the host it redirects to. Would be great if someone from the team could take a look. Happy to share the exact hashed URLs and curl traces if helpful.