After iOS 11.3 Update HTML Viewer does not proceed to splash screen

Jennifer Dooley

11. April 2018 21:59

Hi All,

 

After upgrading to iOS 11.3 from 11.2.7, the HTML5 viewer fails to load.  It doesn't even get to the splash screen.  We've tested this on WiFi and LTE connections, with the same behavior observed.  This is only present in Safari.  The viewer loads fine in Chrome on our iOS devices.  We are running Essentials 4.9.1/ HTML 5 viewer 2.10.1

 

Does anyone have ideas or suggestions? 

 

Thanks!

0

• 

  Permanently deleted user

  13. April 2018 18:12

  Hi Jennifer,

   

  I would see if you can check the developer tools (you would need a mac to do this) - 

   

  https://webdesign.tutsplus.com/articles/quick-tip-using-web-inspector-to-debug-mobile-safari--webdesign-8787

   

  and I would also look at using a tool like Fiddler to see where the loading stops -

   

  https://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigureForiOS

   

  If that fails, feel free to submit a support ticket and we can look at it in support.

   

  Regards,

   

  Wayne Richard

   

  Latitude Geographics Group Ltd.

   

  Head Office: 300 – 1117 Wharf Street  Victoria, BC Canada V8W 1T7

   

  Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com 

   

  Developers of Geocortex web-based mapping software | www.geocortex.com

   

  An Esri Platinum Business Partner

   

   

  0
• 

  Jennifer Dooley

  19. April 2018 17:09

  Ok, Wayne.  I'm going to open a ticket.

  0
• 

  John Nerge

  20. April 2018 13:23

  Jennifer, can you try opening one of our public GE apps on the iPad?

   

  https://gis.brooklynpark.org/neighborhoodinfo

   

  I just upgraded my iPad Air 2 (A1567) to iOS 11.3 and was able to see the splash screen and load the app on cellular and wifi.

  0
• 

  Jennifer Dooley

  23. April 2018 15:02

  John,

   

  I tried it, and I was able to get your app but not ours to load both on cellular and WiFi on my iPhone 7.  Thanks for the help with troubleshooting.  I let Wayne at Latitude know.  Looks like something specific to our installation may be causing the issue with the new version of Safari.

   

  Thanks!

   

  Jennifer

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.