3D model issues

[patudom]

• From @johnarban on Slack: "if I leave the AR mode any way other than the little "x" it skips back to a full screen version of the app that you can't interact with. I have to press the back button again to get back in to the running app"
• Alyssa says the 3D model would not load within the Data Story (not the AR or Merge Cube versions) and then the app reloaded itself in the browser. @Carifio24 says we can try to reduce the model size further.

[Carifio24]

From @johnarban on Slack: "if I leave the AR mode any way other than the little "x" it skips back to a full screen version of the app that you can't interact with. I have to press the back button again to get back in to the running app"

@johnarban Was this on Android or iOS? I wasn't able to reproduce on either - on my Android phone, pressing the back button (the only way I could exit other than pressing the "x") just brings me back to the 3D model screen in the app. On iOS I couldn't find a way to exit other than pressing the "x" button in the top left.

[johnarban]

This is on Android, using Chrome

[Carifio24]

Hmm - I can almost reproduce this, but it requires turning off my phone screen first. If I:

• Open the app
• Open the model-viewer view
• Turn off the phone screen
• Turn the screen back on and open the lock screen

the app isn't full-screen for me, but it is then totally unresponsive and requires a page refresh.

[Carifio24]

Possible idea for the unresponsive issue:
Listen for the ar-status event. When the status changes to "non-presenting", we could redirect to the app URL with some query parameter flag. If specified, maybe this query parameter puts the user directly into the model view and is then consumed. So then as far as the user can tell they just went back to the app, but we can avoid this issue? Maybe worth a shot