iOS Blueprint Safari allow-list rejects Google Docs viewer URLs containing nested `?url=` query parameters — use the direct asset URL instead

iOS

When you add a Google Docs viewer URL — such as https://docs.google.com/gview?url=https://assets.example.com/file.pdf — to the Safari allow-list in an iOS Blueprint, the Esper Console rejects it with a validation error and prevents the Blueprint from saving.

Why this happens

The Safari allow-list validator in iOS Blueprints does not accept URLs that embed a second full URL as a query parameter value. When it encounters a nested https:// scheme inside the query string, validation fails. This is a limitation of Blueprint URL validation logic, not a restriction imposed by iOS or Safari itself.

Steps to fix

1. Extract the direct asset URL from the Google Docs viewer URL. The direct URL is the value of the ?url= query parameter — everything after ?url=. For example, from:
   
   https://docs.google.com/gview?url=https://assets.example.com/document.pdf
   
   extract:
   
   https://assets.example.com/document.pdf
2. Open the iOS Blueprint in the Esper Console. Navigate to Blueprints → [Blueprint Name] → Safari → Allow-List. If you have already added the Google Docs viewer URL, remove it now.
3. Add the direct asset URL to the allow-list. Enter the URL extracted in step 1 into the allow-list field. Using the direct URL bypasses the nested-URL validation failure entirely.
4. Save and publish the Blueprint. Apply the updated blueprint to the target group or devices. Navigate to Blueprints → [Blueprint Name] and confirm the Blueprint saves without a validation error before publishing.

Note: With this change, users will access the file directly in Safari rather than through the Google Docs viewer. Confirm this experience is acceptable before deploying. The direct asset URL must also be publicly accessible without authentication — if the file is hosted behind a login, Safari will not be able to load it.

Verify: The Blueprint saves without a validation error, and on an enrolled device, opening Safari and navigating to the direct asset URL loads the file without being blocked. This should take effect within 5 minutes of publishing the Blueprint.

If this doesn't resolve it

If the direct asset URL is also rejected, check whether it contains special characters, additional nested parameters, or a non-standard port number that may also fail validation. If the URL is accepted but the file still fails to load on-device, the asset host may redirect through additional domains — add those domains to the allow-list as well and re-test.

If neither approach works or your workflow requires the Google Docs viewer wrapper, contact Esper Support with the following information:

• The full Google Docs viewer URL you are trying to allow-list
• The direct asset URL extracted from it
• The exact validation error message shown in the Esper Console
• The name and target group of the affected Blueprint

--- **Improved title:** iOS Blueprint Safari allow-list rejects nested URLs — use the direct asset URL

Still need help?

If you're still experiencing issues with Safari allow-list rejections for your Google Docs viewer URLs, please submit a support ticket and include the specific URLs being blocked and details about your Blueprint configuration.