The age-verifier popup opens blank, invisible, or broken.

This page is for an age-verifier or age-verification layer whose popup UI itself is blank or broken: the overlay appears with no copy, the buttons are missing, the container is transparent, the modal is off-screen, or the verification form never finishes rendering. It is not a substitute for legal advice or a compliance certification.

If the popup is visible and a visitor can browse after selecting Decline, use the age-gate-not-blocking playbook. If the whole storefront is behind a coming-soon password, use password-page-stuck-online. Record the exact URL, device, browser, Market, consent state, customer status, published theme, app vendor, and whether the failure is blank UI or no gate.

Open the live URL in a private window, not only Theme Editor preview. Confirm the age-verifier app embed or section is enabled on the Current theme and assigned to the template you are testing. Inspect the DOM for the popup host and use the Console and Network panels to separate a script error from a missing stylesheet, font, image, translation, or configuration response.

• Compare desktop and mobile widths, a fresh session, and a session with the provider cookie removed.
• Check whether a consent manager, content blocker, CSP, lazy loader, or duplicate app hides or clears the popup.
• Look for display, visibility, opacity, zero dimensions, off-screen positioning, z-index, and a parent with clipping or transform.
• Verify the app's configuration, locale strings, verification endpoint, and asset requests return the expected status without exposing credentials.

Do not “fix” the blank UI by bypassing age checks, consent controls, or regional restrictions. Those are separate product and compliance decisions.

Fix only the confirmed cause: enable the current-theme embed, restore the missing section setting or locale, repair the provider asset path, correct the initialization order, or remove the second script that owns the same modal. If CSS is the cause, restore the intended layout and stacking context rather than adding an opaque global overlay.

Keep verification behavior explicit. A blank popup should not silently become an unblocked storefront. Preserve the intended Accept and Decline paths, avoid storing sensitive identity data in the theme, and keep the vendor's documented consent and retention settings. If the vendor endpoint or app is failing, capture the error and use its supported recovery path rather than injecting an unknown script.

Retest the live published theme in a clean browser: popup mounts with readable copy, controls have labels, keyboard focus enters the modal, Escape and close behavior are intentional, buttons work at mobile width, reduced motion is respected, and the content does not flash behind the layer. Repeat for each configured Market or consent state.

Then test the neighboring failure separately. A popup that renders but permits restricted browsing after Decline is age-gate-not-blocking, not age-verifier-popup-blank. A theme embed that cannot be placed is theme-app-extensions-not-appearing. Keep screenshots, URLs, timestamps, and the before/after result for the store owner.

Stay DIY if one popup has one confirmed embed, asset, CSS, locale, or initialization repair. Publish the smallest change, retest the live store, and document the result.

Pay $997 one-time when the work is wiring the Shopify stack you already use: lead capture, ops alerts, and a checkout-ready workflow. Nico at Latch AI Ops installs it on one live store in 72 hours after collaborator access is in. You are buying the install, not more orders, a conversion guarantee, or legal compliance advice.