Skip to main content

Can't Open or Sign the In-Store Contract on a Mobile Device? Allow Pop-ups

If tapping to open or sign the In-Store Contract does nothing on a phone or tablet, your browser's pop-up blocker is stopping it — here's how to turn it off in Safari, Chrome, and other mobile browsers.

Trying to open or sign the In-Store Contract on an iPad, iPhone, or other mobile device and nothing happens when you tap the button? This usually isn't a Floorzap problem. The contract opens in a pop-up window, and mobile browsers block pop-ups by default, which silently stops the contract from appearing.

This can start happening even if signing worked before. A browser or operating system update can re-enable the pop-up blocker automatically.

Allow Pop-ups in Safari (iPad & iPhone)

Safari blocks pop-ups by default. To allow them:

  1. Open the Settings app on your device.

  2. Tap Apps, then tap Safari. On older iOS/iPadOS versions, tap Safari directly in the Settings list.

  3. Find Block Pop-ups and turn the toggle off.

  4. Return to Floorzap, reload the page, and open the In-Store Contract again.

Allow Pop-ups in Chrome (Mobile)

If you use Google Chrome on a phone or tablet, check its pop-up setting inside the Chrome app:

  1. Open Chrome and tap the three-dot menu.

  2. Tap Settings, then Content Settings (or Site Settings).

  3. Tap Block Pop-ups and turn it off.

  4. Return to Floorzap, reload the page, and open the In-Store Contract again.

Using a Different Mobile Browser?

The same fix applies to any mobile browser, including Edge, Firefox, Samsung Internet, and others. Pop-up blocking is controlled either in the device's Settings app or inside the browser's own Settings menu, usually under a heading like Site Settings, Content Settings, or Pop-ups. Turn off the pop-up blocker there, then reload Floorzap and open the contract again.

Still not opening after allowing pop-ups? Reply to your support ticket, or email [email protected] with the timestamp of when it happened, a link to where it happened, and the affected user so our team can investigate.

Did this answer your question?