Bug 272326 – REGRESSION (iOS 17.5 beta): Opening USDZ to AR QuickLook prompts user if they wish to open model

• Component: New Bugs
• Status: RESOLVED WONTFIX

[Miles]

Created attachment 470812 [details]
Screenshot: opening USDZ to AR QuickLook now causes permission prompt.

With the new iOS 17.5 beta release (21F5048f) there is a change in behaviour when opening a USDZ model to AR QuickLook from Safari.

Previously, tapping a 3D model link would open the 3D model directly to an AR session in QuickLook. 

In Safari 17.5 beta, when the user taps on a 3D model link, the user is presented with a permissions prompt, asking:

> Open this 3D model?

With options "Cancel" and "Allow"

User must click "Allow" to be able to view model in AR QuickLook. 

Furthermore, the user will be presented with this prompt every single time they click on the same model link, and every 3D model on that same site, and all other sites. 

Is this an intentional change in behaviour?

I would submit that this increases the steps required to enter an AR experience and runs the risk of confusing the user. This seems to interrupt a well established user interaction, and will detrimentally impact a very large range of existing websites currently implementing AR QuickLook integration. 

Repro steps:

- Using iPhone with iOS 17.5 beta
- Visit this page: https://developer.apple.com/augmented-reality/quick-look/
- Tap to open a 3D model
- Observe that a permission prompt is displayed to the user asking if they wish to allow opening the 3D model.

[Radar WebKit Bug Importer]

<rdar://problem/126078339>

[Mike Wyrzykowski]

Thank you for the report, this was an intentional change

[Miles]

Understood. Thanks for the confirmation. 

Is there a forum to discuss this or provide feedback?

I understand that this was probably introduced as a security/privacy measure. 

Although it seems like there's very little consequence to inadvertently opening a 3D model into an AR QuickLook session as it's a sandboxed environment and does not risk exposing any personal or spatial data to the originating web page.

Still, I understand the concept. 

But I feel this will interrupt the flow of many existing 3D/AR viewers in existence on the web today. Particularly as these custom 3D/AR experiences already set up the user expectation that they are about to view the model in AR.

For 3D configurator experiences, where the user may need to enter and exit AR repeatedly, while making adjustments to a 3D model and then viewing in AR, this will introduce an annoying interruption to the flow of the experience. 

I could better understand a site-wide Permissions request, similar to Camera / Geolocation / Microphone access. Approve once for a site and it will then automatically open for all models on that site.

But this new implementation will require the user to Allow each and every view of each and every model on each and every site.

[Felix Herbst]

I would like to also understand this better.

The above mentioned workflow for configurators is a common one. I could understand if there was a way (similar to permissions) to allow the website to open models going forward, not asking every single time.