AEM local page creation goes blank after choosing a template

An AEM as a Cloud Service SDK can start on port 4502 while the page-creation wizard still goes blank after template selection. A community user reported exactly that on a Windows ARM laptop, with nothing obvious in error.log. The symptom does not identify the culprit: local runtime, custom template, client library, and browser failure remain separate possibilities.

Capture the first failing request

Open the browser console and Network tab before clicking the template again. Save the first JavaScript exception and failed Touch UI, Granite UI, or clientlib request, including URL and status. This often provides evidence that the server log does not contain.

Compare a known-good template

Try an Adobe sample or otherwise known-good page template in the same SDK. If it works, focus on the project template, policies, resource type, and recently deployed clientlibs. If both fail, inspect SDK build, Java version, and operating-system support against Adobe’s local setup guidance.

Make the handoff reproducible

Share the SDK build, Java distribution and version, device architecture, template path, failing browser request, and relevant custom logs. Avoid declaring ARM incompatibility from one report; the thread itself did not settle that cause.

Adovo’s view

A blank authoring screen is a broken editorial workflow, even if the runtime is technically up. The fastest diagnosis holds one variable still: same SDK with another template, then same template with another runtime. That comparison is more useful than reinstalling blindly.