Anyone else experiencing issues with WebMaps, Experiences, etc. since the Hosted Feature Services issue on Monday?
Hey all,
Wondering if anyone else is experiencing issues remaining after the Hosted Feature Services issue on Monday.
For myself, one of our main Experience Builder solutions only seems to function in Chrome, not Firefox or Edge. On Monday, it wouldn't work in any browser. Since the issue was marked as resolved, it seems to never work in Edge, sporadically or partially work in Firefox, but seems to consistently work in Chrome.
The Experience has a toolbar at the top. Looking at two widget as indicators (layers and near me), all seems to work in Chrome; layers sometimes work in Firefox but near me never works; and no widgets work in Edge.
Chrome - All is good here (though performance is still slower than before Monday)
Firefox - Layers seem to work but Near Me never does
MS Edge - Nothing works!
I'll likely get in touch with the support team but I thought I'd ask here first to see if anyone else has been experiencing issues.
Thanks all!
UPDATE 1
In addition to the standard WebMap, I have a WebScene as part of the Experience which isn't loading at all in any browser! It just has the endless loading animation on screen. Note that if I open the WebScene itself, it works just fine, but it does not work as part of the Experience.
Interestingly enough when I try to edit the actual Experience, everything works as expected, even in MS Edge. This includes all widgets + the 3D view. Basically it works as it did before the service disruption on Monday. However in the actual live version, things decide to stop working.
Functional 3D view - MS Edge while editing the Experience
Functional Near Me widget - MS Edge while editing the Experience
UPDATE 2
I just got off the phone with Esri Tech Support (thanks Colin!). In addition to the Hosted Feature Service disruption, there has been another issue with Services5. The layers in my org are on services5 (URL of items is https://services5.arcgis.com/...). That issue has recently (today recently) been marked as resolved. The issues I'm facing may be related to that and will hopefully resolve itself once things fully reboot. Will post a third update tomorrow morning.
UPDATE 3
After testing my Experience this morning (Thursday) across three browsers, Firefox seems to be fully functional (widgets & 3D scene all working); Chrome is functional for all widgets, but the 3D scene still does not load; Edge continues to not function for any widgets or the 3D scene.
I'll be in touch with Esri support again today and will continue to provide updates.
UPDATE 4
Some positive-ish news on my end. The Experience seems to be fully functional across the three browsers I've been testing (Chrome, Firefox, Safari) on separate machines (and tablets). The Esri support staff that took on my case was not able to reproduce the issue on his end as everything was working fine. I tried the Experience on a separate desktop machine and it also worked just fine. I then tried it on a tablet (both the tablet view and forcing a desktop view) and that again worked fine. The issue seems to be localized to my laptop.
I've tried updating the browsers, clearing the cookies, cache, etc., all to no avail. On my laptop, things still only fully work in Firefox, partially work in Chrome, and do not work at all in Edge.
More updates to come here as this progresses...
FINAL UPDATE
It seems things are back to normal! Both the hosted feature services issue and the services5 issue seemed to work in tandem to cause the Experience to not function and have performance issues. Firefox was the first to be fully functional, followed by Edge, and lastly Chrome.
Regarding Chrome, I kept having issues with the 3D scene not loading. This was due to user error. A solution for a separate issue was to turn off graphics/hardware acceleration, however 3D scenes cannot load with that option disabled. When the embedded scene tried loading, it returned a constant loading symbol. However, when launching the scene on its own, the error message that a scene cannot be opened without utilizing hardware acceleration appeared. Once I turned on the option again, the embedded scene worked.
All in all, it seemed to be a solution that essentially "fixed itself" once the underlying causes from the hosted feature service and services5 had time to recover. Clearing cookies, cached content, etc. was a good initial step to see if that solves the problem, along with trying on different browsers and machines to see if the problem could be replicated. Regarding 3D scenes, if they are not loading, ensure hardware acceleration is turned on in your browser and try reloading. Thanks to Colin from Esri support for all his help with this issue!
Accepted Solutions
Same issue here, all the hosted feature layers not working.
